Hi,

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

Please be informed that I have removed your response from the forums as it 
contains the PII information.

Based on the information provided, I understand that you're including the 
'session_attributes' field when uploading conversions via the Google Ads API, 
but encountering a REQUIRED field error specifically related to the missing 
'GCLID' field. According to the help center article, when importing offline 
conversions, if a 'gclid' is not available, session attributes can be used as 
an alternative. However, it's also clearly stated that OCI users must include 
either hashed user-provided data with wbraid/gbraid or with session_attributes 
when 'GCLID' is not present. In your request payload, it's evident that no 
user-provided data is being passed, which is the primary reason for this error.

I would recommend you to refer to this API documentation for more detailed 
information. This code example describes you on how to pass the user 
identifiers along with the session attributes field. However, I am providing 
you the sample request body on how to pass the user identifiers along with the 
session attributes:

Request Body: ============== POST 
https://googleads.googleapis.com/v20/customers/{customerId}:uploadClickConversions?key=[YOUR_API_KEY]
 HTTP/1.1

developer-token: **********************
Authorization: Bearer [YOUR_ACCESS_TOKEN]
Accept: application/json
Content-Type: application/json

{
  "conversions": [
    {
      "sessionAttributesEncoded": "sessionAttributesEncoded",
      "conversionAction": 
"customers/{customerId}/conversionActions/{conversionActionId}",
      "conversionDateTime": "2025-05-22 19:40:17-04:00", //random conversion 
date time has been passed
      "conversionValue": 0,
      "currencyCode": "USD",
      "orderId": "1234566",
      "userIdentifiers": [
        {
          "hashedEmail": "hashedEmailId"
        }
      ]
    }
  ],
  "partialFailure": true
}

I would request you to pass the userIdentifier object and try to make the API 
call and let us know how it works from your end. If you still encounter any 
issues even after following the provided suggestion, I would request you to 
share the complete updated API logs (request and response logs with request-id 
and request header) generated at your end to further assist you better.

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-07-25 22:28:59Z GMT] This message is in relation to case 
"ref:!00D1U01174p.!500Ht01swpTI:ref" (ADR-00320287)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/B7ScY000000000000000000000000000000000000000000000SZZ7SB00-wfIA5IqSdGcVGq3yaq_4g%40sfdc.net.
  • RE... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to