Understanding the Event Creation Flow
Creating an event is one of the most important workflows within the Novotix platform. During this process, all essential technical, financial, and operational configurations are automatically prepared in the background. This ensures that once your event is created, you can immediately continue with ticket sales, registrations, and further event setup.
This guide explains step by step how to create an event, what each step is intended for, and how your choices influence the setup and behavior of your event.
Before an event can be created, the account onboarding process must be started.
Starting onboarding connects a Payment Service Provider (PSP) to your Novotix account
This connection is required to:
Create events
Accept payments
Process refunds
The onboarding does not need to be completed, but it must be started
Ticket sales can begin immediately after onboarding is started
Payouts of ticket revenue will only take place once onboarding and KYC checks are fully approved
Without onboarding:
Events cannot be created
Payments cannot be accepted
For more information, see the Onboarding & KYC helpdesk article.
Open the main menu on the left side of the dashboard
Go to Management > Events
You will now see the Events overview page
On the top-right of this page, click:
Create new event
This starts the event creation wizard.
Gives you access to the event creation flow
Ensures events are created consistently and correctly
Automatically prepares core system settings in the background
After clicking Create new event, a multi-step wizard opens.
This wizard ensures all mandatory event data is captured in the correct order.
Prepares payment configurations
Sets up default ticketing logic
Creates event-specific system dependencies
After completing the wizard, the event can be fully customized via the Event Details page.
You must first choose the type of event:
Public event
Corporate event
The selected event type determines:
Which features are enabled
Which settings are available
How ticketing, registration, and branding behave
Purpose:
Designed for events open to a broad public audience, usually focused on entertainment or social interaction.
Examples:
Festivals
Club and nightlife events
Concerts
Micro-events
Typical features:
Ticket sales
Public ticket shops
Marketing and promotion tools
Crowd and access management
Purpose:
Designed for professional or organizational use cases.
Examples:
Conferences
Summits
Meetings
B2B events
Typical features:
Registration-based access
Professional branding
Attendee management
Networking and information sharing tools
Choosing the correct event type ensures your event is configured with the right tools, expectations, and workflows.
After selecting the event type, click Continue.
In this step, you define the core identity of your event.
Purpose:
The official name of the event. This name is used throughout the platform, ticket shops, emails, and reporting.
Purpose:
Used to describe the theme, slogan, or context of the event
Example: “The ultimate summer experience”
Purpose:
This field cannot be filled in at this stage.
The description is configured later via the event settings and can:
Be written manually
Be generated using AI
AI-generated descriptions are optimized for:
Marketing
Conversion
Search engines (SEO / Google indexing)
Click Continue to proceed.
This step defines when the event takes place.
Purpose:
Defines the official start date and time of the event itself
Not related to ticket sales or registration opening
Purpose:
Defines the official end date and time of the event
Only reflects event duration, not ticket sales or registrations
Purpose:
Ensures all time-based functionality works correctly, including:
Countdown timers in ticket shops
Automated communications
Notifications and schedules
Correct configuration prevents confusion and ensures consistency across all user-facing systems.
Click Continue to proceed.
This step defines where the event takes place.
Purpose:
Displayed in ticket shops, confirmations, and event information
Purpose:
Used for:
Visitor information
Maps and navigation
Event context and communication
The address can be searched and auto-completed to ensure accuracy.
Click Continue to proceed.
This step defines visitor-facing rules and classification.
Purpose:
Clearly communicates age restrictions to visitors
Purpose:
If enabled, tickets will indicate that ID verification is required at entry
Purpose:
Classifies the event for internal organization, reporting, and ticket shop presentation
Examples:
Festival
Concert
Nightlife
Club
Theater
Sport
Meeting
Conference
Exhibition
Summit
Purpose:
Improve discoverability
Enhance ticket shop presentation
Generate Google search links
Support marketing and SEO
Click Continue to proceed.
This is the final confirmation step.
Confirms all entered data
Creates the event in the system
Activates the event configuration
Click Submit to finalize event creation.
After submitting, you are automatically redirected to the Event Details page, where advanced configuration and management take place.
Below is a high-level overview of what can be managed there.
Purpose:
Monitor event performance and visitor behavior
Includes:
Issued products over time
Revenue and additional revenue
Issued products
Service and transaction costs
Average age
Average products per order
Issued products ratio
Gender ratio
Top 10 cities and countries
Visitor world map
Purpose:
Manage and search all orders related to this specific event. Includes date filters and keyword search.
Purpose:
Create and manage tickets and products
Includes:
Pricing
Ticket layouts
Categories and sections
Purpose:
Define how and where tickets are sold
Includes:
Fully branded ticket shops
Available products per channel
Payment methods
Discounts
Shareable links and QR codes
Embed codes
Purpose:
Collect additional information from visitors
Examples:
PO numbers
Job titles
Dietary preferences
Clothing sizes
Allergies
Purpose:
Manage artist line-ups or speaker lists
Purpose:
Customize communication such as:
Order confirmations
Cancellations
Cart abandoned messages
Check-in notifications
Purpose:
Trigger automated email, SMS, or WhatsApp flows based on the communication templates, events and conditions.
Purpose:
Control which users have access to this event and what permissions they have.
Purpose:
Central configuration hub for:
Event details
Venue settings
Connected apps
Legal terms and conditions
Marketing and invoicing integrations
The Novotix event creation process is designed to be:
Structured
Secure
Scalable
Easy to understand
By guiding you through a clear wizard and automating complex configurations, Novotix ensures your event is ready for professional ticketing and registration with minimal effort.