Hi,
I hope you're doing well. I wanted to follow up on the issue regarding the low match rate. Have there been any updates on this? Please let me know if any further details are needed from my side. Looking forward to your response. Best regards, Carlos Vicente On Tuesday, February 25, 2025 at 6:46:32 AM UTC Google Ads API Forum Advisor wrote: > 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* > <https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/troubleshoot#validate-match> > . > > 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* > <https://support.google.com/google-ads/answer/14310715> and *updates to > consent mode* <https://support.google.com/tagmanager/answer/13695607> 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://support.google.com/google-ads/answer/7474166> > for a more detailed guide on troubleshooting low match rates. Additionally, > you can refer to the *Troubleshoot customer list issues guide* > <https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/troubleshoot?Concierge__enable_concierge=false> > > 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://developers.google.com/google-ads/api/docs/concepts/field-service#request> > > and *response* > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > > logs with *request-id* > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > > and *request header* > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>) > > 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* > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging>, > *.Net* > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging>, > > *PHP* > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>, > *Python* > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging>, > > *Ruby* > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or *Perl* > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > 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, > > [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=5004Q00002vH3j8QAC> > > [image: rating2] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=5004Q00002vH3j8QAC> > > [image: rating3] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=5004Q00002vH3j8QAC> > > [image: rating4] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=4&entry.295079254=5004Q00002vH3j8QAC> > > [image: rating5] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=5&entry.295079254=5004Q00002vH3j8QAC> > [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/8067f77d-f21b-4c61-8962-8ac882b211b0n%40googlegroups.com.
