Configure booking restrictions
Limit repeat attendance for one participant and know when to use generic Touchpoint Restrictions instead.
Stop one attendee from booking the same event over and over. This page covers the event's own attendance limits, when to use them, and when the broader Restrictions (number, frequency, time slots, validation codes) model fits better.
What the event editor controls
The Activity editor focuses on per-participant attendance limits. If your team also gates bookings with a validation-codes pool, treat that as a separate, specialized setup and confirm it before launch.
When this page matters most
Use the event's attendance limits when the rule is about how many times one participant may attend the same Activity.
Common examples:
- a kids activity that allows only one check-in per child per day
- a drop-in activation that allows at most three visits during the campaign
- a repeated session where one participant should not take every slot
Choose the right restriction level
If you just want to stop one person attending too often, set a per-participant limit inside the event. Use the table below to confirm you're in the right place.
| Need | Best place to configure it | Example |
|---|---|---|
| Limit repeat attendance for one participant on this Activity | Per-participant limits inside the event | One child may join the same workshop only once per day |
| Control how many people fit in one slot | Ticket capacity and slot setup | A VIP session with 8 seats per slot |
| Gate access with validation codes or broader Touchpoint rules | Restrictions | Invitation-only access to a private workshop |
Configuration
Decide where the rule belongs
Pick the path that matches your rule:
- Stay in the event when the rule is about repeat attendance on this specific Activity.
- Switch to Restrictions when the rule is about gated access, validation codes, or broader Touchpoint participation.
Set a per-participant limit
Use the per-participant counters to cap repeat attendance. You can set:
- a total cap for how many times one participant may attend
- optional daily and weekly caps when the same Activity repeats often
Choose a number that fits a real scenario
Base the limit on how the event actually runs. For example:
- a kids workshop might allow 1 per day
- a brand activation might allow 3 across the campaign
- a recurring VIP consultation might allow 1 total booking per participant
Keep broader Touchpoint restrictions separate
Set code-gated access, cross-Touchpoint rate limits, and general availability rules in the broader Touchpoint Restrictions model instead.
Keeping them apart makes it clear whether you're limiting event attendance, general Touchpoint access, or both.
If publishing is blocked
A few common reasons and how to fix them:
- The per-contact booking limit is 0 or invalid — set a positive number, or turn the booking limit off.
- The validation-codes restriction is on but no pool is selected — choose the intended pool, or remove that restriction.
See Validation & publishing for the full publish flow.
Related
Restrictions (number, frequency, time slots, validation codes)
Use the generic Touchpoint restriction model for broader access and validation-code rules.
Configure tickets (Booking + Check-in events)
Use ticket capacity when the rule is really about seats per slot.
Event types (Booking + Check-in vs. Check-in Only)
Revisit whether the chosen event mode matches the restriction you actually need.
Configure check-in (Self vs. Scan)
Coordinate attendance limits with the day-of check-in flow.