User List - CRM User Data

[Ajith Pandian]

Hi,

We are trying to send audience data via userLists API and updating the users via uploadUserData.

Create User List:



Upload User Data:

Audience Dashboard:

We have waited more than 48 hours to see the user data.
We do not see uploaded user data or count.

Where can we see the uploaded user data and confirm that the users are uploaded correctly?

Can you please help us in this?

Thanks,
Ajith

[Google Ads API Forum Advisor]

Hi Ajith,

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

I understand that you are unable to view the customer match data uploaded via the Google Ads API in the UI dashboard.

From the screenshots provided, it appears that you are using the UserDataService to upload the customer match data. Note that uploads made through this service will not be visible under the 'Segment members' section for the Customer Match List in the Google Ads UI. This is documented in this guide. Also, keep in mind that it may take several hours for the list to be populated with members. Additionally, a list could appear smaller than expected when viewed in the Audience Manager from the Google Ads UI. This view shows the number of "active users" in the list. For more information, see this troubleshooting guide. 

From the API logs, it appears that you are not setting the consent. Starting with version v15 of the Google Ads API, you should populate the consent field of customer_match_user_list_metadata in your UploadUserDataRequest create requests. For remove requests, consent is not needed. If consent is missing for EEA users, then the consent value is determined as not consented. Data from unconsented EEA users won't be processed and cannot be used for ad personalization using Customer Match. We recommend that you use the OfflineUserDataJobService if you're using the API to manage user lists that are also managed in the UI.

If you still are not able to find enough reasons why the data is not visible in the UI, provide us with your customer ID and the request-id generated at your end while uploading the data.

If you are using the REST interface requests and haven't enabled the logging yet, you can do so via the curl command by using the -i flag.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGiae:ref" (ADR-00274656)

Thanks,
 

Google Ads API Team

[Ajith Pandian]

Hi,

Since we have sucess response for all the requests, we do not have request-id. and the customer ID is 7254285515.

[Google Ads API Forum Advisor]

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:

1. The data was not hashed prior to uploading.
2. 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?

               

[shelby hughes]

Hi, could any of you donate to my GoFundMe if I share it with you? I'm just trying to get my life back after disasters 😔 I have nobody to turn to.

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 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...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/adwords-api/c4dc5eab-01fa-42f6-a40c-b2ef7a5a27c1n%40googlegroups.com.