Low Matching Rate with Looker Integration for Google Customer Match

[Ons Tizaoui]

Hi team,

we are facing an issue with Looker integration for google Customer Match, we've noticed significantly  lower matching rate compared to when we upload the data directly thorough the Google Ads UI.

With Looker integration,  where we are using hashed email addresses, our matching rate is currently 13%. However, when we manually upload the same data in Google Ads UI, we achieve a much higher matching rate of approximately 75%.

Best Regards,
Ons

[Ons Tizaoui]

any update on this ?

[Gjppy]

Hi Ons,

I have the same problem;

Were you able to solve it?

Regards

Gp

[Google Ads API Forum Advisor]

Hi,

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

Based on the information provided, I understand that you are facing issues with the low match rates for your audience list. Could you kindly confirm if you are uploading the audience data using the Google Ads UI or the Google Ads API? If you are using the Google Ads API, then you need to ensure that your upload job has completed before attempting to validate your match rate.

Your match rate might be lower than expected for a number of reasons, including:

• 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.

It's possible for an advertiser to reach anywhere from 1% to 99% of their list, based on how active their users are on Google Search, Gmail, or YouTube. For a more detailed guide on troubleshooting low match rates, visit the Help Center. I would recommend you to kindly refer to the "Troubleshoot customer list issues" documentation for more information. 

I would request you to provide the customer ID and the audience segment ID for further investigation. In order to investigate your issue further, kindly provide us with the complete API logs (request and response logs with request-id and request header) generated at your end and uncropped UI screenshot of the Google Ads account where you are facing the issue.

If you are using a client library and haven't enabled the logging yet, I would request you to 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. 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vEPf7:ref" (ADR-00260530)

Thanks,
 

Google Ads API Team