Eventrise

Descripción

The official Eventrise plugin lets you sell tickets right from your own WordPress site. Connect your Eventrise organization once, then add events anywhere with blocks, Elementor widgets or shortcodes.

Five ways to embed

• Inline iframe: the full Eventrise checkout, right on the page.
• Popup button: a “Get Tickets” button that opens checkout in a popup. It can apply a promo code and preselect tickets.
• Events grid: a card grid of all your published events. Each card opens checkout in a popup.
• Events page: your organizer events page on your own site, with an optional featured section, upcoming events grouped by day, and a month calendar you can switch to.
• Auto-link: any <a> link to your Eventrise checkout opens in a popup. No setup needed, and it works in any theme, page builder or widget. Links to your event pages on eventrise.com can open in the popup too.

Checkout presets, height and sales tracking

New in 1.5.0:

• The Get Tickets button takes a promo code, a ticket and a quantity: [eventrise_button event="summer-fest" label="Get 4 tickets" promo="GROUP4" ticket="{ticket-id}" quantity="4"]. Checkout opens with the code applied and the tickets selected, and the buyer still confirms them. The ticket ID is a UUID from the ticket in your Eventrise dashboard. Quantity runs from 1 to 20.
• The inline embed takes a promo code, and can fit its height to the checkout so visitors never scroll inside it: [eventrise_embed event="summer-fest" promo="EARLY" autoheight="yes"]. The block has the same options in its sidebar.
• Each sale adds an eventrise_purchase event to Google Tag Manager’s dataLayer, with the order ID, total and currency, so you can count it as a conversion. Opening the popup adds eventrise_checkout_open. The page also gets eventrise:checkout-open, eventrise:checkout-complete, eventrise:checkout-expired and eventrise:checkout-close events on document for your own scripts.
• The plugin remembers the campaign a visitor arrived with for 30 days, so a sale is credited even when they land on one page and buy on another.
• The popup fills the screen on phones.
• Elementor widgets: see below.

Elementor widgets

New in 1.5.0: with Elementor active (the free version is enough), the Elementor panel has an Eventrise category with four widgets. Search the panel for “tickets”, “checkout” or “eventrise” to find them.

• Eventrise Buy Tickets: the Get Tickets button. Enter the event slug and, if you like, a label, a style, a promo code, a ticket ID and a quantity. On the Style tab, set its alignment, colors and corner radius.
• Eventrise Checkout (inline): the full checkout on the page, with an optional promo code and a height that fits the checkout.
• Eventrise Events: your events page, with the same options as the Eventrise Events block.
• Eventrise Events Grid: the card grid, with the same options as the Events Grid block.

Each widget shows exactly what the matching block and shortcode show. Without Elementor, the plugin loads none of this.

Events block & shortcode

New in 1.2.0: the Eventrise Events block (in the Eventrise block category) and the matching [eventrise_events] shortcode show your organizer events page on your own site, in the same design as your Eventrise landing page.

It has two parts. The optional Featured section shows the events you’ve featured: one or two as full-width cards, or three in a three-column grid. The Events section below it switches between a list and a calendar. The list groups upcoming events by day and shows the title, short description, date · time · location, and a Buy Tickets button that opens Eventrise checkout in a popup. Once sales end, a View Event link and a “Sales have ended” label take its place. The calendar is a month grid starting on Sunday. Each day links its events to their public event pages, you can move between months, and it has a compact layout on phones.

Attributes (block attribute / shortcode attribute: default):

• organization / organization: empty. Uses the organization slug from Settings → Eventrise. Set it to show another organization’s public events.
• showFeatured / show_featured: true. The featured events strip. It only shows when the organization’s Eventrise landing page is turned on. Otherwise the section is left out.
• showList / show_list: true. The list of upcoming events, grouped by day.
• showCalendar / show_calendar: true. The month calendar. Turn off both the list and the calendar to show only the featured strip. If featured is off too, the block shows a notice that only editors can see.
• defaultView / default_view: list. Either list or calendar, whichever should open first. If only one is turned on, that one opens.
• limit / limit: 0. The most upcoming events to show in the list. 0 shows all of them (up to 100). This doesn’t affect the featured strip or the calendar.
• heading / heading: empty, which shows “Events”. The section heading.
• featuredHeading / featured_heading: empty, which shows “Featured Event” or “Featured Events”. The featured section heading.

The block also supports wide and full width and an HTML anchor. On/off shortcode attributes accept yes/no, true/false, 1/0 and on/off. For example:

[eventrise_events show_calendar="no" limit="6" heading="Upcoming shows"]

[eventrise_events organization="other-org" default_view="calendar"]

Built for WordPress.org standards

• Blocks are rendered on the server, which is good for SEO and accessibility.
• All assets are bundled. No scripts load from other sites.
• No telemetry: the plugin never reports anything about your site or your visitors to us. Sales events go only to the Google Tag Manager you already run, and you can turn them off.
• Licensed GPL-2.0-or-later.
• Translation-ready.
• Multisite-compatible.

External services

This plugin connects only to Eventrise’s own services.

Eventrise API: read-only requests for your organization and its events. Without an API key, the plugin uses four endpoints:

• GET /api/v1/organizations/{slug-or-id}: your organization’s name and public settings (to check your slug on the settings page).
• GET /api/v1/events?organization_id={slug-or-id}: the public list of your published events (Events Grid block, the editor’s event picker, and the Events block’s list and calendar).
• GET /api/v1/organizations/{slug}/featured_events: your featured events (only for the Events block’s featured section). Returns a 404 when your Eventrise landing page is turned off, and the section is left out.
• GET /api/v1/events/{id}: a single event. The editor reads it through the plugin’s REST proxy. With Open event page links in the checkout popup on, the visitor’s browser also asks it whether a clicked eventrise.com link is an event page, sending only the event’s address name and no cookies. When the answer is “not found”, the popup closes and the link opens as usual.

If you add the optional API key, the Events Grid block, the editor’s event picker and the single-event read use your organization’s authenticated endpoints instead (GET /api/v1/organizations/{slug}/events and GET /api/v1/organizations/{slug}/events/{id}), and send the key as a bearer token. The Events block never does.

The host is https://api.eventrise.com (Production) or https://api.dev.eventrise.com (Staging), set by the Environment setting.

Eventrise Checkout at https://checkout.eventrise.com (Staging: https://checkout.dev.eventrise.com): embedded as an iframe to handle ticket purchases. When a visitor arrived on your site from a tagged link, the campaign tags in that address (utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id, ref, gclid, gbraid, wbraid, fbclid, msclkid, ttclid, er_mid) are added to the checkout’s address, so Eventrise can tell the organizer which campaign the order came from. Nothing else from the page’s address is sent. A promo code, ticket or quantity you set on a button or embed is added to the checkout’s address too.

The campaign tags are kept for 30 days in the visitor’s own browser (localStorage, key eventrise_attribution), so a visitor who lands on one page and buys on another is still credited to the campaign. They never reach your server and are sent only to Eventrise Checkout, when the visitor opens it. If your site uses the WP Consent API, the plugin keeps the tags only after the visitor allows statistics cookies, and deletes any kept earlier while they have not; when the visitor allows them later, the plugin starts keeping them. The ad click ids (gclid, gbraid, wbraid, fbclid, msclkid, ttclid) also need marketing cookies: without them they are neither kept nor sent, and any kept earlier are deleted. To keep nothing in visitors’ browsers at all, add add_filter( 'eventrise_remember_campaign', '__return_false' ); to your theme or a small plugin. The checkout still receives the tags of the page the visitor opens it on, which needs no storage.

Eventrise website at https://eventrise.com (Staging: https://dev.eventrise.com): where the Events block’s “View Event” links go. They open the public event page https://eventrise.com/{organization}/{event} in a new tab. Nothing loads from that host until a visitor clicks one of those links.

By using this plugin, your visitors will load content from checkout.eventrise.com when they reach an embedded checkout. See Eventrise’s Privacy Policy and Terms of Service.

Third-party assets

The Events block uses two typefaces. Both are bundled with the plugin under assets/fonts/ with their license files, and served from your own site, never from a CDN:

• Bricolage Grotesque: © The Bricolage Grotesque Project Authors. SIL Open Font License 1.1.
• Rethink Sans: © The Rethink Sans Project Authors. SIL Open Font License 1.1.