Configure notifications by touchpoint
Use the per-object notification mode when different rewards or Touchpoints need different email content.
Placeholders in this article
This article contains placeholder screenshots. Search for placehold.co in this file and replace them before publishing.
In this article, you'll configure notifications per reward or per Touchpoint when one global email would be too broad.
Prerequisites
- You know which rewards or Touchpoints need their own email content.
- You can edit the campaign in
Build. - For booking notifications, the relevant activity already has booking enabled.
Before you switch
There is no fallback once you switch
Per-object mode does not inherit the global email. Any reward or Touchpoint you leave inactive or incomplete will not send that notification.
Configuration
Open the notification type
Go to Build -> Notifications, then open the notification type you want to configure.
Switch to the per-object tab
Choose the second tab for that type:
by RewardforWinner,Loser,Eligible, andReward Redeemedby TouchpointforTouchpoint Unlockedand booking-related notifications
Participate does not offer a per-object tab.

Activate each reward or Touchpoint you need
Expand each reward or Touchpoint and turn Active on for the ones that should send this notification.
Fill the email fields for each active object
For every active reward or Touchpoint, complete Email Subject Line, Email Preheader, Email Banner, and Email Content. Add Email CTA Label and Email CTA Link only when that email needs a button.
Save and review coverage
Click Save, then review the list again to confirm every reward or Touchpoint that should send this notification is active and complete.
Which tab appears for which type
| Notification type | Per-object tab |
|---|---|
Touchpoint Unlocked | by Touchpoint |
Winner | by Reward |
Loser | by Reward |
Eligible | by Reward |
Reward Redeemed | by Reward |
Booking Confirmation | by Touchpoint |
Booking Cancellation | by Touchpoint |
Booking Confirmation Reminder | by Touchpoint |
Booking-specific validation notes
Per-object mode uses the same field checks as the global workflow, plus booking-specific coverage checks:
| Message | Severity | Fix |
|---|---|---|
Activity '{{activity_name}}' has booking enabled but no booking confirmation notification is configured | Error | Configure Booking Confirmation globally or for that activity. |
Activity '{{activity_name}}' has booking enabled but no booking cancellation notification is configured | Warning | Configure Booking Cancellation globally or for that activity. |
Activity '{{activity_name}}' has booking enabled but no booking confirmation reminder notification is configured | Suggestion / Info | Add Booking Confirmation Reminder when reminder emails are needed. |
Booking confirmation reminder is enabled for '{{touchpoint_name}}' but no booking cancellation notification is configured | Error | Activate Booking Cancellation globally or for the same Touchpoint. |
See Configure notifications globally for the shared field validations that also apply here.
Related
Configure notifications globally
Use one email everywhere when the content does not need to vary.
Notification types reference
Check which notification types are reward-based and which are Touchpoint-based.
Email content, banners, CTAs
Review the shared email fields used inside each per-object configuration.
Validation & publishing
Understand how notification issues appear in the publish flow.