Add ActiveTickets Widgets to WordPress

ActiveTickets imports can do more than create WordPress events. After the event sync works, Jeero can place ActiveTickets 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 ActiveTickets:

• account_indicator
• account_inline
• tickets_inline
• tickets_button
• cart_inline
• cart_indicator

Before You Add a Widget

Start with the import, not the widget.

First confirm that ActiveTickets events are importing into WordPress, event dates are correct, and the normal ticket links point to the right ActiveTickets 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 ActiveTickets 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 ActiveTickets 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.

Use inline cart when you want a WordPress cart page that embeds the ActiveTickets cart flow.

Use a cart indicator when your header, navigation, or sidebar should show the visitor's current cart state.

Use inline account or an account indicator when visitors should reach their ActiveTickets account from WordPress.

Set Up Local Widget Pages

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.

Create a Cart page and add the inline cart shortcode:

[jeero_cart_inline subscription="SUBSCRIPTION_ID"]

Create an Account page and add the inline account shortcode:

[jeero_account_inline subscription="SUBSCRIPTION_ID" path="/nl-NL/Account/Manage"]

Return to the same Jeero subscription and select those pages in the widget settings:

• Cart page for the cart indicator.
• Account page for the account indicator.

Add a Tickets Button

Place the tickets button where visitors should move from a WordPress event page to ActiveTickets 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 ActiveTickets 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 ActiveTickets event:

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

For a direct placement, replace SUBSCRIPTION_ID with the Jeero subscription ID and replace tickets_url with the real ActiveTickets ticket page for that event. On the local Tickets page created above, leave tickets_url out; the jeero_event query argument supplies the event context.

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.

Add an Inline Cart

Place the inline cart shortcode on the WordPress page that should contain the cart:

[jeero_cart_inline subscription="SUBSCRIPTION_ID"]

When the ActiveTickets subscription has a baseurl, Jeero builds the cart URL by adding /Cart to that base URL. For example, https://tickets.example.com/shop becomes https://tickets.example.com/shop/Cart.

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

Add a Cart Indicator

Place the cart indicator where visitors expect to see their basket state:

[jeero_cart_indicator subscription="SUBSCRIPTION_ID" label="Cart"]

The indicator renders the label and a cart count binding. ActiveTickets cart messages update cart.count in the browser when the cart changes.

To link the indicator to your local cart page, select that page in the Jeero widget settings for the subscription.

Add an Inline Account Page

Place the inline account shortcode on the WordPress page that should contain the visitor account flow:

[jeero_account_inline subscription="SUBSCRIPTION_ID" path="/nl-NL/Account/Manage"]

When the ActiveTickets subscription has a baseurl, Jeero builds the account URL by adding /nl-NL/Account/Manage to that base URL. For example, https://tickets.example.com/shop becomes https://tickets.example.com/shop/nl-NL/Account/Manage.

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

Add an Account Indicator

Place the account indicator where visitors expect to reach their ticketing account:

[jeero_account_indicator subscription="SUBSCRIPTION_ID" label="Account" logged_in_label="My account" logged_out_label="Log in"]

The indicator renders a label binding. ActiveTickets login messages update account.label in the browser when the account iframe reports the visitor's login state.

To link the indicator to your local account page, select that page in the Jeero widget settings for the subscription.

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 ActiveTickets-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 ActiveTickets ticket page.
• The inline cart widget loads the ActiveTickets cart page.
• The cart indicator appears in the right place and links to the intended cart page when a link is configured.
• The inline account widget loads the ActiveTickets account page.
• The account indicator appears in the right place and links to the intended account page when a link is configured.
• 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 ActiveTickets URL and that the indicator bindings appear. Because the iframe is loaded from ActiveTickets, browser tools may not be able to inspect the full iframe content from WordPress.

Do not use [jeero_cart] or [jeero_account]; those shortcodes are not registered. Use [jeero_cart_inline], [jeero_cart_indicator], [jeero_account_inline], or [jeero_account_indicator].

Ask for Help

Send me the WordPress event page, the ActiveTickets 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.