No CALL_CONVERSION_ALREADY_EXISTS Error Returned
Roza Adamyan
Hi,
I noticed that when I upload the same conversion, the Google Ads API does not return a CALL_CONVERSION_ALREADY_EXISTS error. Is deduplication now handled within Google Ads so that duplicate conversions are silently ignored, or is there another reason for this behavior?
Below are the details of my two requests for your reference.
First request:
Method Name: /google.ads.googleads.v17.services.ConversionUploadService/UploadCallConversions
Host:
Headers: {
"x-goog-api-client": "gl-dotnet/8.0.0 gapic/20.1.0 gax/4.8.0 grpc/2.60.0 gccl/4.0.1 pb/3.25.0",
"developer-token": "REDACTED",
"login-customer-id": "customer_id",
"x-goog-request-params": "customer_id=customer_id"
}
{ "customerId": "customer_id", "conversions": [ { "callerId": "+15163596797", "callStartDateTime": "2025-03-12 12:53:16+00:00", "conversionAction": "customers/customer_id/conversionActions/6902390566", "conversionDateTime": "2025-03-12 12:53:16+00:00", "conversionValue": 0, "currencyCode": "USD" } ], "partialFailure": true }
Response
--------
Headers: {
"request-id": "tYEqqXUtvP7u8IZU6ei4wA",
"date": "Mon, 17 Mar 2025 12:45:57 GMT",
"alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000",
"content-disposition": "attachment"
}
{ "results": [ { "callerId": "+15163596797", "callStartDateTime": "2025-03-12 12:53:16+00:00", "conversionAction": "customers/customer_id/conversionActions/6902390566", "conversionDateTime": "2025-03-12 12:53:16+00:00" } ] }
----------------END API CALL----------------
Second request:
Method Name: /google.ads.googleads.v17.services.ConversionUploadService/UploadCallConversions
Host:
Headers: {
"x-goog-api-client": "gl-dotnet/8.0.0 gapic/20.1.0 gax/4.8.0 grpc/2.60.0 gccl/4.0.1 pb/3.25.0",
"developer-token": "REDACTED",
"login-customer-id": "customer_id",
"x-goog-request-params": "customer_id=customer_id"
}
{ "customerId": "customer_id", "conversions": [ { "callerId": "+15163596797", "callStartDateTime": "2025-03-12 12:53:16+00:00", "conversionAction": "customers/customer_id/conversionActions/6902390566", "conversionDateTime": "2025-03-12 12:53:16+00:00", "conversionValue": 0, "currencyCode": "USD" } ], "partialFailure": true }
Response
--------
Headers: {
"request-id": "W3UeUbc4zQVA8dk-4SdqJw",
"date": "Mon, 17 Mar 2025 12:41:42 GMT",
"alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000",
"content-disposition": "attachment"
}
{ "results": [ { "callerId": "+15163596797", "callStartDateTime": "2025-03-12 12:53:16+00:00", "conversionAction": "customers/customer_id/conversionActions/6902390566", "conversionDateTime": "2025-03-12 12:53:16+00:00" } ] }
----------------END API CALL----------------
Best, Roza.
Google Ads API Forum Advisor
Thank you for reaching out to the Google Ads API support team.
Yes, it is expected that you should get CALL_CONVERSION_ALREADY_EXISTS error when you upload a conversion with the same conversion_date_time, conversion_action, caller_id.
I could see that you are using the 'v17' of the Google Ads API which is already deprecated. I would recommend migrating to the latest version v19, please follow this guide to upgrade to the latest version and provide us with the latest version complete API logs (request and response logs with request-id and request header) generated at your end while updating a conversion with same data for the first time and second time. This would help us investigate the issue 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 .Net to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
You may refer to this documentation on deprecation and sunset for more information regarding the specific deprecation and sunset dates for each available version.
You can send the details via 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-03-17 20:39:05Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vHAfX:ref" (ADR-00295012)
