Thanks for the clarification. Just to confirm my understanding of the current behavior: - The consent object has to be populated for all users (EEA and non-EEA). - Conversions are only usable for reporting and user lists when ad_user_data and ad_personalization are GRANTED. - If consent is UNSPECIFIED or missing, those uploads are treated as not consented and effectively dropped for measurement and lists. Given that, my last question is a practical one: how are integrators expected to decide when to set GRANTED for a given GCLID/WBRAID/GBRAID?
For example: - If our site already uses Consent Mode v2 and our CMP sets ad_user_data and ad_personalization, are we expected to copy those same values into the consent object of uploadClickConversions? Or does Google use the Consent Mode state internally, and we should only upload when we see that consent is GRANTED on our side? I just want to be sure we’re reading the right signals when deciding: - non-EEA user with consent → upload with GRANTED, - EEA user without consent → do not upload at all. Clear guidance on this mapping would help a lot. On Friday, November 28, 2025 at 4:05:23 AM UTC+4 (Deprecated) Google Ads API and AdWords API Forum wrote: Hi, Please find the answers below for your queries. *If we upload a ClickConversion for a user located outside the EEA/UK (e.g., a user in the United States) and we omit the consent object (or set it to UNSPECIFIED):* - No, you cannot omit the consent object irrespective of region (whether EEA/UK or outside the EEA/UK*). *That means you should populate the consent object when uploading the user data. That means the *consent setting applies to all users. * *I need to confirm if the GRANTED signal is a global technical requirement for the API to process data, or if the API logic checks the GCLID's region and allows non-EEA data to be processed even when consent is UNSPECIFIED or missing. * - *For EEA users: *For Customer Match lists to be used in EEA, both consent fields of ConsentStatus type must be set to “GRANTED” to indicate that you have received the required user consent. - *For users outside the EEA: *Here the consent depends on availability (GRANTED, UNSPECIFIED, or DENIED). If the consent status is set to “UNSPECIFIED,” it will be treated as missing consent. If you set the consent status as DENIED, you will get an error. As informed above, the consent setting applies to all users uploaded in a job, and advertisers should use separate jobs to upload users with different consent signals. This means *if there are non-EEA and EEA* user records in 1 job, and the consent status is sent as GRANTED, this GRANTED consent status is used for all records in that job. *Example:* we have two jobs that update a single audience; the first sends identifiers with *UNSPECIFIED* consent, and the second sends identifiers with *GRANTED* consent. In the example provided you would use two jobs—one for uploading users with *UNSPECIFIED* consent status for the ad_user_data and ad_personalization parameters and another job for users that have *GRANTED* consent status for the two consent parameters. Thanks & Regards, Google Ads API Support Team. On Monday, November 24, 2025 at 8:53:34 AM UTC+5:30 adsapi wrote: Hi, Please note that as per the document <https://www.google.com/about/company/user-consent-policy-help/#:~:text=As%20a%20publisher,in%20these%20countries> about the queries regarding EU user consent policy <https://www.google.com/about/company/user-consent-policy/>, this policy applies to end users in the EEA, the UK and Switzerland. The policy does not apply if Google services were removed from the website/app for users in these countries. Based on this, I can say that consent fields are only required for the above-mentioned regions and are not required to be provided for non-EEA users. Additionally, you can refer to the Help Center <https://support.google.com/google-ads/answer/14310715> article for more FAQs about the EU user consent policy for Customer Match upload partners. I hope this clarifies your concern. Please feel free to reach out for any further concerns/ queries. Thanks, [image: Google Logo] Google Ads API Team Feedback How was our support today? [image: rating1] <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=500Ht00001vTczSIAS> [image: rating2] <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=500Ht00001vTczSIAS> [image: rating3] <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=500Ht00001vTczSIAS> [image: rating4] <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=4&entry.295079254=500Ht00001vTczSIAS> [image: rating5] <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=5&entry.295079254=500Ht00001vTczSIAS> [2025-11-24 03:22:47Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vTczS:ref" (ADR-00339498) -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 "(Deprecated) 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/f1e7c6cc-4f24-4057-84d3-f805284c43e3n%40googlegroups.com.
