Widget vs. CTA: tenant checkout modes

When a visitor buys a ticket on your tenant site, Spotagig can either open checkout on-site using the ticketing platform's embedded widget, or send the visitor straight to the platform in a new tab as a plain call-to-action (CTA) link. Which one happens is controlled per tenant, separately for each ticketing integration.

The modes, and what each one does

Eventbrite — Ticket Checkout Mode

• Official SDK (EBWidgets — recommended) — Eventbrite's own widget script opens ticket selection in a modal on top of your page. Visitors never leave your site, and Eventbrite maintains the checkout experience for you.
• Custom iframe modal — Spotagig builds and owns the modal itself and loads Eventbrite's checkout page inside an iframe. This gives full control over styling, loading state and z-index (useful if the official widget clashes with your theme), at the cost of maintaining that modal ourselves.
• Direct redirect to Eventbrite — the button is a plain link; visitors leave your site and complete checkout on eventbrite.com. No widget or modal is involved.

Fienta — Fienta Checkout Mode

• On-site widget (embed.js — recommended) — Fienta's embed.js script intercepts the button click and opens checkout on-site, the same way the Eventbrite SDK mode does.
• Direct redirect to Fienta — the button is a plain link to your Fienta ticket page; no embed script runs.

Why the mode matters

Widget and CTA modes are a trade-off between experience, control and reliability — there's no single right answer for every tenant:

• Widget modes keep visitors on your site. No handoff to another domain, no lost branding, and (for Eventbrite/Fienta) analytics events fire from a page you control — important for pixel tracking and server-side analytics to see the full funnel.
• The custom iframe modal trades platform polish for control. Use it if the official Eventbrite widget's modal styling, z-index or loading behavior conflicts with your theme or other on-page scripts. Most tenants should stick with the recommended official SDK unless they hit a specific problem it doesn't solve.
• Redirect modes are the simplest and most compatible. They have zero dependency on a third-party embed script loading correctly, so they're a safe fallback if a widget misbehaves for some visitors (ad blockers, strict browser privacy settings, or script loading failures), and the reduced third-party JavaScript can also mean a slightly faster page. The trade-off is a visible handoff away from your site and a browser-side analytics gap once the visitor leaves.