Sometimes an experience only makes sense if a visitor has already seen another one. Campaign Dependencies let you build that logic directly into your campaigns — no complex segment workarounds needed.
What are Campaign Dependencies?
A Campaign Dependency is a rule that controls whether a campaign can trigger, based on whether a visitor has (or hasn't) already been exposed to another campaign or experience.
You set them up in the Campaign Editor under Rules, and Made With Intent evaluates them automatically on every visit.
Best for: sequenced journeys, progressive messaging, and experiences that only make sense, or don't, given what a visitor has already seen.
A quick example
Say you're showing a free delivery message on your PDP to high-intent visitors. You want a follow-up message in the basket - but only for visitors who saw the original. A dependency rule makes that explicit
How dependencies work
When a visitor qualifies for a campaign, Made With Intent checks all dependency rules before it triggers. Every rule must be satisfied - they use AND logic.
Each rule has three settings:
Condition — did the prior campaign or experience trigger, or did it not trigger?
Scope — the window to look back across: Page, Session, or Journey
Type — does the rule apply to a whole Campaign, or a specific Experience within one?
How to add a dependency rule
Open the campaign in the Campaign Editor
Go to Rules in the left-hand sidebar
Click Add to create a new rule
Set the Condition — triggered, or not triggered
Set the Scope — Page, Session, or Journey
Set the Type — Campaign or Experience — then pick the relevant one from the dropdown
Click Add to save
Repeat for any additional conditions. Once rules are in place, they're visible directly in the editor - so anyone opening the campaign can see the logic at a glance.
A few things worth knowing
A campaign can have multiple dependency rules — all must be met before it triggers
Rules support both positive and negative conditions
Archived campaigns won't appear in the picker when you're selecting dependencies
Dependency rules are evaluated before campaign-level bucketing
When to use them
Dependencies cover a few distinct use cases — it's worth knowing which one you're solving for.
Sequencing with A/B testing Sequenced campaigns don't support A/B testing after the first step. Dependencies do. So if you want to show a discount on a PDP and then test whether showing the same message at basket adds value, you would use a dependency, not a sequence.
Suppression based on prior exposure Prevent a campaign from triggering for visitors who've already seen something related. Keeps messaging consistent and avoids repetition.
Progressive journeys Show a follow-up only to visitors who've already seen a selection of campaigns