Match rate discrepancies

[seba...@movio.co]

Hi,

I've uploaded an audience with the size of 344,608 unique contacts. Google's API returns a match rate of 76% but 96,000 as the size for display and 120,000 as the size for search. None of those numbers explain the reported 76% match rate.

120000/344608 ~ 35%
96000/344608 ~ 28%
(120000+96000)/344608 ~ 63%

Could you please explain the difference?

[Google Ads API Forum Advisor]

Hi,

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

After reviewing your concern, I understand that you have an issue on the match rate discrepancies on contacts you have uploaded, Could you further elaborate on what exactly you are looking for the Google Ads API support team? If possible, please share the related screenshots or error screenshots for further investigation.

Kindly provide us with the complete API logs (request and response 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.!5004Q02pVPxX:ref"

Thanks,
 

Google Ads API Team

[seba...@movio.co]

I'm looking for an explanation how the match rate of 76% that the Google API returns gets calculated or is based on. Is it based on size_for_display, size_for_search, the sum of both or not related to any of those?

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

The match rate reported by Google Ads API is the percentage of customer information in your uploaded audience that could be matched to Google users. The match rate of 76%, which means that 76% of the customers in your uploaded audience could be matched to Google users. However, the size of your audience is 344,608 unique contacts, and the API reports the size of your audience for display as 96,000 and the size of your audience for search as 120,000.

In order to investigate further, kindly provide us with the uncropped UI screenshots of the issue where you are facing the discrepancy to assist you better.

[seba...@movio.co]

Ok, so I did another test and uploaded 2,135,065 unique contacts to a custom match audience. The match rate shows 73% so I would expected sizes of around 1.5M but the size is 530k-660k so clearly the match rate is computed differently. Are there any additional criteria for contacts to be contactable that are not included in the match rate computation?

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us. 

Kindly note that the Google Ads UI screenshot you provided was cropped, so I would kindly request you to provide an uncropped screenshot of the Google Ads UI. Since you are utilizing the Google Ads API for the purpose of uploading contacts to the custom match audience, kindly provide us with the complete API logs (request and response with request-id and request header) generated at your end to better assist you further.

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.

[seba...@movio.co]

Could you please just clarify if a contact needs to have logged in (Google, YouTube, etc) within the last X days to be targetable and that's why the actual match rate is way lower? 

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

In order to assist you further, please provide us the earlier requested uncropped screenshot of the Google Ads UI and the complete API logs (request and response with request-id and request header) generated at your end to better assist you further.