Touchpoint dates override
Override campaign dates for one touchpoint while keeping its schedule inside the campaign window.
Give one Touchpoint its own start and end dates inside the campaign — so it can open later, close earlier, or run for just one phase, all on its own schedule.
Touchpoints follow the campaign schedule by default
A Touchpoint uses the campaign's dates unless you say otherwise. Turn on an override only when one Touchpoint needs its own start and end dates inside the campaign window.
By default, a Touchpoint follows the campaign schedule. To give it its own window, turn on Override Campaign Dates, set a start and end date inside the campaign dates, and optionally add custom before/after messages with Override Campaign Messages.
Before you begin
- Campaign dates are already set. If not, see Campaign dates.
- The Touchpoint already exists in the campaign.
Configure the override
Open the Dates tab
Open Build > Touchpoints, select Configure on the Touchpoint, then open the Dates tab.
This area uses the campaign schedule until you turn the override on.
Turn on Override Campaign Dates
Turn on Override Campaign Dates when the Touchpoint should not follow the full campaign window.
Use this when one Touchpoint starts later, ends earlier, or should be available only during a specific phase of the campaign.
Set Start Date and End Date
When the override is on, both Start Date and End Date are required.
Keep both dates inside the campaign date range. The override narrows the campaign window; it does not create a separate schedule outside it.
Add custom availability messages if needed
Turn on Override Campaign Messages when the Touchpoint needs its own visitor messaging.
Then fill Before Start Date Message and After End Date Message so the Touchpoint can show its own copy before it opens and after it closes.
Save and test the Touchpoint window
Save the Touchpoint and confirm availability behaves as expected.
Check both the open window and the before/after messaging, especially when the Touchpoint is available for only a short phase.
When a date override makes sense
Date overrides are most useful when:
- one Touchpoint should open later than the rest of the campaign
- one Touchpoint should close earlier
- several Touchpoints should go live in phases across one campaign
- the campaign uses a calendar-style experience where each Touchpoint needs its own date window
Special case: Advent Calendar
If the campaign uses an Advent Calendar layout, each linked Touchpoint needs its own date override, and the windows must not overlap.
That lets each calendar day unlock a specific Touchpoint at the right moment, instead of revealing all of them at once.
What happens when you turn the override off
Turning Override Campaign Dates off returns the Touchpoint to the campaign schedule.
If you need a Touchpoint-specific window again later, turn the override back on and recheck both the dates and the custom before/after messages.
If something's blocked
A few common date-override problems and how to fix them:
- The override is on but a required date is missing — set both Start Date and End Date, or turn the override off.
- An Advent Calendar Touchpoint still follows the campaign dates — turn on Override Campaign Dates for that Touchpoint and set its own window.
- Two Advent Calendar Touchpoints have overlapping dates — adjust the ranges so each one has its own non-overlapping window.
- The override falls outside the campaign window — keep both dates inside the campaign date range.
Publishing is also blocked for any Touchpoint override that falls outside the campaign window, even when both dates are filled.
Related
Campaign dates
Review the campaign-level schedule that Touchpoints follow by default.
Validation & publishing
See how touchpoint date issues appear before publication.
Advent Calendar layout
Understand the calendar layout that requires staggered touchpoint windows.
Configure slots: weekly vs. specific dates
Compare touchpoint date overrides with event-slot scheduling.
Attribution slots (simple & advanced)
Separate touchpoint availability from reward distribution windows.