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* <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 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 <https://developers.google.com/google-ads/api/docs/client-libs?hl=en>. 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 [email protected] alias instead. Furthermore, with regards to the 429 error, please see this API documentation <https://developers.google.com/google-ads/api/docs/best-practices/quotas#grpc_limitations> for more information about the said error. Regards, Carmela Google Ads API Team On Friday, November 25, 2022 at 12:11:26 PM UTC+8 Dung Vien wrote: > 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 > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 on the web visit https://groups.google.com/d/msgid/adwords-api/d1f5c13d-e2ea-4ad5-aaef-ef69ca398cb5n%40googlegroups.com.
