Customer Match - USER IDs - Way too low since March 2024

[Vishnu Vankayala]

Hi,

We've been facing issues with Customer Match rate with User IDs. We've uploaded 100K user ids and match rates show around 40%..

However the list size says only 2000.

Similarly we do send the consent parameters along with the USER ID when we upload the excel sheet in the UI, we don't have options to upload the consent paramters.

Could you explain what is the right way to upload the data?

[Vishnu Vankayala]

Update:

When we upload without the consent the same USER IDs we've higher match rates. 

[Google Ads API Forum Advisor]

Hi,

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

I understand that you are experiencing issues with Customer Match rates, as the User IDs are showing low match rates. Kindly note that once the OfflineUserDataJob has a SUCCESS status, the estimated match rate is available in the operation_metadata.match_rate_range field. If you query this field before the job completes, the value in this field might be zero. To ensure your match rate is ready for verification and the list ready for targeting, we recommend polling the job for completion. It can take as little as 10 minutes or up to 24 hours for the job to complete. I would recommend you to kindly refer to the "Verify list upload and match rate" documentation for more information. Also, I would suggest you to refer to this help center article "Fix Customer Match issues with list upload, small list size or low volume" for more information. You can refer to this guide for more information on how to properly pass consent when using the Google Ads API.

Could you kindly confirm whether you are using Google Ads UI or the Google Ads API for uploading the customer match data? If you are using API, 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 (with visible customer ID) of 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.!5004Q02tJGMS:ref" (ADR-00239209)

Thanks,
 

Google Ads API Team

[Vishnu from CustomerLabs]

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@googlegroups.com
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 a topic in the Google Groups "Google Ads API and AdWords API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/NZaikhnuISk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adwords-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/ukeYk000000000000000000000000000000000000000000000SEUMGB005KVqLUQnTcyx1CG2AZu9kQ%40sfdc.net.

[Google Ads API Forum Advisor]

Hi,

Please note that we didn't receive the earlier requested information. In order to assist you further, could you confirm whether you are using Google Ads UI or the Google Ads API for uploading the customer match data?

[Jiiva]

We are using the Google Ads API to upload a customer list. When we upload via the API, we get only 18k matched users. However, when we use the same user list and upload it manually via the UI, the match count is around 41k.

During the manual upload, I was not prompted to provide consent, but we included consent when uploading via the API.

We have double-checked our API implementation, and it works perfectly according to the documentation.

Is there an issue with the API? Could there be a reason for this discrepancy?

[Vishnu Vankayala]

any update on this pls?