How to Set Up PI Event Master WordPress Plugin in 10 Minutes for Ticketmaster Discovery API

PI Event Master can take a new WordPress site from an empty page to a live, filterable events listing in about ten minutes. The fastest route is to configure only the essentials first: install the plugin, add a Ticketmaster Discovery API key, verify the connection, choose a display style, and publish one shortcode. Styling, importing, automation, and affiliate tracking can follow after the first listing works.

Before you start

You need an administrator account on your WordPress site and a Ticketmaster Developer account. Ticketmaster creates a default application when you register; the application’s Consumer Key is the API key used by PI Event Master. Ticketmaster documents that process in its Discovery API getting-started guide.

Minute 1–2: install and activate the plugin

1. In WordPress, go to Plugins → Add New Plugin → Upload Plugin.
2. Select the PI Event Master ZIP file, choose Install Now, and then Activate.
3. Open Settings → PI Event Master.

If your licence includes a key, open the License Key tab, enter it, and activate it. The licence tier controls access to Business and Developer features, but a basic live listing can be configured before those advanced workflows are needed.

Minute 3–4: get your free Ticketmaster API key

1. Register or sign in at the Ticketmaster Developer Portal.
2. Open your default application.
3. Copy its Consumer Key. This is the value Ticketmaster expects in the Discovery API’s apikey parameter.

Keep the key private. It belongs in the WordPress administration screen, not in page content, screenshots, or public code examples.

Minute 5: connect PI Event Master

In PI Event Master, open the API Config tab and paste the Consumer Key into the Ticketmaster API key field. Save the settings and use Test API. A successful test confirms that WordPress can reach Ticketmaster and that the key is valid. If the test fails, check for an accidental space before or after the key, security rules blocking outbound HTTPS requests, or a newly created key that has not yet become available.

Minute 6–7: choose sensible live-event defaults

Open Live Settings. For a first listing, use:

• Default events per page: 12
• Default display style: Grid — 3 columns
• Default radius unit: miles or kilometres for your audience

Then open Live Event Fields and keep the fields that help a visitor decide: date, venue, city, category, price range, and the ticket button. You can enable virtual detail pages later; when you do, also review Auto-import on First View so indexed URLs do not disappear when Ticketmaster removes expired events.

Minute 8–9: generate your first listing

Open the Shortcode Builder. Select Live — Ticketmaster API, choose a layout, set the number of events, and add one useful location filter. For example:

[tm_events source="live" size="12" style="grid" pagination="yes" city="Chicago"]

Copy the generated shortcode, create a WordPress page, add a Shortcode block, paste the code, and publish. For a ZIP-based directory, use a postal code and radius instead of a city. Avoid combining too many filters on the first test; an empty result can simply mean the query is too narrow.

Minute 10: enable caching and perform a final check

Open the Caching tab, enable caching for live API results, and start with a one-hour expiry. Each unique shortcode or widget query receives its own transient, reducing repeated Ticketmaster calls and improving load time.

View the published page in a private browser window. Confirm that event cards appear, pagination works, ticket links open correctly, and the layout collapses cleanly on mobile. Your first listing is now live. The next useful upgrades are imported events for permanent WordPress content, affiliate tracking, city landing pages, and scheduled Business-tier imports.

Quick troubleshooting checklist

• No results: remove keyword, category, or radius filters and test a broad city query.
• Invalid API key: copy the Consumer Key again and save before retesting.
• Old output: flush the live cache or append ?piwpt_nocache=1 while logged in as an administrator.
• Shortcode displayed as text: use a WordPress Shortcode block rather than a Code block.