Skip to main content

Connecting Seeka to Eventbrite

Installation takes around 2 minutes and can be done by anyone with admin access to your Eventbrite organiser account.

For Eventbrite organisers, it is recommended that you connect Seeka anywhere you collect data, such as your ticketing outlet, official website, and pre-registration platforms.

šŸ’” Early access: The Eventbrite integration is rolling out now. If you can't see it in your Eventbrite account yet, contact your account manager to be added to early access.

Before you start

You'll need:

  • Admin access to your Eventbrite organiser account

  • Access to your Seeka account

The whole thing takes around 2 minutes. If you'd rather your Eventbrite account manager set it up for you, use the Copy instructions for account manager button on the Seeka setup screen and send it straight to them.

Connect Seeka to Eventbrite

Step 1 - Open the setup screen in Seeka

  1. Log in to your Seeka account

  2. In the left-hand menu, click Apps

  3. Search Eventbrite

  4. Click Connect

Keep this tab open - you'll copy three identifiers from here in a moment.

Step 2 - Find the Seeka section in Eventbrite

  1. In a new tab, log in to your Eventbrite organiser account

  2. Click Manage events and select the event you want to track

  3. In the left-hand menu under your event, go to Marketing, then Tracking pixels

  4. Scroll down to the Advanced tracking through Seeka section near the bottom of the page

  5. Click Set up Seeka

  6. Choose your scope: This event or All events

šŸ’” Choosing All events means every current and future event in your account is tracked automatically, so you don't have to repeat this for each new event. This is what we recommend for most organisers.

Step 3 - Paste in your Seeka identifiers

Back in Seeka, copy each identifier using the buttons on the setup screen and paste it into the matching field in Eventbrite:

  • Organisation ID - identifies your organisation in Seeka

  • Public Key - your Seeka SDK key

  • Instance ID - identifies your Seeka instance

Double-check each value lands in the right field, as a mismatched identifier is the most common reason data doesn't flow.

Step 4 - Turn on attendee shared data

Still in Eventbrite, scroll to the Attendee shared data section and tick all four checkboxes:

  • First name

  • Last name

  • Email

  • Phone number

āš ļø Enable all four for peak ad performance. These fields are what let Seeka match your attendees back to the people who saw your ads. Leaving any of them off directly reduces match rates and weakens attribution.

Step 5 - Save and finish

  1. Click Save in Eventbrite

  2. Return to Seeka and click Complete installation

šŸ’” It may take a few hours for the card to say "connected" in Seeka, based on data flow from Eventbrite, so don't worry if you don't see it in the product straight away! Conversions can take 24ā€“48 hours to appear across all of your ad platforms.

Avoiding duplicate tracking

Any tracking pixels that are connected in Seeka must be removed from the native pixel slots in Eventbrite. If the same pixel fires from both places, your conversions will be counted twice and your reporting and ad optimisation will be skewed.

Example: if you already use Eventbrite's built-in Meta pixel and you now want Seeka to handle Meta tracking, delete the Meta pixel from Eventbrite's native pixel section before switching it on in Seeka.

šŸ’” Pixels belonging to other marketers, or to another instance of Seeka, are fine to leave in place.

If you need a hand untangling an existing setup, see Understanding Pixel Implementation and Duplicate Firing Pixel Events.

What Seeka tracks on Eventbrite

Seeka captures the same funnel events as Eventbrite's built-in pixels, but delivers them server-side for better reliability:

  • View Content - someone views your event listing page

  • Add to Cart - someone selects tickets

  • Initiate Checkout - someone starts the checkout process

  • Purchase - someone completes a ticket purchase

These are set up automatically - no additional event configuration is required for your Eventbrite events.

Confirming it's working

  1. Open your Seeka dashboard and look for incoming View Content, Add to Cart, Initiate Checkout and Purchase events

  2. Check your connected ad platforms to confirm conversions are landing there too

Allow 24ā€“48 hours before troubleshooting, as data doesn't appear everywhere instantly.

Connecting your data destinations

A data destination is somewhere you would like to send data to, such as Metaā„¢ Ads, TikTokā„¢ Ads or Google Analytics 4ā„¢. The great news is that you only have to connect each destination once, and then anywhere you install Seeka will automatically send that rich data to your connected destinations.

Each destination has its own short guide. Follow the one you need:

Good to know

  • Mobile app purchases aren't tracked yet. Seeka currently supports web-based purchases on Eventbrite only.

  • Consent is handled by Eventbrite. Eventbrite's consent tool controls when attendee data is sent to Seeka, based on user consent and local privacy laws. Seeka is classified as non-essential tracking, so data only flows where the attendee has consented.

  • Activating Seeka creates a direct relationship with Seeka. When you switch it on, you're setting up data processing directly with us, not through Eventbrite.

Cross-domain tracking

Cross-domain tracking is required if you're running ads to your own website and then sending users through to your Eventbrite event page to complete their purchase. Without it, Seeka can lose important context (like Meta click IDs and UTMs) once a user moves from your site to Eventbrite, which impacts attribution.

Example: You run ads on your official website, and a user then clicks through to your Eventbrite event page to buy a ticket. Set your Source domain to your official site URL and your Destination link to your Eventbrite event URL, with UTM behaviour set to UTMs from the browser session so ads landing on your page are attributed through.

For the full step-by-step, follow the Cross-Domain Tracking Setup Guide.

Note: Cross-domain tracking cannot work if the link in the button is wrapped in a link shortener like Bitly.

Connecting external websites

Connecting your external websites to Seeka is highly recommended for attribution and data collection. Seeka can be installed almost everywhere, and if we don't support a source yet, please let us know, and we'll get it done.

We support external sources in a variety of ways, including:

  • Official apps, which you can find in the Apps section of Seeka

  • A Script tag can be placed in the header code of most platforms.

Note that your official website and select pre-registration platforms will require manual event setup, as only the 'View Page' event is set up automatically. Seeka's Express Setup Tool makes this quick.

Where to get help

  • Questions about your Seeka account, data destinations or the Seeka dashboard - start a chat with us here in the Help Centre.

  • Questions about Eventbrite's Tracking pixels page or your Eventbrite account - contact Eventbrite support.

Related Articles
Did this answer your question?