Hello Kurt, I've been working on this API for many years, so I'm jumping in here to help out. First, I'll explain the Customer Match attributes flow and how it is used. Then, I'll cover my observations in your particular case followed by the next steps.
Customer Match attributes flow This is what I know about the feature when it was first introduced in, I believe, 2020. Customer Match attributes are not tied to a specific user list. API developers upload Customer Match attributes through an offline data job not tied to a user list. Then, those Customer Match attributes sit in a pool on the Google Ads account. Finally, rule-based user lists are created using that pool of Customer Match attributes. Even though the feature is similarly named to Customer Match, it is not tied to Customer Match lists. I realize that this can be confusing, but as a fellow engineer, I'm sure you know how difficult naming can be. I'm planning on updating the guide on this. You're probably wondering why it appears almost no one knows anything about this feature. This is because this feature has historically been allowlisted with very, very few people on that allowlist who qualify to be on it. That's why the documentation for this feature is sparse. I'm sure you're also wondering why it isn't working for you, so I'll get to that now. Observations I took a deep-dive through our source code, back-end database, and logs. This is what I found: This feature is still allowlisted, and your Google Ads account is not on the allowlist. When you uploaded data through the offline data job, you set the user list in the customer match metadata. When uploading Customer Match attributes, that field should not be set. By setting that user list field, it appears that our validator for the Customer Match attributes feature may not have triggered, which allowed the job to proceed. When you uploaded the data, the job attempted to process the data. I see that the data uploaded and processed. However, because your account is not on the allowlist for the feature, the account was not able to do anything with that feature. Also, it's expected that Customer Match attributes are not tied to any user list, so it's expected that the user list you have would be empty. Next steps So, here's what we can do next. I'll update the documentation to make it more clear on how the Customer Match attributes feature works, and I'll make it more clear that there is allowlisting associated with that feature. I'll follow up with one of my fellow engineers to verify that it is indeed the validator logic for the allowlist not being triggered for this edge case. If that is indeed the case, then that will be updated. If you would like to be on that allowlist, you would first need an account manager. If you have an account manager, then you can talk to them about requesting to be added to that allowlist. I'm not sure what all the qualifications are since I'm not involved with the allowlisting process for that feature, but I do know there are very few developers on there, so the qualifications may be high. Regards, Nadine Wang Google Ads API Team ref:_00D1U1174p._5004Q2TjyJH:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 on the web visit https://groups.google.com/d/msgid/adwords-api/4u8z9000000000000000000000000000000000000000000000R5XO3I00c7dLgemmR4aJdOJFWHMvjA%40sfdc.net.
