Hi,

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

Regarding ‘low match rate’, there might be various reasons (normalization 
issues, matching process time delay, etc). Ensure that your upload job has 
completed before attempting to validate match rate.

Please refer to the below troubleshooting steps to deal with the match rate 
issue.

The data was not hashed before it was uploaded.
The data was not correctly formatted before it was hashed.
You are comparing against match rates in a different system.

Also, please be aware that starting on March 6, 2024, if consent is missing for 
EEA users, then the consent value is determined as not consented. Data from 
unconsented EEA users won't be processed and cannot be used for ad 
personalization using Customer Match. See FAQs and updates to consent mode 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 for a more detailed guide on troubleshooting low match rates. 
Additionally, you can refer to the Troubleshoot customer list issues guide 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 
and response logs with request-id and request header) generated at your end 
when uploading the customer match list via the API.

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, .Net, PHP, Python, Ruby or Perl 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,

Google Ads API Team


Feedback
How was our support today?


[2025-02-25 06:45:58Z GMT] This message is in relation to case 
"ref:!00D1U01174p.!5004Q02vH3j8:ref" (ADR-00289654)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/mmH2o000000000000000000000000000000000000000000000SS884N00gnzphtUeSqWRTaFcspdpSg%40sfdc.net.
  • Is... Swat Google App
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
      • ... Swat Google App
        • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to