NO_CONVERSION_ACTION_FOUND

174 views
Skip to first unread message

Paulo Silva

unread,
Jun 11, 2024, 5:14:54 AM6/11/24
to Google Ads API and AdWords API Forum
Hi

i send to search API the request below

* Preparing request to https://googleads.googleapis.com/v15/customers/6328939997/googleAds:search
* Current time is 2024-06-10T23:36:30.508Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 30000ms
* Enable SSL validation
* Enable cookie sending with jar of 15 cookies
* Too old connection (228 seconds), disconnect it
* Connection 257 seems to be dead!
* Closing connection 257
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS alert, close notify (256):
* Hostname in DNS cache was stale, zapped
*   Trying 2800:3f0:4001:818::200a:443...
* Connected to googleads.googleapis.com (2800:3f0:4001:818::200a) port 443 (#258)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/cert.pem
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=upload.video.google.com
*  start date: May 21 06:28:35 2024 GMT
*  expire date: Aug 13 06:28:34 2024 GMT
*  subjectAltName: host "googleads.googleapis.com" matched cert's "*.googleapis.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x114008c0800)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /v15/customers/6328939997/googleAds:search HTTP/2
> Host: googleads.googleapis.com
> user-agent: insomnia/9.2.0
> content-type: application/json
> developer-token: ----
> authorization: Bearer ---
> accept: */*
> content-length: 322

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

| {
| "query":" SELECT conversion_action.id,conversion_action.name,             conversion_action.type,             conversion_action.category,             conversion_action.status,             conversion_action.type,conversion_action.counting_type,             conversion_action.owner_customer      FROM conversion_action"
| }

* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 200
< request-id: s2pDv8bufN2TIR_7XFOgZw
< content-type: application/json; charset=UTF-8
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< date: Mon, 10 Jun 2024 23:36:31 GMT
< server: ESF
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< accept-ranges: none


* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Received 644 B chunk
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #258 to host googleads.googleapis.com left intact

and receive this result

{
"results": [
{
"conversionAction": {
"resourceName": "customers/6328939997/conversionActions/6819728058",
"status": "ENABLED",
"type": "UPLOAD_CLICKS",
"category": "PURCHASE",
"countingType": "MANY_PER_CLICK",
"id": "6819728058",
"name": "GlucoFreedom",
"ownerCustomer": "customers/6328939997"
}
}
],
"fieldMask": "conversionAction.id,conversionAction.name,conversionAction.type,conversionAction.category,conversionAction.status,conversionAction.type,conversionAction.countingType,conversionAction.ownerCustomer",
"queryResourceConsumption": "909"
}

note the resource name that is returned

customers/6328939997/conversionActions/6819728058

when i try to send to upload click api (request below)
* Preparing request to https://googleads.googleapis.com/v15/customers/6328939997:uploadClickConversions
* Current time is 2024-06-10T23:21:46.120Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable timeout of 30000ms
* Enable SSL validation
* Enable cookie sending with jar of 15 cookies
* Too old connection (356 seconds), disconnect it
* Connection 255 seems to be dead!
* Closing connection 255
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS alert, close notify (256):
* Hostname in DNS cache was stale, zapped
*   Trying 2800:3f0:4001:837::200a:443...
* Connected to googleads.googleapis.com (2800:3f0:4001:837::200a) port 443 (#256)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/cert.pem
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=upload.video.google.com
*  start date: May 21 06:28:35 2024 GMT
*  expire date: Aug 13 06:28:34 2024 GMT
*  subjectAltName: host "googleads.googleapis.com" matched cert's "*.googleapis.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x114008cb800)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /v15/customers/6328939997:uploadClickConversions HTTP/2
> Host: googleads.googleapis.com
> user-agent: insomnia/9.2.0
> content-type: application/json
> developer-token: ---
> login-customer-id: 6328939997
> authorization: > accept: */*
> content-length: 354

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

| {
|   "conversions": [{
|    "gclid":"EAIaIQobChMImv_s_ojNhgMVk25_AB3_Dwo5EAAYAyAAEgIXVPD_BwE",
| "conversionAction": "customers/6328939997/conversionActions/6819728058",
| "conversionDateTime": "2024-06-10 10:33:00+00:00",
| "conversionValue": 121.10,
| "currencyCode": "USD"
| }],
|   "partialFailure": true,
|   "validateOnly": false,
|   "debugEnabled": true
| }

* We are completely uploaded and fine
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 200
< request-id: yv_sfco2wsiB97SUPJXFtw
< content-type: application/json; charset=UTF-8
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< date: Mon, 10 Jun 2024 23:21:48 GMT
< server: ESF
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< accept-ranges: none


* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Received 1170 B chunk
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #256 to host googleads.googleapis.com left intact

and receive this response

{
"partialFailureError": {
"code": 3,
"message": "The conversion action specified in the upload request cannot be found. Make sure it's available in this account., at conversions[0].conversion_action",
"details": [
{
"@type": "type.googleapis.com/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [
{
"errorCode": {
"conversionUploadError": "NO_CONVERSION_ACTION_FOUND"
},
"message": "The conversion action specified in the upload request cannot be found. Make sure it's available in this account.",
"trigger": {
"stringValue": "customers/6328939997/conversionActions/6819728058"
},
"location": {
"fieldPathElements": [
{
"fieldName": "conversions",
"index": 0
},
{
"fieldName": "conversion_action"
}
]
}
}
],
"requestId": "VuQB0WeXWPd1FYUZpzIjtQ"
}
]
},
"results": [
{}
],
"jobId": "2554110228377542301"
}

Do you agree that it doesn't make sense? I query an api that returns the name of the same resource that the upload api is refusing. Can someone help me?

Google Ads API Forum Advisor

unread,
Jun 11, 2024, 10:41:15 AM6/11/24
to pa...@extractify.com.br, adwor...@googlegroups.com
Hi,

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

From the logs that you have provided, I can confirm that the status of the conversion action - 6819728058 is 'inactive' in the Google Ads UI. 

Conversion tracking is an important tool in your online marketing campaigns. It’s important to accurately understand the status of your conversions and diagnose any conversion actions that have errors and aren’t working properly. Tag Assistant is a tool that helps you verify your conversion actions on your website. I would recommend you refer to this Help Center article on "Use Tag Assistant to troubleshoot your unverified or inactive conversion actions" for more information.

Let us know if this works or if you still encounter the NO_CONVERSION_ACTION_FOUND error.

 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJHQs:ref" (ADR-00239441)

Thanks,
 
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages