Hi,

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 refer to the Verify list upload and match rate guide for 
more information.

Make sure your upload job is complete before attempting to check your match 
rate. Several factors can contribute to a lower-than-expected match rate, 
including:

The data was not hashed prior to uploading.
The data was improperly formatted before hashing.

Advertisers can reach anywhere from 1% to 99% of their list, depending on how 
active their users are on Google Search, Gmail, or YouTube. I would recommend 
you to refer to the Validate match rate guide for more information.
As you are not seeing the match rate, can you confirm if you are passing the 
consent field of customer_match_user_list_metadata in your OfflineUserDataJob 
create requests.
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 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.
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.!5004Q02vGiae:ref" 
(ADR-00274656)

Thanks,

Google Ads API Team


Feedback
How was our support today?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@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 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 adwords-api+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/adwords-api/QyVBF000000000000000000000000000000000000000000000SON3L600-bg2Sr5jTWCiOLQM-ieRBA%40sfdc.net.
  • Re... Ajith Pandian
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
    • ... shelby hughes

Reply via email to