+2Hi there,
we are new the Klaviyo yeah.
just looked through the predefined lists and saw a lot of @marketplace.amazon.com emails which have been imported, but don't have double opt-in.
how can I make sure those ppl don't get a email?
we are switching from DRIP to Klaviyo and want to start with a fresh install :)
Elenio
Best answer by retention
Here’s a quick screenshot of this:
Marketing Segment Excluding Amazon Emails
Segment of Amazon Emails
If you go with method #1, then you can just use that segment for all Campaigns and it will exclude Amazon emails automatically.
If you go with method #2, then you have to make sure to exclude those emails every time you send a campaign. The benefit of this is you will have the option, for whatever reason, to use that Segment separately as an audience to send emails to - or if some campaigns (that are allowed by Amazon) you can choose to not exclude them.
I imagine method #1 is more practical, and you can always create the segment for Amazon emails should you ever need to send ot them separately.
Hope this helps!
+62Here’s a quick screenshot of this:
Marketing Segment Excluding Amazon Emails
Segment of Amazon Emails
If you go with method #1, then you can just use that segment for all Campaigns and it will exclude Amazon emails automatically.
If you go with method #2, then you have to make sure to exclude those emails every time you send a campaign. The benefit of this is you will have the option, for whatever reason, to use that Segment separately as an audience to send emails to - or if some campaigns (that are allowed by Amazon) you can choose to not exclude them.
I imagine method #1 is more practical, and you can always create the segment for Amazon emails should you ever need to send ot them separately.
Hope this helps!
+1This isn’t really feasible if you have multiple dynamic segments you’re using for targeting. We’ve got 8-10 different domains we need to block like Amazon, Indeed, ebay and others. If you only send to 1 segment you’re spamming most likely and not using Klaviyo properly and leaving money on the table which is a bigger problem.
Klaviyo support, please setup a global blocked domain feature so we don’t have to build out elaborate segments unnecessarily every time just to have a clean send.
+4You need to create a segment like this
+1Thanks for the response
Yep, already did but it’s unclear if when you action the “suppress” feature for that segment if it’s going to suppress future peeps that are added to the segment…
+8
If your goal is to truly suppress emails for a set of domains on an ongoing basis (i.e. you never want to message them), I would recommend (1) doing a one-time suppression of the segment using the button in your screenshot and (2) setting up a segment-triggered flow (using the segment you defined) that suppresses new users with these kind of emails using a flow webhook calling Klaviyo’s APIs. See https://www.klaviyo.com/blog/solution-recipe-9-use-klaviyo-flow-webhooks-to-automate-suppressions-using-segments-and-klaviyos-apis for a guide on this. The reason to avoid doing the flow + back-populating is you’ll likely hit API rate limits for your initial set.
Cadence / Book a demo
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
