API (Offline Conversions) Troubleshooting
Accounting Uprova
Hello,
I am reaching out to request assistance regarding the tracking of our uploaded API conversions. Our Ads Manager account, associated with the basic token access, is under the number ending in 8031. Our main Ads account is ends in 4084.
Currently, our team manually uploads offline conversions using a Google Sheet on a daily basis. However, we have encountered two issues that require clarification and resolution:
1) When we upload conversions using the account ending in 8031 and ConversionActionId ending in 5991, the records fail to upload. We receive the following error: PartialFailure = {{ "errors": [ { "errorCode": { "conversionUploadError": "INVALID_CONVERSION_ACTION" }, "message": "Make sure you specify a valid conversion action set up for offline import.", "trigger": {
2) When we upload conversions using the account ending in 8031 and Linked ACCOUNT ConversionActionId ending in 1403, we receive a successful response. However, when we navigate to the Google Ads Manager dashboard and access the Conversions page, we are unable to locate the uploaded records.
We would greatly appreciate your assistance in addressing these issues and helping us understand the destination of our uploaded offline conversions.
Thank you for your attention to this matter.
Best regards,
The Uprova Team
Google Ads API Forum Advisor
Thank you raising this issue to the Google Ads API support team.
With regards to your concern, it appears that this is about the INVALID_CONVERSION_ACTION error. Having said that, please note that there are several items to note to avoid the said error, you may see below:
To avoid a ConversionUploadError.INVALID_CONVERSION_ACTION error, the conversion_action [https://developers.google.com/google-ads/api/reference/rpc/v14/ClickConversion#conversion_action] attribute must refer to a ConversionAction where:
- The ConversionActionType is UPLOAD_CLICKS [https://developers.google.com/google-ads/api/reference/rpc/v14/ConversionActionTypeEnum.ConversionActionType#upload_clicks].
- The status [https://developers.google.com/google-ads/api/reference/rpc/v14/ConversionAction#status] of the ConversionAction is ENABLED.
- The ConversionAction exists in the effective conversion account [https://developers.google.com/google-ads/api/docs/conversions/overview#effective_conversion_account] of the click's Google Ads account.
- At the time of the click, conversion tracking was enabled in the effective conversion account of the click's Google Ads account.
- The customer_id of the UploadClickConversionsRequest [https://developers.google.com/google-ads/api/reference/rpc/v14/UploadClickConversionsRequest] must be the customer ID of the owner_customer of each click conversion's conversion_action [https://developers.google.com/google-ads/api/reference/rpc/v14/ClickConversion#conversion_action].
Moreover, you mentioned that currently, your team manually uploads offline conversions using a Google Sheet on a daily basis. That said, can you confirm when you encountered the issue is when you uploaded conversions via the Google Ads API? If so, can you please provide the below complete API logs so our team can have a better view and can provide accurate guidance to this matter?
- request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
- response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
- request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
- request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers
Note that these logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here (https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging) for the specific guideline to enable it.
For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include HTTP response headers in the output.
You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.
This message is in relation to case "ref:_00D1U1174p._5004Q2n7Lpg:ref"
 |
Google Ads API Team |
