Touchpoint dates override
Override campaign dates for one touchpoint while keeping its schedule inside the campaign window.
In this article, you'll learn how touchpoint date overrides work, when to use them, and how to configure a narrower touchpoint window than the campaign default.
Pattern B in practice
Touchpoints inherit the campaign schedule by default. Turn on an override only when one touchpoint needs its own start and end dates inside the campaign window.
Prerequisites
- Campaign dates are already configured. If not, see Dates (Pattern B).
- The touchpoint already exists in the campaign.
Configure the override
Open the Dates tab
Open Build -> Touchpoints, select the touchpoint, then open Dates.
This area inherits the campaign schedule by default until you deliberately turn the override on.
Turn on Override Campaign Dates
Enable 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 enabled, both Start Date and End Date are required.
Keep both values 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
If the touchpoint needs its own visitor messaging, turn on Override Campaign Messages.
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 the availability behaves as expected.
A good test is to verify both the open window and the before/after messaging, especially when the touchpoint is only available for 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 Advent Calendar layout, each linked touchpoint needs its own date override and the touchpoint windows must not overlap.
That allows each calendar day to unlock a specific touchpoint at the right moment instead of exposing 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 later need a touchpoint-specific window again, turn the override back on and recheck both the dates and the custom before/after messages.
Common validation issues
| Validation message | What it means | Fix |
|---|---|---|
Touchpoint '{{touchpoint_name}}' has date override enabled but is missing {{missing_field}} | The override is on, but one required date is empty. | Set both Start Date and End Date, or turn the override off. |
Collectible '{{collectible_name}}' used in advent calendar item {{item_index}} does not have date overrides enabled | A touchpoint linked to an Advent Calendar day is still inheriting the campaign dates. | Turn on Override Campaign Dates for that touchpoint and define its own window. |
Advent calendar collectibles '{{collectible_1_name}}' and '{{collectible_2_name}}' have overlapping date ranges | Two Advent Calendar touchpoints are available during overlapping periods. | Adjust the ranges so each touchpoint has its own non-overlapping window. |
Validation also blocks any touchpoint override that falls outside the campaign window, even when both dates are filled.
Related
Dates (Pattern B)
Review the campaign-level schedule that touchpoints inherit 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.