Before starting registration setup:
-
Think through the whole journey: The registration pipeline is extremely flexible and customizable so we recommend mapping out the full registration journey before starting to build the pipeline. For example, where do you need conditional logic? What categories will you use? Are any approvals needed? Planning these details first will avoid having to go back and make changes once you’ve built the pipeline
-
Confirm mapping before building anything — if a third-party registration vendor is being used, confirm field mapping before building the pipeline. Retrofitting after setup causes significant rework.
Please note - it’s possible to clone an existing event and then just update the cloned registration pipeline rather than starting from scratch each time but before doing so please review these important points to know about cloning, both overall and specific to registration.
If you only need the questions, you can export a Visitor Custom Report, however, it will not include the dropdown selection options
While building registration:
-
Mark API-populated fields as non-editable — fields populated via API (CRM, SSO) should be read-only on the frontend to prevent data conflicts.
-
Conditional fields that depend on participant category should be tested with each category
-
File upload fields have size limits configured at admin/general/settings