Hi,

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

Since you are uploading the conversion via the API, please note that the count 
of "successfully uploaded conversions" via the API doesn't necessarily equal 
the count of reported conversions, and this is expected. It is important to 
make sure that you are comparing the "successfully uploaded conversions" in 
both the API and the UI. I would recommend you refer to this Help Center 
article ​for more information regarding the discrepancies in conversion 
uploads. For more details on mapping user interface metrics to API metrics, you 
can refer to the Map user interface metrics API documentation, which provides a 
table summarizing the equivalent metrics in the API for the UI columns.

Probably you are verifying the wrong column in the Google Ads UI for the 
conversion count. Kindly note that conversions in the Google Ads UI will appear 
in reports based on the time of the impression or click. If you want to view 
conversions by their conversion date in Google Ads, you can include the 
relevant "conversion time" columns in your reports, such as "Conversions (by 
conv. time)" and "Conv. value (by conv. time)." 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 conversions.

If you are still observing the issue, to help us investigate this issue 
further, please provide the following:

Specific data where you noticed this discrepancy.
Provide the ‘conversion action name’ and the ‘Google Ads customer ID’ where the 
conversions are recorded.
Relevant uncropped UI screenshots (if available).
Please provide us with the complete API logs (request and response with 
request-id and request header) generated at your end when uploading the 56 
conversions successfully via the API.

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 for 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 the Reply privately to the author option or direct 
private reply to this email.

Thanks,

Google Ads API Team


Feedback
How was our support today?


[2025-08-19 23:05:14Z GMT] This message is in relation to case 
"ref:!00D1U01174p.!500Ht01u4gg0:ref" (ADR-00330418)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/adwords-api/m2hjY000000000000000000000000000000000000000000000T19K4Q00kiAMlCi4REeYjuIN2GLkqw%40sfdc.net.
  • Co... Radical Activity
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to