How settings work across campaigns and touchpoints
Four patterns tell you whether a setting is set once, per touchpoint, or built once and linked.
Almost every OmniLab setting follows one of four patterns. Spot the pattern, and you know where to set it and what the touchpoints inherit.
| Pattern | What it means | Examples |
|---|---|---|
| Off, campaign or touchpoint | You choose Disabled, Campaign Level or Touchpoint Level | Opt-in, participation form, notifications |
| Campaign default, touchpoint exceptions | Touchpoints inherit the campaign's value and can narrow it | Dates |
| Campaign only | One setting for the whole campaign | Acquisition form |
| Build once, then link | Create it once, attach it where it's used | Rewards, badges |
Off, campaign or touchpoint
The default is Disabled. Campaign Level gives the whole campaign one setup. With Touchpoint Level, each touchpoint needs its own complete setup: nothing falls back to the campaign's. In notifications, the same choice reads Global or by Touchpoint.
Campaign default, touchpoint exceptions
The campaign's dates are the outer limits. A touchpoint can have its own dates, but only inside them: it can't open before the campaign starts or stay open after it ends. See Touchpoint dates override.
Campaign only
The acquisition form, the sign-up every participant goes through, is the same everywhere in the campaign, so sign-up and consent stay consistent.
Build once, then link
A reward or a badge is created once for the campaign, then linked to the touchpoints that hand it out. Change it once and every touchpoint gets the change.
Where to find each setting
| Setting | In Studio |
|---|---|
| Opt-in | Build > General > Terms & Conditions Settings |
| Participation form | Build > General > Participation Form |
| Dates | Build > General > Campaign Dates Settings |
| Notifications | Build > Notifications |
| Acquisition form | Build > Settings > Campaign Translation |
| Rewards | Build > Rewards |
| Badges | A touchpoint's Gamification tab |