Logic Rules (Attendee Form)

Introduction

Logic Rules are simple or complex rules that control the display and processing of registration forms.

Logic Rules are used by Planners to create highly customized online registration forms based on the specific needs of the event registration process.

A logic rule belongs to only one form, but a form may have many logic rules.

Videos:

• All Logic Rules videos
• Using Logic Rules to: Assign Attendee Types (2:54)
• Display a Custom Question (3:06)
• Send Email to a Third Party (4:22)
• Hide the Additional Reg Button (4:32)

An Overview of Logic Rules:

• The basis of a Logic Rule is an action that will occur on a form IF a set of conditions is met.
• The condition can be to "always apply," but the condition is usually at least one IF clause, often one or more clauses joined by AND / OR conjunctions.
• The action can be thought of as a THEN clause after the conditions; that is, what happens after the conditions are met.
• For example: IF {the attendee type} {equals} {Exhibitor} THEN {Display Questions} {Exhibitor-only Questions}.
• A Logic Rule can include many levels of conditional clauses, such as: IF {email address} {does not end with} {"@certain.com"} AND {company} {contains} {"certain"} OR {position} {contains} {"certain"} THEN {Assign Attendee Type} {Certain Inc. Employee}.
• An infinite variety of combinations can be used to create forms as complex as needed in order to accurately collect the event's registration data online.
• When an attendee modifies their information, Certain undoes any logic-based actions that resulted from the original answer. For example, if the registrant selects "Manufacturer" as their business type, and that answer results in a $30 registration fee, then if they change their business type to "Retail," the $30 fee will be removed.
• This "undo" action occurs on the verify/edit, payment, and confirmation pages of the registration form.
• Note: Logic Rules are created here, but a logic section must be included in the online form setup in order for the logic to be processed in the form.

List and Labels

The Logic Rules set up for the current form are listed here. This list may span multiple pages.

Click edit in the Actions column to view or modify a rule.

Click copy in the Actions column to make an exact copy of a rule.

Click Add New to add a new logic rule.

Whichever option is clicked, the Logic Rule Details page is displayed, with the Conditions and Actions sections in which the logic rule is described under List Rule Details below.

Labels for Form Sequence: Each logic rule must be assigned to a form Section on which it will be processed in the online form sequence (defined on Form > Setup). A form may include up to 20 logic sections, and any number of rules may be processed on a single section. Rather than use the default section labels of "Logic 1," "Logic 2," etc., a custom Label and Description can be defined for each one. These are what you see when adding logic sections to the form and setting their online sequence, on Form > Setup. For example, the label could be renamed to "Assign Attendee Type & Display Error," making the purpose obvious. This eliminates the need to toggle back from Form Setup to this Logic Rules section to remember what action the rules in a Logic section perform.

Logic Rule Details (Attendee Form)

Details and Conditions

List Rule Details

• Name – (Required.) A descriptive name for the rule. This name should describe the condition and the action that will follow; for example, "Display exhibitor questions to exhibitors (attendee type)".
• Section – Select the section on the form on which the rule will be processed. (Logic 1, Logic 2, etc.) A form may include up to 20 logic sections, and any number of rules may be processed on a single section.
• Processing Order – The order in which the rule is processed relative to other rules in the same Section. (1, 2, 3, etc.)

Conditions

• Always apply – The specified action will always be applied. No further "Conditions" detail is required. Complete the details for the Actions.
• Apply ONLY if these conditions are met – The specified action will only be applied if the condition(s) evaluate to "True." The condition(s) begin with an IF. A question/data field, a comparison operator, and an answer value are selected.
• Question / Data Field – Select a question or field from the list. Options may include Standard Profile Fields, Custom Profile Fields, Standard Registration Fields, Registration Payment Fields, Custom Registration Fields, Custom Travel Fields, and other fields such as Group, Promo Code, or Today. The available fields depend on enabled modules for the event.
• Comparison Operator – The operator compares the contents of the data field with the option entered into the Answer Value field. Operators include:
• =
• <>
• >
• <
• >=
• <=
• begins with
• ends with
• contains
• does not begin with
• does not end with
• does not contain
• is one of
• is not one of
• is blank
• is not blank
• Answer Value – In this unlabeled field to the right of the comparison operator, enter the value to be compared. This field is not displayed if the operator is "is blank" or "is not blank".
• Conjunction – If more than one condition is required, select AND or OR from the unlabeled drop-down after the Answer Value. A new set of fields appears to add more conditions. Conditions can be combined with more than one condition.

Rules with Identical Conditions

Warning: Do not include two logic rules with identical conditions on the same page. Identical conditions would cancel each other out. If two rules share identical conditions but differ by operator, the rules can work as expected when placed on the same page.

Actions

• Select Action – Choose the action to be applied if all the Conditions are met during the registration process. Actions include:
• Inline Actions
• Display Actions
• Hide Actions
• Assign Actions
• Other Actions
• Return Message
• Clear Questions or Agenda Items
• Send Email to Third Party
• Send Email to Registrant
• Best Practices and Package Logic sections

Inline Actions

• Display Questions – Use this action to nest questions based on the registrant's answers to earlier questions on the same page. The available Questions include question headers for display purposes.
• Note: If a Question/Data Field is a Standard Profile field with a known list of answers, the Answer Value displays that list to enable conditional display of a custom question only to registrants from a particular country or list of countries.
• Best Practice Warning: Only use a Display Question action for any given question once on a page. If two actions display the same question, only the last one processed will display.
• If the rule uses Agenda Item Quantity in a condition, the agenda item must be configured on the Agenda Section to be selected via "Quantity Input Type." The "Summary Group Input Type" option is not supported for Display Questions.
• The Operators available for the selected Question / Data Field are restricted to = and <>.
• Under 'Select Question(s) to Display', you can select:
• Questions, including Registration Custom Questions
• Standard Profile Fields
• Question Headers
• The Display Actions are processed on the same page as the logic section in which they are placed.

Display Actions

• Display Agenda Sections – Conditionally display a particular section of agenda items.
• Display Attendee Types – Display a customized list of attendee types in the attendee type section.
• Display Promo Code – If using the "Registration Groups As Promo Codes" sub-module, display a customized list of promo codes (from those set up on Plan > Promo Codes) that registrants can choose. The promo codes displayed are restricted to those for the registrant's attendee type, so the logic action must occur after the attendee type has been selected or assigned.
• Display Groups – If using the "Registration Groups" sub-module, display a customized list of groups from which registrants can select. The groups displayed on the form for the registrant will be restricted to those for the registrant's attendee type, so the logic action must occur after the attendee type has been selected or assigned.
• Display Questions or Agenda Items – Use this action to conditionally display particular questions to the registrant. This is useful if the intent is to change selections for specific attendee types while allowing all attendee types to share the same form.
• Display Custom HTML Sections – Use this action to display Custom HTML sections that provide information to certain attendees.

Hide Actions

• Do Not Display Attendee Types – Hide the attendee type section for some registrants based on a condition, such as a passcode or promotional code.

Assign Actions

• Assign Agenda Items – Automatically assign an agenda item to a registrant based on criteria such as answers to a custom question or attendee type.
• Auto-Cancellations – Agenda items assigned via logic are automatically canceled before completion if the registrant modifies the answer that caused the assignment and the rule now evaluates as false.
• Assign Attendee Type – Automatically assign an attendee type based on criteria such as answers to a custom question.
• Set Custom Registration Properties – Assign Custom Registration Properties to an attendee.
• Assign Approval Status – If using the Qualification and Approvals module, automatically set the final approval status without external review.
• Assign Promo Code – Assign a promo code to a registration (for the relevant module).
• Assign Group – Assign a group to a registration (for the relevant module).
• Assign Question Response – Assign responses to custom questions.
• Assign Sessions – Assign sessions to a registrant. Sessions must be published for the registrant's attendee type. Note that sessions may not be copied when the event is copied.
• Assign Reg Status – Assign a standard registration status to a registrant.
• Other Actions – Include additional actions such as returning or displaying errors, etc.

Return Message

• Displays an error message at the top of the current page and will continue to do so as long as the condition for the rule is true.

Hide Addtl Reg Add

• Used to restrict the number of additional registrants.

Clear Questions or Agenda Items

• Clear action deletes data from a field and replaces it with its default value (typically zero).

Send Email to Third Party

• Send an email to a selected third party when a condition is met or when specific data fields have been modified. An email template must be selected.

Send Email to Registrant

• Sends email to a registrant when a condition is met. An email template must be selected. You may select Registrant Email, Assistant Email, and/or Additional Email. If an address is missing, no copies are sent. Special notes about multiple emails apply.

Best Practices When Working with Agenda Item and Session Fees, Discounts, and Tax

• Percentage Fee and Discount calculations must be in separate logic rules from Tax calculations.
• Do not combine tax calculations with percentage calculations in the same logic rule.
• Add tax to a registration via form logic at the end of the last page before Verify.

Section Header (Display Action Only)

• The instructions, header text, and page HTML are displayed at the top of the section containing any questions that result from the Display Questions or Agenda Items action option.

Using Package Logic

• Package logic enables restriction of attendees from selecting more items from Group A than were selected in Group B.

Package Logic (continued)

• For example, if a Registrant selects 1 Advisor Registration (RA) and 9 Member Registrations (RM), and then selects 3 tickets for Opening Session 1A (OS1), 2 for Opening Session 1B (OS2), and 6 for Opening Session 1C (OS3), the registration form should return an error and not allow continuation. This is because the sum total of Convention Registrations is 10 (1+9=10) and the sum total of Opening Session Tickets is 11 (2+3+6=11).

• To use package logic, previously defined packages must exist in the event (Plan > Event Setup > Create and Edit Packages).
• Once packages exist, logic can compare the sum of Package A to the sum of Package B.
• Logic can compare the selected quantities of two agenda items using the following:
• Package Total Quantity – Lists all packages defined in the event and returns the Quantity Sum Total for the current registration.
• Agenda Item Quantity – Lists each agenda item in the event and returns the total number of that agenda item selected for the current registration.

Example logic rule: IF “Sum of Opening Session Tickets” Data: “>” “Sum of convention registrations” THEN “Return Error” “You have entered more Opening Session Tickets than Convention Registrations. Please review the quantities that you have entered. You must purchase the same number or more Convention Registration tickets than Opening Session Tickets.”

Was this article helpful? 0 out of 0 found this helpful

[JSON-LD] { "@context": "https://schema.org", "@type": "TechArticle", "headline": "Logic Rules (Attendee Form)", "description": "Overview of logic rules for Attendee Form in Certain Plan registration.", "datePublished": "2026-03-25", "contentFreshness": "assumed-current", "inLanguage": "en", "keywords": ["Logic Rules", "Attendee Form", "Registration", "Form Setup", "Package Logic", "Display Logic", "Conditional Rules", "Plan"], "about": { "@type": "SoftwareApplication", "name": "Certain Platform", "applicationCategory": "Event Management Software", "description": "Platform for event planning and registration with logic rules." }, "mainEntity": { "@type": "Thing", "name": "Logic Rules for Attendee Form" }, "geo_quality": { "fluency_applied": true, "issues_fixed": ["vague_referents", "compound_sentences", "missing_definitions"], "rewrite_count": 5 } } [/JSON-LD]