On Mon, Jun 10, 2024 at 10:42 AM 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum <[email protected]> wrote:
> 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 > <https://developers.google.com/google-ads/api/reference/rpc/v17/OfflineUserDataJob#status>, > the estimated match rate is available in the > operation_metadata.match_rate_range > <https://developers.google.com/google-ads/api/reference/rpc/v17/OfflineUserDataJob#operation_metadata> > 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 > <https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#verify-list>" > 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 > <https://support.google.com/google-ads/answer/7474166?hl=en-AU&ref_topic=10551093&sjid=2660027258571057863-AP>" > for more information. You can refer to this guide > <https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#usage-flow> > 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 > <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 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 > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging>, > .Net > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging>, > PHP > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>, > Python > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging>, > Ruby > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or Perl > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > 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, > > [image: Google Logo] Google Ads API Team > > > -- > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > 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 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 > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/adwords-api/ukeYk000000000000000000000000000000000000000000000SEUMGB005KVqLUQnTcyx1CG2AZu9kQ%40sfdc.net > <https://groups.google.com/d/msgid/adwords-api/ukeYk000000000000000000000000000000000000000000000SEUMGB005KVqLUQnTcyx1CG2AZu9kQ%40sfdc.net?utm_medium=email&utm_source=footer> > . > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/CAPg8tH53AVt1AtscDy0JR_LsUOTwR6ZRRC0WiHG6XFE7Z%2BAc5Q%40mail.gmail.com.
