Conversion action is not recieveing conversions uploaded with WBRAID/GBRAID using AdwordsAPI

67 views
Skip to first unread message

Kulvinder Tuteja

unread,
Mar 20, 2025, 8:45:33 AM3/20/25
to Google Ads API and AdWords API Forum
Hi,

I have been trying to upload conversions using WBRAID/GBRAID IDs for the clicks where I do not have GCLID. I got a successful response with the job_id when sending the request to Adwords ConversionUploadService. I am not able to see any logs to see what is going wrong, and the conversion values are not getting reflected in the Adwords UI for the conversion action

Sample_result:
results {
  conversion_action: "customers/7650046580/conversionActions/7052526877"
  conversion_date_time: "2025-03-17 17:06:52+00:00"
  gbraid: "0AAAAA-sal-BKom2V6zQIJGUC9LddJgEOs"
}
job_id: 4597829396819412843

Google Ads API Forum Advisor

unread,
Mar 20, 2025, 1:11:13 PM3/20/25
to ascendeu...@gmail.com, adwor...@googlegroups.com

Hi,

Thank you for reaching out to the Google Ads API support team.

Based on the provided information, I understand that the conversion values are not getting reflected in the Google Ads UI for the conversion action. Upon checking your Google Ads Account (765-004-6580), I could see that the conversion action ‘7052526877’ status is showing as ‘Active’ and all the conversions are recording successfully.

To report on conversions by conversion date in Google Ads, add the relevant 'by conv. time' columns, such as 'Conversions (by conv. time)' and 'Conv. value (by conv. time)' in Google Ads and compare the successful API uploaded data. Please be informed that the uploaded conversions are reflected in reports for the "impression" date of the original click, not the date of the upload request or the date of the conversion_date_time of the ClickConversion.

I have tried to verify the offline_conversion_upload_conversion_action_summary, I could see that you have encountered the following API errors:

1. EXPIRED_EVENT error means that when uploading conversions, the click associated with the given identifier or ios url parameter is either too old to be imported or occurred outside of the click-through lookback window for the specified conversion action. For this error, you may double-check if the given identifier is not too old or occurred before the lookback window for the specified combination of conversion date and conversion action. You may use the click_view report resource to verify your GCLID. In addition, you can first verify the click_through_lookback_window_days specified in your conversion_action. From the value retrieved, then perform a request using the click_view report for each day (with date filter for one day) until the last valid date, in reference to the lookback window days. 

2. EVENT_NOT_FOUND error which is due to the click associated with the given identifier or iOS URL parameter could not be found in the system. This can happen if the identifier or iOS URL parameter are collected for non Google Ads clicks. I would suggest, when storing the GCLID, you'll need to double-check to see where the GCLID came from. Having said that, would you be able to confirm if the identifier used in the request actually generated from a Google Ads click?

3.CONVERSION_PRECEDES_EVENT says that the event time is earlier than the Click event. I would like to ask if the Click event is the starting point of all web events? At what node does it occur specifically? Our event occurs and is transmitted back when the user enters the web page and performs a specific operation. The trigger time should be after Click.

To assist you further, please provide an uncropped UI screenshot that shows where the conversion values are not getting reflected and how many conversions you have successfully uploaded through the Google Ads API. Additionally, provide us with the complete API logs (request with request-id) generated at your end to better assist you further 

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.


Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-03-20 17:10:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vHBXF:ref" (ADR-00295694)



Reply all
Reply to author
Forward
0 new messages