Building Your Sale · JBFOne Knowledge Base
Tickets Rules
The Tickets section of your event checklist is where you manage the registration ticket types available to consignors. By adding rules, you can show or hide ticket types, adjust pricing, add waivers, block registration, or trigger emails — all based on who is registering and how they arrived at your sale.
What this article covers
- What Tickets rules can do
- How to build a custom rule from scratch
- How OR group conditions work
- Available actions and when to use each
- Pre-built templates available in this section
- Frequently used rule setups
How to Add a Rule
Where to find it: Event Checklist → Tickets → Rules tab
- Click Add a rule to open the rule builder
- Select Start from scratch — build a custom rule to build your own
- Or choose a pre-built template to start with a partially filled structure
The Tickets rule builder includes an optional Description field — use it to leave a note about the rule's purpose for your own reference.
Walkthrough — Show a Ticket to a Social Media Audience
This rule shows a specific ticket type only to consignors who arrived at your registration page through Facebook or Instagram. It is a clean way to offer a social media exclusive ticket — an early bird rate, a promotional tier, or any ticket you want visible only to that audience.
The key feature of this example is the OR group — either condition can be true for the rule to fire. A consignor arriving from Facebook qualifies. A consignor arriving from Instagram also qualifies. Both conditions point to the same action.
- Click Add a rule → Start from scratch — build a custom rule
- Rule name: Show ticket by audience
- Priority order: [your priority number]
- Active: checked ✓
Pro Tip: Set priority order in increments of 10 (10, 20, 30) rather than single digits. This leaves room to insert new rules between existing ones later without renumbering everything.
Conditions — OR group (any condition must match):
Click + Add OR group to create the group, then add both conditions inside it.
Condition 1:
Context: Tracking link
Field: UTM Source
Operator: equals
Value: Facebook
Condition 2:
Context: Tracking link
Field: UTM Source
Operator: equals
Value: Instagram
Then do this:
Action: Show ticket
Ticket: [select your ticket type]
- Click Save rule ✓
Consignors who arrived through any other source will not see this ticket type. Those who came from Facebook or Instagram — regardless of which one — will.
Pro Tip: UTM Source values are case-sensitive. If your tracking links use lowercase values, your Value field must match exactly. Check your tracking link setup before saving the rule.
How "OR Groups" Work
An "OR group" means any condition inside it can match — only one needs to be true for the group to qualify.
- Condition 1 alone would show the ticket only to Facebook traffic
- Condition 2 alone would show the ticket only to Instagram traffic
- Together inside an OR group, either source qualifies — broadening the match without creating two separate rules
Pro Tip: Use OR groups when multiple paths should lead to the same outcome. Use AND groups when you need a registrant to meet all criteria simultaneously.
All Available Actions in This Section
- Show ticket — makes a ticket type visible only to registrants who meet the conditions. Select the ticket from your saved ticket types.
- Hide ticket — removes a ticket type from view when conditions are met.
- Set price of — overrides the ticket price for qualifying registrants. Select the ticket and enter the new price.
- Set fee of — overrides the fee associated with a ticket for qualifying registrants. Select the ticket and enter the new fee amount.
- Add waiver — attaches a waiver to the registration when conditions are met. Select the waiver ID from your waiver library.
- Block registration — stops the registration entirely and displays a custom message to the registrant. Enter your reason in the Value field.
- Send email — triggers an email to the registrant. Select the email template from your template library.
You can add multiple actions to a single rule using + Add another action.
Pro Tip: Block registration is most effective when paired with a clear, helpful message. The Value field is what the consignor sees — write it as a direct explanation, not a system note.
Available Templates in This Section
- Give a discount based on history — reduce the price for returning or loyal registrants
- Show a ticket to specific registrants — only show a ticket type when conditions are met
- Hide a ticket based on an answer — remove a ticket when a question is answered a certain way
- Block registration — stop registration with a custom message
- Send a custom confirmation email — send different emails based on ticket type or history
- Send a reminder email — remind specific registrants before the sale
Note: Templates pre-fill the rule structure but use the same rule builder. You will still select your specific tickets, conditions, and values before saving.
Frequently Used Rule Setups
Show a ticket to registrants from a specific source
Context: Tracking link
Field: UTM Source
Operator: equals
Value: [your UTM source value]
Action: Show ticket → [select your ticket]
Tickets rules give you precise control over who sees what — and what they pay — without building separate registration flows.
Next Steps
- LINK TO SCHEDULE RULES ARTICLE
- LINK TO QUESTIONS RULES ARTICLE
- LINK TO RULES OVERVIEW ARTICLE
Last Updated: SW — 05/01/2026