Add Ticketmatic Widgets to WordPress

Ticketmatic imports can do more than create WordPress events. After the event sync works, Jeero can place Ticketmatic widgets on your WordPress site so visitors can continue from an event to the right ticket flow without losing the event context.

This guide is for the widgets that the Jeero WordPress plugin currently exposes for Ticketmatic:

• tickets_button
• tickets_inline

Before You Add a Widget

Start with the import, not the widget.

First confirm that Ticketmatic events are importing into WordPress, event dates are correct, and the normal ticket links point to the right Ticketmatic pages. The widgets improve the visitor journey after that foundation is in place.

For the examples below you also need the Jeero subscription ID. Jeero shows widget shortcodes in the subscription settings for supported Ticketmatic imports.

Paste shortcodes as plain text in a WordPress Shortcode block or in the code editor. Do not escape the quotes, and avoid rich-text transformations that turn quotes into curly quotes.

Choose the Widget

Use inline tickets when an event page should show a specific Ticketmatic ticket page inside WordPress.

Use a tickets button when the event page should link visitors onward with a normal button instead of embedding the ticket page.

Set Up Local Widget Pages

Before using this widget, fill the widget-specific settings in the same Jeero subscription:

• Ticketmatic return URL. Required for the inline widget.
• Ticketmatic skin ID. Required for the inline widget.
• Ticketmatic sales channel ID. Optional when your Ticketmatic setup does not need a separate value.

Create a Tickets page and add the inline tickets shortcode without a fixed ticket URL:

[jeero_tickets_inline subscription="SUBSCRIPTION_ID"]

Return to the same Jeero subscription and select this page under Tickets Button > Tickets page. A tickets button with event context will now open this local page with a jeero_event query argument. The inline widget uses that event to load the matching ticket URL.

Add a Tickets Button

Place the tickets button where visitors should move from a WordPress event page to Ticketmatic tickets:

[jeero_tickets_button subscription="SUBSCRIPTION_ID" tickets_url="https://example.com/tickets"]

Replace SUBSCRIPTION_ID with the Jeero subscription ID and replace tickets_url with the real Ticketmatic ticket page for that event when the placement does not already provide event ticket context.

The button is status-aware. The widget can return a link for normal on-sale events, a non-linked label for sold-out or cancelled events, or no output when the ticket status is hidden.

If you select a local tickets page in the Jeero widget settings, Jeero links the button to that WordPress page with a jeero_event query argument. If no local page is selected, Jeero uses the event tickets_url.

For The Events Calendar, add the shortcode to the single event content or to a template location that runs inside the current tribe_events post context. Jeero can then read the event's ticket metadata and build the local Tickets page link with jeero_event.

For Theater for WordPress, go to Theater > Settings > Display and add {{jeero_tickets_button}} to the Template field under Upcoming events. Jeero then renders the correct button for every event date in the agenda.

Add Inline Tickets

Place the inline tickets shortcode where visitors should choose tickets for one Ticketmatic event:

[jeero_tickets_inline subscription="SUBSCRIPTION_ID"]

Before using this widget, fill the widget-specific settings in the same Jeero subscription:

• Ticketmatic return URL. Required for the inline widget.
• Ticketmatic skin ID. Required for the inline widget.
• Ticketmatic sales channel ID. Optional when your Ticketmatic setup does not need a separate value.

Replace SUBSCRIPTION_ID with the Jeero subscription ID. Place the shortcode in the current WordPress event context, or use the local Tickets page flow above. Jeero uses the current event's imported ticket URL plus the subscription widget settings to generate the signed Ticketmatic widget URL; a tickets_url or url shortcode attribute cannot replace canonical event data.

If the Tickets page is empty, check this first: Confirm that the event has an imported Ticketmatic ticket URL and that the same Jeero subscription has a Ticketmatic return URL and skin ID in the widget settings. Adding tickets_url or url to the shortcode cannot replace canonical event data.

If you use Theater for WordPress, imported productions and event dates are stored separately. For inline tickets, use the tickets_url from the relevant wp_theatre_event date, not the wp_theatre_prod production post. The URL will look like https://tickets.example.com/nl-nl/Show/Details/1234.

If your imported events are still drafts, test the inline tickets widget on a temporary published page first. Move it into the event template or event page once the event is public.

The inline tickets widget renders an iframe. It accepts optional title, width, and height attributes. If you do not set them, Jeero uses Tickets, 100%, and 800.

Theme, Block, or Menu Placement

If your theme or a custom block controls placement, use the same Jeero widget renderer instead of rebuilding the shortcode behavior.

Use jeero_get_theater_widget() when you need the rendered HTML as a string:

echo jeero_get_theater_widget( 'tickets_button', 'SUBSCRIPTION_ID' );

Use jeero_theater_widget() when you want to echo the widget directly:

jeero_theater_widget( 'tickets_inline', 'SUBSCRIPTION_ID' );

This keeps subscription lookup, widget support checks, wrapper classes, and Ticketmatic-specific output in one place.

Check the Result

After placing a widget, check the page as a visitor:

• The inline tickets widget loads the intended Ticketmatic ticket page.
• The tickets button opens the local Tickets page with a jeero_event query argument, and that page loads the matching ticket iframe.
• The ticket flow still works after moving between event pages and the ticket page.

On the WordPress side, check that each iframe source points to the expected Ticketmatic URL. Because the iframe is loaded from Ticketmatic, browser tools may not be able to inspect the full iframe content from WordPress.

Ask for Help

Send me the WordPress event page, the Ticketmatic ticket URL, and where the widget should appear. I can help choose the right shortcode and check whether your setup needs inline tickets, a tickets button, or a small theme placement.