Restrictions
Limit who can participate, how often they can participate, and when a touchpoint is available.
Control who can take part, how often, and when — to protect prize budgets, keep things fair, and open a Touchpoint only during the window you want.
Before you begin
- The Touchpoint already exists in the campaign.
- You know whether you need to limit total access, per-participant access, time windows, or code-gated access.
Open the restrictions area
Open the Touchpoint in Build
Go to Build > Touchpoints, then select Configure on the Touchpoint you want to control.
Restrictions are set per Touchpoint, not once for the whole campaign.
Open Restrictions
Open the Restrictions tab for that Touchpoint.
This is where OmniLab groups participation limits, time-window limits, and code-based access rules.
Turn on the restrictions you need
Each restriction has its own switch. Turn on only the controls you actually need.
For numeric limits, enter the maximum allowed value. For time-window limits, add one or more time slots.
Save and validate
Save the Touchpoint, then run validation before publishing the campaign.
Restrictions are one of the most common places where limit conflicts and overlapping windows are caught.
Available restrictions
Each restriction answers a different "how do I cap this?" question. Pick the ones that match what you're protecting.
| Restriction | Use this when… |
|---|---|
| Total Participations | You want to cap entries across everyone — for example, the first 500 plays only. |
| Per Participant Limit | You want to cap how many times one person can take part — for example, 3 plays each. |
| Global Daily Restriction | You want to spread plays out over time — for example, 100 plays per day across everyone. |
| Global Weekly Restriction | You want a weekly ceiling across everyone — for example, 500 plays per week. |
| Daily Limit | You want each person to play a set number per day — for example, 1 play per day each. |
| Weekly Limit | You want each person to play a set number per week — for example, 3 plays per week each. |
| Time Slots Restriction | The Touchpoint should open only at certain times — for example, weekday lunchtimes. |
| Validation Codes Restriction | Only people with a code should get in — for example, codes printed on receipts. |
Keep the limits consistent
Your limits have to add up
When you combine limits, keep them logically consistent so a wider limit is never smaller than a narrower one inside it:
- Total Participations should be greater than or equal to the global weekly and global daily limits.
- Per Participant Limit should be lower than Total Participations.
- Per Participant Limit should be greater than or equal to Weekly Limit and Daily Limit.
- Global Weekly Restriction should be higher than Global Daily Restriction.
- Weekly Limit should be higher than Daily Limit.
- Every limit you turn on should be 1 or higher.
Time slots vs. reward timing
Time Slots Restriction controls when the Touchpoint itself can be opened.
It does not control when rewards are given out. That is handled separately through Attribution slots (simple & advanced).
If you're working with activities, keep that distinction in mind: Touchpoint restrictions are not the same as booking-slot configuration or booking restrictions. For that workflow, see Configure booking restrictions.
Validation codes and pools
When the Touchpoint shows Validation Codes Restriction, turn it on and choose a Validation Codes Pool.
Validation codes are managed as reusable pools rather than entered separately in each Touchpoint. The same idea appears in activity booking flows when bookings must be checked against a chosen pool.
If validation blocks this setup, follow the field names you see on screen first: OmniLab asks you to choose a pool, even when the message uses the broader phrase "validation codes".
If something's blocked
A few common restriction problems and how to fix them:
- The time slots restriction is on but no slots are defined — add one or more time slots, or turn the restriction off.
- Two time slots overlap — adjust the windows so they no longer overlap.
- A total or per-participant limit is zero or below — set any limit you've turned on to 1 or higher.
- The global weekly limit is lower than the global daily limit — raise the weekly value or lower the daily value so they add up.
- The per-participant total is higher than the global total — keep the per-participant limit below the global total.
- The validation codes restriction is on but no codes are set up — finish the validation-code setup or turn the restriction off.
Related
Key concepts glossary
Review the shared definitions behind touchpoints, scope, and validation codes.
Configure booking restrictions
Use the OmniLab Events-specific flow when the restriction belongs to bookings rather than generic participation.
Attribution slots (simple & advanced)
Separate touchpoint availability from reward-distribution windows.
Validation & publishing
See how restriction errors and warnings appear before publication.