Thank you for your response here. We will look through our logs and get back to you on Monday after working with our dev team with complete API logs so we can continue investigate this.
Thank you, Emilia From: Google Ads API and AdWords API Forum <[email protected]> Date: Wednesday, March 12, 2025 at 4:10 PM To: Google Ads API and AdWords API Forum <[email protected]> Subject: Re: Low Match Rate - Customer Match External message, be mindful when clicking links or attachments Hi, I would recommend you to check these FAQs<https://urldefense.com/v3/__https:/support.google.com/google-ads/answer/14310715__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_Fzj8oxH$> and updates to consent mode<https://urldefense.com/v3/__https:/support.google.com/tagmanager/answer/13695607__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_JK8Q4-j$> for more details. This might also be one of the reasons for the low match rate for the uploaded customer match list. I would recommend you to refer to this Help Center<https://urldefense.com/v3/__https:/support.google.com/google-ads/answer/7474166__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_Bacq23X$> for a more detailed guide on troubleshooting low match rates. Additionally, you can refer to the Troubleshoot customer list issues guide<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/troubleshoot?Concierge__enable_concierge=false__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_IqeEz1y$> to help you troubleshoot low match rates and common errors that might come up in your Customer Match integration. In order to assist you further, kindly provide the complete API logs (request<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*request__;Iw!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_PY-J4DE$> and response<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/field-service*response__;Iw!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_KAx9vYm$> logs with request-id<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/call-structure*request-id__;Iw!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_O0kQUht$> and request header<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/concepts/call-structure*request_headers__;Iw!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_EhN4o3F$>) generated at your end when uploading the customer match list via the API so that we can validate the Ad User Data and Ad Personalization Consent status fields. If you are using a client library and haven't enabled the logging yet, I would request that you enable logging for the specific client library that you are using. You can refer to the guides Java<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/java/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_KWOE4UA$>, .Net<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/dotnet/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_Ed8xH01$>, PHP<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/php/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_PhoJcvs$>, Python<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/python/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_PSL0mVy$>, Ruby<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/ruby/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_FLFyRfS$> or Perl<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/client-libs/perl/logging__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_EcKgTzM$> to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag. You can send the details via Reply privately to the author option, or direct private reply to this email. Thanks, The Google Ads API Team. On Wednesday, March 12, 2025 at 9:49:51 PM UTC+5:30 [email protected] wrote: Hi Google Ads API, We are using Google Ads API to send our customer lists from Salesforce Data Cloud application. We just need someone from your team to review logs on Google Ads API side what values are coming through for Ad User Data and Ad Personalization Consent status fleds? We are suspecting that if the value is incorrect, that is impacting our low match rates? Please advice us who on Google Ads API side can support us with reviewing logs and confirm back to us? Thank you, Emilia On Wednesday, March 12, 2025 at 7:10:58 AM UTC-7 Google Ads API and AdWords API Forum wrote: Hi, Thank you for contacting the Google Ads API support team. As you have mentioned that you are using the Salesforce Data Cloud application in order to upload audience segments via the Google Ads API, I would recommend you to contact the Salesforce Data Cloud application support team as they are better equipped to address your concerns. This is because the logs that would have been generated while uploading the audience segments should be accessible by the Salesforce Data Cloud application support team. Based on those logs, the support team can confirm what value of consent was uploaded. Please note that our team only provides support for Google Ads API<https://urldefense.com/v3/__https:/developers.google.com/google-ads/api/docs/start__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_AehQjw-$> related concerns and technical implementations. As you are not directly using the Google Ads API, your concern is out of scope for our team. With respect to your query “We are uncertain if a True/False value would suffice or if the value needed to be 1 or 0. OR does the value need to be GRANTED.”, the answer is that the value should be GRANTED. Thanks, Google Ads API Team On Wednesday, March 12, 2025 at 11:36:36 AM UTC+5:30 [email protected] wrote: We are having issues with audience segments we are sending over from Salesforce Data Cloud application via API. The segment size in source system are all well above 10k+ but when they appear in Google Ads, majority shows under 100 matched people. We read up on the Ad User Data and Ad Personalization Consent status here: https://support.google.com/google-ads/answer/14546648?hl=en<https://urldefense.com/v3/__https:/support.google.com/google-ads/answer/14546648?hl=en__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_A1VVuDn$> and your documentation explicitly states that both of those fields need to be set to ‘GRANTED’ in order to convey consent. For these segment ids: 8958423270, 8971324011, 8974875564, can you confirm to us what values are coming through from Data Cloud to Google Ads for Ad User Data and Ad Personalization Consent status? We are uncertain if a True/False value would suffice or if the value needed to be 1 or 0. OR does the value need to be GRANTED. This is not clear in any documentation and it is difficult for us to identify if our low match rate is a result of the values we are sending in these fields that don’t align with what Google can ingest. Thanks, -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/<https://urldefense.com/v3/__https:/googleadsdeveloper.blogspot.com/__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_Lq9sxCN$> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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<https://urldefense.com/v3/__http:/groups.google.com/group/adwords-api?hl=en__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_MCZ5bOD$> --- You received this message because you are subscribed to a topic in the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/fY7pqKrtgmM/unsubscribe<https://urldefense.com/v3/__https:/groups.google.com/d/topic/adwords-api/fY7pqKrtgmM/unsubscribe__;!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_AU5For0$>. To unsubscribe from this group and all its topics, send an email to [email protected]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/adwords-api/eb34ab17-115f-4664-9e4f-5b5b0608c0d0n%40googlegroups.com<https://urldefense.com/v3/__https:/groups.google.com/d/msgid/adwords-api/eb34ab17-115f-4664-9e4f-5b5b0608c0d0n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!HrbR-XT-OQ!TCn4Fp4dACnAjVtjhK0dWkNQ7VNhMQG10q70HwY4E1AKO6UOpLnzmnFShlKoEYcrLqwROKFvUtzYFj-C_I1CCwPO$>. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/IA1PR12MB95221203BCC07DBD0E35C5F1B2D32%40IA1PR12MB9522.namprd12.prod.outlook.com.
