Eventbrite events on your own site.

Google Events search is a dedicated SERP feature that surfaces upcoming events for queries like 'pottery class near me,' 'tech conferences December 2026,' or '[city] yoga workshop this weekend.' It pulls almost exclusively from pages that emit valid Schema.org Event JSON-LD with a precise set of fields: Event with name, startDate, endDate, eventStatus, and eventAttendanceMode; nested Place with name, address (PostalAddress with streetAddress, addressLocality, addressRegion, postalCode), and ideally geo coordinates; nested Offers with price, priceCurrency, availability (InStock, SoldOut, PreOrder), and url; and ideally Organizer and Image. If your event page does not emit this exact structure, it does not appear in the Events SERP, no matter how authoritative your domain is. The Eventbrite organizer page itself does emit it, but it lives at eventbrite.com/o/your-name, not on your own domain, and any visitor who lands there has already left your site. The only way to keep visitors on your site and still rank in Google Events is to embed an Eventbrite events widget that injects valid Schema.org Event JSON-LD on your own URL. Poper does exactly that. Every event the widget renders ships server-side with the full Schema.org Event tree, including EventStatus changes (Eventbrite's cancelled or postponed events flow through automatically), EventAttendanceMode (OfflineEventAttendanceMode for in-person, OnlineEventAttendanceMode for virtual, MixedEventAttendanceMode for hybrid), and Offers nested per ticket tier. Most third-party Eventbrite embeds skip this completely, which is why their customers' events never reach the Events carousel.

Eventbrite supports a deep ticket-tier model: Early Bird, General Admission, VIP, comp tickets, group discounts, donation tiers for non-profits, sponsorship packages, and add-ons. The way you surface those tiers on your own site directly affects conversion. The two failure modes most embed widgets fall into: showing only the cheapest tier (so a $25 General Admission shows up but the $499 VIP that would have converted a corporate buyer never appears), or showing every tier in a flat list with no sense of urgency. Poper's widget renders every active tier with live availability counts, sold-out badges per tier (not just per event), 'Almost sold out' threshold styling, and an optional 'X tickets left' urgency cue when capacity drops below a configurable threshold. For non-profits, donation tiers and sponsorship packages render with custom labels (for example 'Gold Sponsor' instead of 'Ticket'). For conferences, multi-day passes versus single-day passes versus workshop add-ons each get their own visual treatment. The Schema.org Offers JSON-LD nests one Offer per tier with the right price, currency, availability, and url, so Google Events can show 'From $25' in the SERP card and lead the high-intent buyer straight to your tier-specific Eventbrite checkout.

Before 2020, virtual was a fringe format, mostly for corporate webinars. After 2020, it became permanent. Eventbrite reports that more than half of organizers now run at least one virtual or hybrid event per year, and the pure-virtual segment alone grew over 1000% during 2020-2021 and stabilized at far above pre-COVID baselines. The widget you embed has to handle three event modes correctly. In-person events need a venue card with full PostalAddress, an embedded map (or a 'Get directions' link), and timezone-aware start times. Virtual-only events need a 'Virtual' badge, the join link gated behind registration (never shown publicly), and visitor-local timezone display so attendees in different geographies all see the right time. Hybrid events need both: physical venue plus virtual access, with clear messaging about which ticket tier gets which mode of access. The Schema.org spec handles all three via EventAttendanceMode and a virtualLocation property for online and hybrid events. Poper's widget renders the right card layout automatically based on the Eventbrite event metadata, and the JSON-LD reflects the correct attendance mode. This matters for Google Events search because the SERP filters allow users to narrow to 'in person' or 'online,' and your event only appears in the right filter if EventAttendanceMode is set correctly.

The events platform space consolidated dramatically over the last few years. Hopin, once Eventbrite's biggest virtual-event competitor with a $7.75 billion peak valuation in 2021, sold its Events and Sessions business to RingCentral in 2023 after the virtual-event boom cooled. Universe, a peer-to-peer ticketing platform, was acquired by Ticketmaster (Live Nation) back in 2017 and quietly folded into Live Nation's stack. That leaves Eventbrite as the dominant independent platform for the long tail of event organizers (non-enterprise conferences, non-profits, classes, meetups, music venues, community events). For most organizers reading this, choosing 'where to host the event' is already settled (Eventbrite). The unsolved question is 'where to display the event,' and that is where the embed widget matters. Eventbrite's own native embed has not been substantially redesigned in years, emits limited Schema.org markup (Event but often without complete Offers or Place coverage), is hard to brand to match a custom site, and offers no multi-organizer combined feed for brands with regional chapters. Hopin and Universe never had standalone embed widgets that worked for non-paying customers. So the practical comparison for most organizers in 2026 is: Eventbrite native embed (free, limited) versus Poper Eventbrite events widget (free plan, full Schema.org coverage, multi-organizer, brand-match styling, hybrid event support).

Event pages are above-the-fold for the kind of visitor who is most likely to convert, which means the widget you embed is on the critical rendering path for your conversion rate. The worst Eventbrite embeds load 200KB+ of synchronous JavaScript, fetch events on every page view (no caching), inject styles that override your design system, and hit Eventbrite's API directly from the browser (which means visitors in a region with poor Eventbrite latency see slow-loading event cards). Poper's widget loads asynchronously, fetches events from a global CDN edge cache so visitors never hit Eventbrite directly, uses scoped CSS that will not bleed into your design tokens, and clocks in under 40KB gzipped with the JSON-LD inlined server-side so Googlebot reads it on first request. On GDPR: the widget never sets cookies, never collects PII unless a visitor clicks through to checkout, and the OAuth token between Poper and Eventbrite stays server-side. EU visitors see the same widget as US visitors with no consent banner trigger required. On API resilience: Eventbrite's API v3 has been stable for years, but rate limits can bite organizations with many concurrent embeds. Poper handles this by batching requests, caching at the edge with smart invalidation when you publish or update an event, and falling back to the last known good event list during any rare API outage so your site never shows a broken state. The operational reality is that an Eventbrite events widget is a piece of infrastructure that has to keep your event calendar live and your Schema.org markup intact for every page view, every search bot crawl, every social share. Most embed tools treat it as a feature checkbox. Poper treats it as the live front door to your ticket sales.