Match rate is different between Google Ads API and Google Ads UI

[Dung Vien]

Hi adsapi team,

We are having an issue with match rate between Google Ads API and Google Ads UI

Reproduce steps:

1. Get raw data from local DWH with PHONE(in E.164 format) and EMAIL(with lower and uppercase) columns 

2. Hash both columns with SHA256 encryption without normalizing the email (yes, I'm aware that the doc told me to normalized it before hashing) and write to csv file

3. Manually upload the csv file to audience A  - got match rate of 91-100% and audience size of 1M-1.2M 

4. Using Google Ads API to upload the same csv file to audience B - got match rate of 81-90% and audience size is 760K - 850K

I've tried normalized the data before hashing, for the Google Ads UI it stay the same, but Google Ads API method drop drastically both in match rate and audience size

I got some problems with "429 Resource has been exhausted (e.g. check quota)" before, but i've fixed it by rerun "AddOfflineUserDataJobOperationsRequest" to the same "offline_user_data_job_resource_name", not sure if it cause some operations to miss out 

I can provide you the user list ids, request-response logs and the python script if necesary
Best regards,
Ryan

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry [https://groups.google.com/g/adwords-api/c/_n7CvrK96oQ] from the forum as it wasn't routed to our support queue.

Regards,
Carmela

Google Ads API Team

[Google Ads API and AdWords API Forum]

Hi Ryan,

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

With regards to your question, you mentioned that this is about an issue with the match rate between Google Ads API and Google Ads UI. Having said that, could you please provide an uncropped Google Ads UI screenshot and the complete request and response logs with request ID and request header generated on your end so our team can provide guidance accordingly? If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link. You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Furthermore, with regards to the 429 error, please see this API documentation for more information about the said error.

Regards,

Carmela

Google Ads API Team