Hi all,
We currently have an issue where we can't seem to suppress email addresses from campaigns and canvases. We have used the re-targeting options (i.e those who have received a message etc) but the issue with this is it manages it at a profile level - not email level.
The challenge we have is that many of our users share email addresses across profiles and its not possible to merge them. We have multiple campaigns sending per day and need to be able to control the amount of emails an email address receives NOT necessarily the profile.
As an example ..
Using the current re-targeting options, we would be able to ensure that User A only receives one message, but the email address would receive 2 (one for User A from Campaign 1 and then one for User B from Campaign 2).
We need an easy way to orchestrate this within Braze, but the only way we think we can manage this is by passing delivery logs back to our warehouse then passing back through as an attribute .. which isn't ideal with the data delays around that!
Has anyone got any ideas / worked around the issue?
That is correct, you send to a user not an email address.
It also dedupes email in a campaigns, so even if there are multiple users with the same email address, only 1 email is sent which could also be problematic depending on your message purpose and needs.
The best practice is to have email unique per user, but it seems that won't work for you.
The duplicate users (multiple users with the same email address) are they different types of users / services? If so, you could split into different apps/workspaces
Another option would be to send triggering events to a braze endpoint to send the messages.
Alternatively, in this case: User A and User B qualifies for Campaign 2
You add a custom attribute when sent to the use record and loop the sending checking for the attribute.
LiamG In the scenario you described:
What is your desired outcome?
When both User A and User B share the same email address, we don't see how the two users can be distinguished from an Email Recipient perspective. But maybe your desired outcome could help clarify how we might be able to achieve this.
An interesting use case for sure! Would love to learn more about it!
