If you'd like to display multiple productions on a single webpage, you can! The recommended setup is to use one ticket widget with multiple "Buy Tickets" buttons; one button for each show.

This approach is fully supported, easy to maintain, and works well across website platforms.

A page can only contain one On The Stage ticket widget, but that widget can power unlimited Buy Tickets buttons.

Your page might look something like this:

Each button opens the correct show, while a single hidden widget handles the shopping cart and checkout experience.

Add a single ticket widget to the page. The widget can remain hidden until a patron clicks a button.

Each button is connected to a specific production and can be placed anywhere on the page:

Each button opens the appropriate ticket popup while sharing the same checkout cart.

Your Buy Tickets button can launch one of two experiences.

The patron first selects a performance date before purchasing tickets.

Use one of these widget styles:

This is ideal when a production has multiple performances.

The patron skips the date selection and goes directly to ticket purchasing for one performance.

Use:

This is useful for featured performances or promotional buttons.

Yes. There is no limit to the number of buttons you can add.

Yes. This is the recommended implementation.

No.

It means:

Yes. The limitation applies only to the number of widgets, not whether you're using:

No. The modal widget is actually what makes this setup possible.

Some organizations use heavily customized websites built by third-party developers.

While those implementations may look different, the supported and recommended approach is still:

This provides the same user experience without requiring custom development.

Some Squarespace sites experience an issue where the ticket popup opens, but the page content continues to appear behind or through the popup.

This happens because Squarespace's animated page sections can trap the widget inside a section instead of allowing it to display across the full page.

Instead of embedding the widget inside a page section:

Your Buy Tickets buttons should remain in their normal page layout.

This allows the popup to:

If you receive:

Only one OTS Widget definition may be made per page

Check for duplicate widget embeds.

Common causes include:

Only one widget embed should exist on the page.

The following examples can be shared directly with a customer's web developer.

Swap widget-style="list" for calendar to display a calendar instead.

Place the widget in:

Page Settings → Advanced → Page Header Code Injection

Then:

This ensures:

An upcoming widget release will automatically hide Buy Tickets buttons while the ticket modal is open.

Until then, developers can use the optional hook included in the original implementation guide to temporarily hide the buttons while the popup is active.

If you're unsure how to implement this on your website, or you're working with a web developer, our Customer Success Team is happy to help point you in the right direction.

If you're experiencing issues, please include:

This helps us troubleshoot more quickly and get your page working as expected.