Website Integration

​

Overview

Website integration allows you to embed your event pages and checkout flow directly on an external website. Instead of redirecting customers away to purchase tickets, an embedded checkout opens in a modal overlay — keeping customers on your website throughout the purchase process. This is useful when:

• You want to sell tickets directly from your own website without redirecting customers
• Partners or sponsors need to sell tickets from their sites
• You want a seamless branded experience that keeps customers in your ecosystem

​

How Embedding Works

The platform provides a JavaScript embed script and a button that you place on your external website. When a customer clicks the button, a modal overlay opens containing your event page inside a secure frame. The customer can browse items, add them to their basket, and complete checkout — all without leaving the host website. The embed script handles:

• Opening and closing the modal overlay
• Secure communication between the host page and the embedded checkout
• Responsive sizing across desktop and mobile devices
• Origin validation to prevent unauthorised embedding

​

Setting Up an Embed

To generate embed code for an event:

1. Open the event in the admin panel.
2. Click Website integration to launch the embed wizard.

The wizard walks through four steps:

​

Step 1: Button Settings

Configure how the embed button appears on the external website:

​

Step 2: Modal Settings

Control the appearance and behaviour of the modal overlay:

​

Step 3: Embed Code

The wizard generates HTML code to copy and paste onto your external website. The code includes:

• A <script> tag that loads the embed script
• A <button> element with a configuration attribute containing your settings

Paste this code into your website’s HTML where you want the button to appear.

​

Step 4: Troubleshooting

The final step includes a troubleshooting guide to help resolve common issues with embedded checkouts.

​

Cross-Site Analytics

When the checkout is embedded on an external website, the platform sends tracking events via the browser’s postMessage API. The host website can listen for these events to integrate embedded checkout activity with its own analytics tools. Events include:

• Page views — When the customer navigates between pages within the embed
• Product impressions — When products are displayed to the customer

To capture these events, add a message event listener on the host page that checks for the nuTracker property in the event data.

​

Seating Plan Integration

For events with assigned seating, the embedded checkout supports a rich interaction API for controlling the seating plan from the host website. The host page can programmatically:

• Enable or disable seat selection
• Highlight specific areas, price bands, or individual seats
• Select or deselect seats
• Navigate into and out of venue areas
• Listen for seat selection, deselection, and error events

This enables building custom seating experiences where the host website provides its own UI alongside the embedded seating plan. Communication uses the browser’s postMessage API — the host page sends commands to the embedded frame and receives events back.

​

Sessions in Embedded Checkouts

Embedded checkouts handle sessions differently from standard visits because third-party cookies may not be available within embedded frames on some browsers. When cookies cannot be set, the platform automatically falls back to passing a session identifier via URL parameters or request headers — no additional configuration is needed. The session is validated on each request to prevent hijacking, and the platform tracks the client’s identity to ensure session integrity.