Re: Digest for adwords-api@googlegroups.com - 9 updates in 8 topics

56 views
Skip to first unread message

Phisit Inkrthuek

unread,
Feb 16, 2024, 12:11:25 PM2/16/24
to adwor...@googlegroups.com

ในวันที่ พฤ. 15 ก.พ. 2024 17:59 <adwor...@googlegroups.com> เขียนว่า:
Zweitze <zwe...@gmail.com>: Feb 15 02:55AM -0800

You're using the .NET library, right?
In one of the recent versions a breaking change was introduced, related to
the default settings in the config file. You need to use an extra package.
Unfortunately I forgot which.
 
The library maintainers refuse to document this breaking change in the
change file.
Your best bet is to enter a new bug report, within a few days you should
get a reply.
If you're in a hurry, look at the closed bug reports of the last six months
or so.
 
 
 
On Tuesday, February 13, 2024 at 2:44:10 PM UTC+1 Olayinka Popoola wrote:
 
G San <gl...@upside.digital>: Feb 14 06:34PM -0800

Hi thanks for this but there's some details that is not giving the full
picture.
 
So to clarify, we are a lead generation company so we don't deal with the
actual sales - it happens on our client end, but regardless we get updates
from our clients when sales happens so we would like to post that as a
conversion to help with our campaigns.
 
We currently have the following conversion points:
 
1. *Lead* - Processed by *GTM (enhanced conversion already)* - this is when
a lead submits our forms on the landing page. A *transaction_id *is created
for the lead at this point and is passed to Google Ads via GTM.
2. *Validated Lead* - This one we want to process via *API* - this is when
the lead data is pushed to our CRM (with the transaction_id) and then the
details are validated.
3. *Qualified Lead* - This one we want to process via *API* - this is when
the lead is updated to *Appointment*.
4. *Converted Lead* - This one we want to process via *API *- this is when
the lead data has made a *Purchase* which happens on our client's end, but
our CRM is updated with this event.
 
Which we can use to make the lead journey is tracked up to *Converted Lead*.
 
So with the above said, do you still think we should send the leads as:
*Validated Lead *==> Enhanced Conversions for Leads
<https://developers.google.com/google-ads/api/docs/conversions/enhanced-conversions/leads>
?
 
*Qualified Lead* (Appointment) ==> Adjust Conversions
<https://developers.google.com/google-ads/api/docs/conversions/upload-adjustments> ?
Is the adjustment method the one needed to adjust a transaction_id's
conversion action from *Validated Lead* to *Appointment*? Is there another
way to do this that won't require a delay of 24 hours, because appointment
setting is usually happens the same day the lead comes in.
 
*Converted Lead *(Purchase) ==> Upload Click Conversions
<https://developers.google.com/google-ads/api/docs/conversions/upload-clicks> ?
Do we use Click Conversions or do we use Upload Store Sales Conversions
<https://developers.google.com/google-ads/api/docs/conversions/upload-store-sales-transactions>
 
[image: Screenshot 2024-02-15 at 1.17.09 pm.png]
 
Thank you! Looking forward to finalising which are the methods we should
use.
 
On Thursday, February 15, 2024 at 5:53:54 AM UTC+11 Google Ads API Forum
Advisor wrote:
 
G San <gl...@upside.digital>: Feb 15 02:30AM -0800

Or can we just post all of our conversion actions (Validated, Qualified and
Converted Leads) as Enhanced Conversions for Leads
<https://developers.google.com/google-ads/api/docs/conversions/enhanced-conversions/leads>
?
Iryna Dzikun <dziku...@gmail.com>: Feb 14 11:08PM -0800

Hello,
 
I am writing to inquire about the status of our request for the Google Ads
API Developer Token. We submitted our request almost three weeks ago and
have not received any confirmation or feedback from your side. This is for
Google Ads account number 735-984-6256. We only need basic access.
 
We kindly ask you to check the status of our request and let us know when
we can expect to receive the Developer Token. This is critical for our
business needs, as we want to use the API for our advertising campaigns.
 
We appreciate your prompt response and assistance on this matter.
 
Thank you!
 
Iryna Dzikun
 
On Tuesday, February 13, 2024 at 1:10:36 PM UTC+3 Iryna Dzikun wrote:
 
"D. H." <heiberge...@gmail.com>: Feb 14 05:57PM -0800

Hi,
 
Using the python client library I get values returned as "normal" floats
like "0.9605413375709904" for campaign optimization score, from the
campaign query report.
 
Is it possible something in your process is converting/interpreting the
number in scientific notation? What does the initial raw response look like?
 
Regards,
 
D.H.
 
On Saturday, February 10, 2024 at 3:15:39 PM UTC+8 Oksana Sulyma wrote:
 
Daniel Alvarado <gaytan...@gmail.com>: Feb 14 04:17PM -0800

Hello team,
 
We are using the campaign, adgroup, keyword view and keyword display view
resources.
Data associated to campaign, adgroup are correct.
However when We check at the keywords level, the costs show discrepancy for
Display Keywords: To be precise, the costs associated to keyword display
view are empty.
Can you help us?
 
We are happy to share in private google ui and script.
 
Thanks!!
 
Daniel.
Mark Petree <petre...@gmail.com>: Feb 14 03:46PM -0800

I was requested to post on here. Any update?
 
On Monday, February 12, 2024 at 11:58:13 AM UTC-8 Google Ads API Forum
Advisor wrote:
 
Google Ads API Forum Advisor <ads...@forumsupport.google>: Feb 15 05:43AM

Hi,
 
Thank you for reaching out to the Google Ads API support team.
 
After reviewing your concern, I understand that you are encountering the "INTERNAL_ERROR" while trying to fetch data using the queries via the Google Ads API searchStream method.
 
Kindly note that the INTERNAL_ERROR occurs when something unexpected happened while processing the request. The common cause could be that the API isn't functioning correctly due to a bug. However, this is transient in nature and the issue may be resolved by retrying the request after a short pause. You may retry any requests that failed with this error, using an exponential backoff schedule for the retries. Here is a code example demonstrating how to implement an exponential back off strategy.
 
Also, note that I am able to replicate this issue at my side. So, kindly allow me to check this with the rest of our team and one of our colleagues will reach out to you once we have an update. Meanwhile, your patience is highly appreciated.
This message is in relation to case "ref:!00D1U01174p.!5004Q02rz6B3:ref"
 
Thanks,
 
Google Ads API Team
Prashanth Sirsi <pras...@anibyte.net>: Feb 15 07:32AM +0530

I have not received any case id from them yet. Please advise on how to
proceed further.
I am not getting any response from them, no matter how I try
 
Regards,
Prashanth Sirsi
Ph: 98452 60757
 
 
On Wed, Feb 14, 2024 at 6:01 PM Google Ads API Forum Advisor
 
> Hi Prashanth,
 
> Thank you for reaching out to the Google Ads API support team.
 
> After reviewing your concern, I understand that you have applied for
basic access and haven’t received any response. Since the access requests
are handled by the Google Ads API Compliance team, we are transferring the
case to the Ads API Compliance team. Can you kindly provide the following
information for the compliance team to further assist you with your concern:
 
> Case ID generated from the compliance team in the format 0-0###########0
(if there is any generated).
 
> @Compliance team, please confirm if you are able to assist in the below
access request.
 
> Google Ads Manager Account (MCC) ID: 631-963-6223
> Case ID: Requested
 
> Do reach out to the Google Ads API support team for any queries related
to the API.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to adwords-api...@googlegroups.com.

Google Ads API Forum Advisor

unread,
Feb 28, 2024, 10:33:04 PM2/28/24
to phisi...@gmail.com, adwor...@googlegroups.com
Hi,

Thanks for your patience with this issue. We have confirmed that this issue is fixed now. You can try with issuing the queries in question again, and let us know if you still experience issues with them.

Thanks!

 
This message is in relation to case "ref:!00D1U01174p.!5004Q02rz6B3:ref"

Thanks,
 
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages