Event website

Your event’s website — we build and launch it

An event website is usually made last, breaks the day before the start and shows the old programme. We build it on Aditum data: the programme and speakers are the ones in the console; the forms are the ones that feed your database.

What’s on the site

What a guest looks for on an event site

Not a “landing page with design” but a working site: information, programme, people, partners and a form that leads into the console.

Home

Dates, venue, what the event is about, key speakers and a register button. The brand is yours.

Programme

By days and halls, parallel tracks. The source is the Aditum console.

Speakers

Cards with roles: speaker, moderator, host. Photo, organization, sessions.

Partners

A catalogue with types: general, strategic, media. Logo and description.

Registration by category

Attendee — public form, speakers and partners — by link. All into one database.

Venue & getting there

Location, halls and zones on a map, directions, parking, nearby hotels.

Visitor’s personal account

Application status, e-badge, own schedule — the same as in the guest app.

Communication with participants

Message a speaker or another participant, arrange a meeting — within the event.

Live data

Changed a session in the console — the site is already different

Programme, speakers and partners are edited in one place. The site, the guest app and access rules read the same thing.

Three routes

The catalog, an organization site or your own site on the API

  1. Event catalog

    The event appears in the platform catalog at aditum.events, with an event card and ticket sales. No separate site needed.

    • A public event card
    • Ticket sales and seat choice on the card
    • No separate site
  2. Organization site

    A site template with your accent colour, languages and your own domain. Every event of the organization on one site.

    • Template and accent colour
    • Several languages
    • Your own domain
    • All the organization’s events on one site
  3. Your own site through the API

    Have a team or an agency? The site stays yours. Registration, programme and tickets come from Aditum through an open, documented API.

    • Registration forms on your site
    • Programme and speakers
    • Tickets and payment on the site — once a payment provider is connected
    • Performances of a series and partner packages
    • Seller legal documents
    OAuth2 OpenAPI
Example

An organization site with two events

A conference and a tour on one site. This is what the “Organization site” route looks like.

Example: one site, the organization’s own domain, all its events.
Turnkey

We build and launch

You provide the brand, copy and programme structure. We assemble the site on Aditum data, connect the forms and launch. Programme and speaker changes pull from the console by themselves.

  • Any languages, your brand
  • Registration forms by category embedded
  • Hosting and support on us
Forms

An application from the site — straight into your console

The form on the site is the same form as in Aditum: version, fields, quota, registration window. The guest clicks “Submit” — the application is in the catalogue, the email is sent, the approver sees it.

How registration works →

Let’s discuss your event website

Tell us your path — turnkey or your own development — and the launch date. The rest is on us.

A 30-minute demo

Tell us about your event — we’ll show it on yours

A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.

  1. Fill in the form: event type, number of participants, a few words about it
  2. Within one business day we email you to agree a time
  3. On the call we show Aditum configured for your event and answer your questions
Or write directly [email protected]
Phone
We’ll call if the email gets lost
By submitting you agree to the privacy policy.