Hi Team,
I understand, and we follow the same approach. However, my question is more
focused on the impact of adding multiple email addresses and phone numbers
for a single customer in a single row vs. separate rows, both in CSV
(manual) and API uploads.
Example CSV
Scenario 1: Single Row, Multiple Email and Phone Columns
Email, Email, First Name, Last Name, Country, Zip, Phone, Phone
t...@example.com, te...@example.com, Test, User, IN, 60000, 123456790,
1234567890
Scenario 2: Multiple Rows
Email, First Name, Last Name, Country, Zip, Phone
t...@example.com, Test, User, IN, 60000, 123456790 te...@example.com, , , ,
, 1234567890
For my understanding:
- *UserData* represents a single user in the customer list, which can
hold up to *20 UserIdentifiers*, each of type OneOf, either a
*hashedEmail*, *hashedPhoneNumber*, or *addressInfo* (but only one at a
time).
Please confirm whether the following scenarios are valid.
*Scenario A*:
- *CSV*: Single row with multiple email and phone columns.
- *API*: Single UserData with multiple identifiers (email and phone).
Example:
CSV: Email, Email, First Name, Last Name, Country, Zip, Phone, Phone
t...@example.com, te...@example.com, Test, User, IN, 60000, 123456790,
1234567890
API: UserData =
[
{
"hashedEmail": "hash('t...@example.com')"
},
{
"hashedPhone": "hash('123456790')"
},
{
"addressInfo": {
"hashedFirstName": "hash('Test')",
"hashedLastName": "hash('User')",
"countryCode": "IN",
"postalCode": "60000"
}
},
{
"hashedEmail": "hash('te...@example.com')"
},
{
"hashedPhone": "hash('1234567890')"
}
]
*Scenario B*:
- *CSV*: Multiple rows with email and phone for the same customer.
- *API*: Multiple UserData, each with unique identifiers but belonging
to the same customer.
Example:
CSV: Email, First Name, Last Name, Country, Zip, Phone
t...@example.com, Test, User, IN, 60000, 123456790
te...@example.com, , , , ,1234567890
API: UserData = [
{
"hashedEmail": "hash('t...@example.com')"
},
{
"hashedPhone": "hash('123456790')"
},
{
"addressInfo": {
"hashedFirstName": "hash('Test')",
"hashedLastName": "hash('User')",
"countryCode": "IN",
"postalCode": "60000"
}
}
]
UserData=[
{
"hashedEmail": "hash('te...@example.com')"
},
{
"hashedPhone": "hash('1234567890')"
}
]
Could you please confirm if both scenarios are valid? Any insights on how
the Google ads customer list processes these would be helpful and how it
would impact the match rate?
More like are both just the same when it comes to match rate of a customer
list
Note: Please ignore data validation and correctness this is just an example.
Thanks!
On Wednesday, December 11, 2024 at 12:11:38 PM UTC+5:30 Google Ads API
Forum Advisor wrote:
Hi,
Thank you for reaching out to the Google Ads API support team.
Kindly note that your match rates might be lower when you are trying to add
multiple user identifiers to a single userIdentifier object. Instead, you
need to add multiple userIdentifiers to a single UserData object as shown
in this code example
<https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#code_example>.
I would recommend you to refer to the Validate match rate
<https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/troubleshoot#validate-match>
guide for more information. Also, you can refer to this help center article
About
Customer Match match rates
<https://support.google.com/google-ads/answer/10534785?hl=en-GB&ref_topic=10551093&sjid=13702701222349285747-AP#>
for more information.
This message is in relation to case
"ref:!00D1U01174p.!5004Q02vGoPN:ref" (ADR-00278360)
Thanks,
[image: Google Logo] Google Ads API Team
Feedback
How was our support today?
[image: rating1]
<https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=5004Q00002vGoPN>
[image: rating2]
<https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=5004Q00002vGoPN>
[image: rating3]
<https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=5004Q00002vGoPN>
[image: rating4]
<https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/formResponse?usp=pp_url&entry.141427034=4&entry.295079254=5004Q00002vGoPN>
[image: rating5]
<https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/formResponse?usp=pp_url&entry.141427034=5&entry.295079254=5004Q00002vGoPN>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/3284d0be-07e8-46cf-8646-b127cf8bb274n%40googlegroups.com.
