In EventsAir, you can create various websites, apps and portals, all of which will have specific URLs.
Typically, URLs generated within an event are structured using your customer alias, event alias (and sometimes, information such as the site alias).
Customer alias
Your EventsAir customer alias is a short word or series of letters that’s part of your EventsAir login URL (it appears before the word ‘planner’ when you’re logging in):
Change from "app" to "planner" URLs
In April 2026, we updated our domain structure to improve platform efficiency:
app.customer-alias.eventsair.com → customer-alias.planner.eventsair.com.
OnAir: portalapp.alias.eventsair.com → alias.onair.eventsair.com
For example, if your alias was airtime:
EventsAir: airtime.planner.eventsair.com
OnAir: airtime.onair.eventsair.com
Existing links have been automatically redirected until October 2026
If you have saved bookmarks to the current URLs, they will continue to work through the redirect.
You should update any saved bookmarks in your browser.
If old links aren't working, use the new links instead.
Event alias
Then there’s your event name (and event alias).
By default, the event alias matches the event name, but you can manually change it.
[Unless you have custom domain for your whole event – in that case, event alias is locked and there’s a cost if you want to change it.]
The alias of an app, portal, or site you build in EventsAir may also form part of the URL (see following pages).
Making changes later
If you need to make changes to your event name or alias, make sure you check any impact on URLs. For example, if you update your event name (and alias) AFTER your registration site and attendee app were created, the URLs attached to the previous event alias will break.
Alternatively, if you change your event name but not the event alias, your URLs will no longer reflect your event name.
For custom domains, especially for event websites, you need to take special care (especially if changing from an event website built in the Legacy builder to one built in the Modern Event Website builder). More information can be found later in this article.
Terminology - domain structure (what a URL can include)
Protocol | Sub-subdomain | Subdomain (before the domain)
| Root domain/
| Sub-folder / [NOT subdomain] | page |
|
|
| Second-level domain | Top-level domain |
|
|
htttps:// | january. | blog. | company | .com | /about-us | /contact |
How URLs are generated (if there are no custom domains)
Below are examples of how URLs are generated in EventsAir when there is NO event-level custom domain / website custom domain.
Interactive (registration) site:
App/Portal from the EventsAir App Store:
The OnAir Portal is slightly different:
Modern Event Website:
IMPORTANT: Your Event Website created in the Modern builder needs to have a different domain to the rest of your event. [This is why it does NOT include the event name by default.]
The URL is created by default as a sub-domain (a prefix added to the main domain) of your event domain.
However, if you’re using a Custom Domain (for all your events, your event website, or your event) you need to ensure that the Modern Event Website doesn’t share that domain. (See more information below.)
In the Modern Event Website settings:
Legacy Event Website:
Mobile Apps (Attendee App, Organizer App):
Custom domains – overview
Your URLs will take a different format if you’re using a custom domain.
You may choose to have a custom domain if you want a customized URL to suit your event or company brand.
In EventsAir, a custom domain can be applied to various levels within the platform, depending on your requirements.
You can have:
A System-level custom domain (to give ALL events the same base domain) – costs apply
An Event-level custom domain (to connect one domain to a single event) – costs apply
An “Event website only” custom domain*
*This is a newer option and applied to the Modern event website only. It must be unique to the event website. Legacy event websites URLs use the event’s domain.
The actual domain name (URL)
NOTE: For ALL custom domains (including event websites only), you need to purchase (register) the actual domain name from your preferred domain registrar (also known as a domain re-seller).
A custom domain can't be attached in more than one place – e.g. a system-level domain can't be your corporate website domain. |
Example of system-level vs. event-level custom domain
System-level
A domain applied to ALL your events.
Example: imaginarycompany.com/event_alias/
Event-level
A particular domain for one specific event.
Example: myeventname.com
(See further below for more details of these examples)
What URL should my Modern event website have?
If you'd prefer to have your event website use the simplest domain, you can use a subdomain as your system-level or event-level custom domain (such as 2026.myeventname.com) and then use the root domain (e.g. myeventname.com) as the custom domain for your Modern event website.
If you want to follow this example and you have an existing system-level or event-level custom domain, you need to ask us to change the system/event domain to a subdomain FIRST, before attaching the custom domain to your Modern event website.
How your custom domain setup might look:
System-level custom domain example
System Domain (URL) set to www.imaginarycompany.com (applies to all events, each event will have its own domain subfolder/subdirectory e.g. event1, event2)
EVENT 1
URL STRUCTURE: imaginarycompany.com/event1
EVENT 2
URL STRUCTURE: imaginarycompany.com/event2
EVENT 3
URL STRUCTURE: imaginarycompany.com/event3
Event website (built in Modern) | Interactive Sites, apps, portals |
EVENT 1 |
|
| URLs take the default format but use the system-level custom domain as the base, for example:
Registration site: imaginarycompany.com/event1/interactive-site-alias/site/register
Imaginarycompany.com/client-portal/event1/portal-alias |
EVENT 2 |
|
|
|
EVENT 3 |
|
|
|
For all 3 events, an event website built in Legacy would have the domain: |
|
NOTE:
While most Apps/Portals will inherit a custom domain if applied to the event (system-level or event-level), the OnAir Portal doesn't - it follows the same format as it would without a custom domain:
customer-alias.onair.eventsair.com/VirtualAttendeePortal/event-alias/portal-alias
For all three events, if you’d built the event website in Legacy, it would be: Event System-level domain plus event alias
Event-level custom domain example
EVENT 1
URL STRUCTURE: myeventname.com
Event website (built in Modern) | Interactive Sites, apps, portals |
| URLs take the default format but use the event-level custom domain as the base, for example:
Registration site: myeventname.com/event1-alias/interactive-site-alias/site/register
Portal/app: myeventname.com/client-portal/event1-alias/portal-alias
|
OnAir portal:
customer-alias.onair.eventsair.com/VirtualAttendeePortal/event-alias/portal-alias
An event website built in Legacy would have been: myeventname.com
EVENT 2 (a)
URL STRUCTURE: myneweventname.com
[You can’t have the same custom domain on two events if they’re both live/connected to the domain at the same time.]
Event website (built in Modern) | Interactive Sites, apps, portals |
| URLs take the default format but using the event-level custom domain as the base, for example: Registration site: myneweventname.com/event2-alias/interactive-site-alias/site/register
myneweventname.com//client-portal/event2-alias/portal-alias |
OnAir portal:
customer-alias.onair.eventsair.com/VirtualAttendeePortal/event-alias/portal-alias
An event website built in Legacy would have been: myneweventname.com
EVENT 2 (b) - using same custom domain as event 1
This is how it'd look if you’re using the SAME custom domain as event 1, because you’ve removed the custom domain from event 1, and attached it to event 2 (which must have a different alias).
You can move a custom event-level domain from one event to another at no cost, as long as it's within 2 years of purchase of the custom domain service from EventsAir.
URL STRUCTURE: myeventname.com
Event website (built in Modern) | Interactive Sites, apps, portals |
| URLs take the default format but use the event-level custom domain as the base, for example: Registration site: myeventname.com/event2-alias/interactive-site-alias/site/register
Portal: myeventname.com/client-portal/event2-alias/portal-alias
Note that these URLs are different to Event 1, because the event alias is different.
|
OnAir portal:
customer-alias.onair.eventsair.com/VirtualAttendeePortal/event-alias/portal-alias
Event website, if you'd built it in Legacy: myeventname.com (if you were keeping the website built previously with that domain)
Custom domains - how to get them
System-level domain
If you want a System-level domain (for all your events), please ask your Account Manager who can help you with pricing and setup.
Event-level custom domain
Purchasing an event-level custom domain is activated in the Setup Panel, in Event [Preferences], Custom Domain tab.
As explained above, the custom domain will be applied to interactive sites and apps/portals from the app store (not your Attendee or Organizer apps or your Modern event website).
You can see and authorize the relevant additional charge, which covers server costs, configuration, certificate installation, traffic routing, and the underlying coding that makes it all possible.
You’ll need to provide the following information when requesting an event-level custom domain, and after your provide this and authorize the purchase, our IT team will contact you to advise on the next steps.
Domain required
Organization name – that owns the domain
City/Location
State/Province
ISO Country Name
Technical contact (email)
There’s also a checkbox where you can indicate if you already have an SSL certificate for this domain.
Summary of how a custom domain affects your websites
Create your own event-website custom domain (Modern event website builder only)
A custom domain that’s just for your event website can be created in the Modern Event Website builder, at no additional cost, by adding the domain name and DNS settings (and advising your DNS provider). This must be unique (not shared with your event domain).
Create the event website using the Modern Builder
Under 'EVENT WEBSITE', choose 'Settings'
Fill in the 'Custom domain' field, then select 'Attach domain'
Add the details and give your DNS provider the correct information
Again, a system-level OR event-level domain must be different to an event website domain if using the Modern Website Builder.
Event-level custom domain with Modern event website
If you're building an event website in the Modern Builder, but you want a custom domain for the rest of the event (registration sites, apps & portals from the EventsAir App Store), the event website must have a different domain. Use the above process to get a system or event-level custom domain, then add a different domain to your event website.
Event-level custom domain with a Legacy event website
If you were to build an event website in the Legacy Builder, the only way to have a custom domain for that event website is to purchase a custom domain for the whole event OR a system-level custom domain (using the above process). The event's custom domain would then be automatically applied to your Legacy-built event website.
More help with Custom Domains
Search this site for more information about using and updating custom domains.
Resolving duplicate website domain issues
If you had previously had a custom domain attached to a Legacy-built event website, and you want to use that custom domain for another website:
You need to go the previous event, go into Setup, Event, Custom Domain tab, and select the “Remove Custom Domain” button.
Wait at least five minutes before using the domain for a different (Modern-event-builder-created) event website.
If your event website was created in the Legacy builder, hasn’t yet been removed; your event alias has been changed (and the event website is republished), which has created a second website at the new alias URL in addition to the original site (i.e. two different websites for the same event).
The best option is to delete the Legacy site and build a new one in the Modern builder.
Alternatively, if you need to use the Legacy builder for the updated website, follow the steps below to remove or overwrite the original alias:
Change your event alias back to match your old event website URL.
In the Legacy Event Website Builder, create a closed landing page, set your other pages as draft to stop them being published, then republish the site. (This will replace the site available at the old URL with a closed page.)
Change your event alias back to the correct value, and build your new event website in the Legacy builder, if you need to do that.
Consider consulting your domain provider's support if DNS configuration issues persist.
More custom domain tips:
Always test URLs before sharing/promoting them.
DNS changes can take time to propagate, and changes may not be instant (and can take up to 48 hours). If you’re concerned, talk to your DNS provider’s support team.