1. Home
  2. Sell tickets on your website
  3. WordPress
5,000+ organizers trust Hi.Events

Sell tickets on WordPress
One block. No plugin.

A WordPress event ticket system does not need a plugin. Paste the Hi.Events widget into a Custom HTML block and ticket sales run on your page, with checkout opening over it. Works with any theme and any page builder that has an HTML element.

One paste into a Custom HTML block, nothing to install or update.

§ 01 · Before you start

What you need

Nothing to install on WordPress. The widget is a few lines of HTML that Hi.Events generates for you.

  • A Hi.Events event, published, with at least one ticket type on sale
  • Edit access to the WordPress page or post, as an Administrator or Editor
  • Two minutes in the block editor

Which WordPress sites can run the widget

Self-hosted WordPress runs it on any plan, as long as your user role has the unfiltered_html capability (Administrators and Editors on most sites; Contributors have script tags stripped on save). On WordPress.com, script tags in the Custom HTML block need a paid plan with hosting features activated; the free plan removes them. If you are unsure, add the block, save, and reload the page: if the widget shows, you are fine.

§ 02 · Steps

How to sell tickets on WordPress

5 steps, with the exact menu path in WordPress for each one.

  1. Copy the code from Hi.Events

    Open your event in Hi.Events and click Widget Embed under Integrations. Set up the widget and save it with a name. Under Add to your site, choose WordPress in Where is your website? and copy the code. It already contains your event and widget IDs.

    Hi.Events > Your event > Integrations > Widget Embed
  2. Add a Custom HTML block where tickets should appear

    Edit the page or post in the block editor. Click the Block Inserter (the + icon), search for HTML and choose Custom HTML, or type /html in an empty paragraph and press Enter.

    Block Inserter (+) > Custom HTML
  3. Paste the code into the block

    Click Edit HTML on the block and paste the code into the HTML pane: the div and the script line under it, together. The preview beside the code shows the widget once the script has loaded.

  4. Optional: load the script once in your site head

    If you put the widget on several pages, you can load the script line once in the head instead, through your theme's header code option or a header and footer scripts plugin, and paste only the div into each block. Loading it twice on one page does no harm, so you can skip this.

  5. Update the page and run a test checkout

    Click Update, open the page logged out, and buy a ticket. Checkout opens in a pop-up over your page. Refund the test order from the Hi.Events dashboard.

§ 03 · The code

The embed code, and where it goes on WordPress

The Widget Embed page in Hi.Events generates it with your widget already set up. This is what it looks like.

Code to paste

All of it goes in the Custom HTML block, exactly where you want the tickets to show. To load the script once for the whole site, move that line into the head through your theme's header code option or a header scripts plugin.

<div class="hievents-widget"
data-hievents-id="123"
data-hievents-widget="wgt_a1B2c3D4e5F6g"
></div>
<script async src="https://app.hi.events/widget.js"></script>

123 and wgt_a1B2c3D4e5F6g are placeholders. Open your event, click Widget Embed under Integrations, save your widget and copy its code: it carries your real event and widget IDs. Colors, the checkout setting and the language are stored with the saved widget, so changes you save reach your page without pasting again. A Button widget keeps its text, colors and corner radius in the code, and Fit height to content is in the code for the other widgets, so copy it again after changing those. The full list of attributes is in the widget docs.

§ 04 · What to expect

What happens once it is live

Checkout opens over your page

When a buyer clicks continue, checkout opens in a pop-up on top of your WordPress page. They never leave your site. To send them to a new tab instead, set Checkout opens in to New tab in Widget Embed.

The block grows to fit

The widget auto-resizes as ticket types expand and collapse, so you do not set a height on the block. Prices and availability update on their own; the code never needs re-copying for that.

It matches your site

Match your event page in one click, or set your own button, background, text and border colors, corner radius and padding. Save the widget and your changes reach every page that embeds it, with its views, orders and conversion counted in Hi.Events.

If you cannot run scripts on WordPress

If your role or plan strips script tags, add a Buttons block instead and link it to your Hi.Events event page. Buyers get the same checkout on app.hi.events, in your colors from the Homepage Designer. How the Homepage Designer works

§ 05 · The widget

What the widget sells on your WordPress page

Whatever you set up in Hi.Events shows in the widget. There is no cut-down embed version.

Paid, free, donation and tiered tickets
Add-ons, sold with a ticket or on their own
Promo codes, including hidden tickets they unlock
Registration questions per ticket type
Tax and fees inside the price or added at checkout
Ticket by email, with a link to the QR code
Checkout in the visitor's own language
Sale windows, capacity and per-order limits
Card, Apple Pay and Google Pay through your Stripe account
§ 06 · FAQ

Selling tickets on WordPress: questions

Do I need a WordPress ticketing plugin to sell tickets?
No. The Hi.Events widget is a few lines of HTML pasted into a Custom HTML block, which is part of the WordPress block editor. There is nothing to install, activate or update, and no plugin that can conflict with your theme. Tickets, orders, payments and check-in all live in Hi.Events.
Does it work with Elementor, Divi or another page builder?
Yes. Elementor, Divi, WPBakery and the other page builders each have an HTML or code element. Paste the code from Widget Embed into that element; the div and the script line can sit together. The widget only needs a place that renders raw HTML.
Will the widget slow down my WordPress site?
The script line loads with the async attribute, so the browser fetches it alongside your page instead of waiting for it. The widget itself renders inside the block once the page is ready.
Does it work on WordPress.com?
On WordPress.com the Custom HTML block accepts script tags only on a paid plan with hosting features activated, according to WordPress.com's help center. On the free plan the script is removed when you save. If that is your situation, link a button to your event page instead.
Why did my script tag disappear after saving?
WordPress strips script and iframe tags from users who do not have the unfiltered_html capability, such as Contributors. Ask an Administrator to add the block. A security plugin can also remove scripts; if the widget does not appear, allow scripts from app.hi.events in its settings.
Can I show the widget on more than one page?
Yes. Paste the code into a Custom HTML block on each page. Use the same saved widget everywhere and the changes you save in Hi.Events reach all of those pages, with views and orders counted together.
Can I embed a buy button, my lineup or my schedule instead?
Yes. An event's Widget Embed has four types: Tickets, Button (a button that opens tickets in a pop-up), Lineup and Schedule. Each one goes into a Custom HTML block the same way.
What does it cost to sell tickets on WordPress with Hi.Events?
There is no charge for the widget, no monthly fee and no plugin licence. Free tickets are free. Paid tickets carry the Hi.Events platform fee of 1.25% plus a small fixed amount per ticket, which you can pass to the buyer at checkout, and Stripe's standard card rate.See pricing →

Put tickets on your WordPress site today

Create your event, open Widget Embed, paste the code. No credit card, no sales call.

Free events cost nothing. Paid tickets are 1.25% + $0.60, with no monthly fee and no contract — see the full pricing.