26/06/25: Campaign Manager & Segment Execution Improvements
26/06/25: Campaign Manager & Segment Execution Improvements
Today we're excited to announce the launch of further advancements to our Campaign Manager, and some changes to Segment Executions.
What's New?
Fire multiple experiences within a single campaign
Our new Multi Experience feature lets you decide whether a visitor can see more than one experience within a campaign. You can also choose how often visitors get re-bucketed; per event, per page, or per session.
New controls for how campaigns run together
From now on, all campaigns will fire concurrently by default. But if you need more control, you can create exclusion groups.
Any existing campaigns have been placed into a default exclusion group, but you can adjust this at any time.
Segment Executions → Third Party Triggers
We’ve renamed and relocated segment executions. They now live within Campaigns as a new experience type called Third Party Triggers. This change makes it easier to manage and control these experiences in your other platforms [Learn how to build campaigns with Third Party Triggers here]
Exclude campaigns from the Holdback Group
By default we have a holdback group of 10% of visitors who will never see a Made With Intent campaign. This is to allow you to report on the value MWI is driving for your business. However we know you may want 100% of a segment to see a campaign, and so you can now exclude campaigns from the Holdback group in the Global Rules of a campaign