Hi Roman,
Thank you for your follow up question. You may refer below for my responses :
Tell me please is it a right logic to work with multiple emails? Is it right that in this case (user_identifier_with_hashed_emails.hashed_email = self.normalize_and_hash(email) ) user_identifier_with_hashed_emails stores normalized and hashed emails after each iteration so that it is not overwriting each time?
When working with multiple emails, you may refer to this earlier
blog post, on how you can specify them as user identifiers. Also, it is correct that hashing should be performed per each email.
Second question: lets imagine a case when I uploaded a user list and then used this list as a segment in a specific ad in a random campaign. One day later I decided to refresh this segment with new contacts by deleting old contacts first and then uploading a new set of contacts. So the question is what is going to happen to an ad? Will it stop working because of this little time gap when contacts were removed? If so, how I can avoid it?
Our team specializes in the implementation and troubleshooting of the API's
customer match feature. What happens in production such as the ads' performances while changes are being applied (whether via the API or the UI) to the audiences, is unfortunately outside of our API team's scope. That said, for this item, I would recommend that you clarify this instead with the Google Ads Product Support team, via this
link.
I hope this helps.
Best regards,
 |
| Peter Laurence |
| Google Ads API Team |
|
|
| |

ref:_00D1U1174p._5004Q2fokJS:ref