Marketing consent suppression list
A list of people who never gave marketing consent or have since opted out, so you can exclude them from every marketing send.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Install now1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Build the suppression list
Install nowBlu builds Segment
About this recipe
When to use it
One journey that ignores a revoked consent is a GDPR or CAN-SPAM problem waiting to happen. This builds the suppression segment directly from consent_granted/consent_revoked events so opted-out users are excluded everywhere, automatically.
What it delivers
Builds a marketing-consent suppression segment from consent_granted/consent_revoked events, excluding opted-out users from every marketing journey for GDPR/CAN-SPAM compliance.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“A list of people who never gave marketing consent or have since opted out, so you can exclude them from every marketing send.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
- 01Segment
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Build the suppression listBuild a segment of users named "Marketing Consent Suppression List". A user is in the segment when any of these is true: - they have never done the Subscribed consent event - they did the Unsubscribed consent event after their most recent Subscribed consent eventSegment
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /compliance-setup in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyAccounts at churn riskPaying accounts the health score has flagged as at risk, with no renewal deal in flight, so your CSMs can step in before they leave.View recipe Sid ChaudharyHealthy accounts with no open dealCustomer accounts with no open deal and account-level health attributes, plus per-user recent session activity, so AEs can review expansion whitespace.View recipe Sid ChaudharyDiscount-only buyersCustomers who have never bought anything without a discount code, so you can keep them out of full-price campaigns and protect your margin.View recipe 