Request API access
Micro Frontend · Overview

Your ticket shop, part of your website.

Visitors choose, register and pay for tickets directly on your pages: no redirect to another shop, in your brand's look. Events, prices, availability, payment and tickets keep running through ADITUS.

See the live demoTechnical documentation
ExperienceDays demo website in a desktop browser: below the page heading, the embedded ticket shop shows the event start page with tiles.
The same shop on an iPhone: event start page.
The ExperienceDays demo site: the shop sits inside the page, on desktop and smartphone.

What the Micro Frontend is

The Micro Frontend is the ADITUS ticket shop as a building block for your website. Your web team places it on any page, and it looks and behaves like part of that page.

  • Visitors stay with you

    No jump to a separate shop domain and no embedded foreign window. Navigation, header and footer of your site stay in view throughout the purchase.

  • It looks like your brand

    Colours, fonts and shapes follow your brand. Without any adjustment, the shop uses the colours of your event from ADITUS.

  • ADITUS runs it

    Events, prices, availability, payment and tickets come live from your ADITUS ticket shop. You maintain nothing twice, and updates reach your site automatically.

How a purchase works

Four steps, all on your page. The screenshots come from the ExperienceDays demo site.

  1. Choose tickets

    Ticket types with prices, discounts and remaining availability. Promotion codes and vouchers are redeemed right here.

    Ticket selection with ticket types, prices and quantity buttons.

  2. Review the cart

    A clear summary of all items. The shop suggests suitable add-ons if you have set them up in ADITUS.

    Cart with the selected tickets, totals and suggested add-ons.

  3. Register attendees

    Each ticket gets its attendee, with your questions and, where provided, time slots and a badge preview.

    Attendee registration for a ticket with time slot selection and badge preview.

  4. Pay

    All payment methods set up in your ticket shop. The buyer then receives the confirmation and the tickets, optionally also for Apple Wallet and Google Wallet.

    Payment step with PayPal, card, invoice and other methods plus the billing address.

Made for the smartphone too

Many tickets are bought on a phone. The shop adapts to small screens by itself, so you do not need a separate mobile version.

The shop on an iPhone: cart with ticket summary.

The base setup

The quickest start: your web team adds two lines of code to the page, and ADITUS enables your website. No server of your own and no programming needed.

Already included

  • The complete purchase from ticket selection to the ticket
  • Vouchers and promotion codes
  • Attendee registration with your questions and time slots
  • Upgrades and add-ons, as configured in ADITUS
  • All payment methods of your ticket shop
  • Your event's colours from ADITUS
  • German and English shop interface
  • Desktop, tablet and smartphone

Buyers enter their details in the shop. Linking to customer accounts on your site is add-on level 2.

Dialog offering an upgrade from the day ticket to the season ticket.
Upgrade offer after choosing tickets: shown automatically when set up in ADITUS.

Optional add-on levels

Each level builds on the base setup and can be added later. You choose how deep the integration goes.

  1. Level 1

    Match your brand

    Worth it if the shop should match your website exactly, beyond the event colours.

    Colours, fonts, corner radii and spacing are set visually in the styling tool. The result is a small configuration your web team adds.

    The same ticket selection without custom styling.
    Without custom styling
    The ticket selection with the ExperienceDays styling.
    With the ExperienceDays styling

    Effort: settings in the styling tool, no programming

    Open the styling tool →

  2. Level 2

    Connect your customer accounts

    Worth it if visitors sign in on your site, for example in a member area, customer account or exhibitor portal.

    Your site tells the shop who is buying. Known customers do not sign in a second time; their buyer data is taken over and stays protected in the shop.

    Effort: a small extension on your web server

    Technical details →

  3. Level 3

    Interlock with your website

    Worth it if the shop should be part of your website's navigation, measurement and processes.

    • Mini cart in your page header
    • Sales in Google Analytics 4
    • Your own confirmation page after the purchase
    • The browser's back button and swipe gesture go one step back in the shop

    Effort: small additions by your web team, each feature on its own

    Technical details →

  4. Level 4

    Full build-out

    Worth it if ticket sales are a central part of your website.

    All levels combined: your design, your sign-in, your cart in the header, your confirmation page and your analytics. For visitors, the shop can no longer be told apart from your website.

    Effort: levels 1 to 3 together, usually introduced step by step

    See integration examples →

Next steps

This page gives an overview. Every technical detail is in the documentation.

Questions about your project? Contact us