Skip to main content

Connecting Seeka to Moshtix

Connect Seeka to your Moshtix events so every funnel event flows to your ad platforms.

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

Before you start

You'll need:

  • Admin access to your Moshtix Dashboard

  • Access to your Seeka account

The whole thing takes around 1 minute per event and can be done by anyone with admin access to Moshtix.

Connect Seeka to Moshtix

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 Moshtix

  4. Click Connect

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

Step 2 - Find the Seeka section in Moshtix

  1. In a new tab, log in to your Moshtix Dashboard

  2. Navigate to Events and click on the name of the event you want to install Seeka on

  3. Navigate to Reports/Tracking in the left-hand menu

  4. Scroll down to tracking codes

  5. Remove any other tracking pixels from platform slots that you will be connecting via Seeka (see Avoiding duplicate tracking below)

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 Seeka field in Moshtix:

  • Organisation ID

  • Public Key

  • Scope ID

Step 4 - Complete Set-up

  1. Click the save button in Moshtix

  2. Return to Seeka and click Complete installation

šŸ’” The Seeka connection is set up per event in Moshtix, so repeat Steps 2ā€“4 for each event you want to track. It may take a few hours for the card to say "connected" in Seeka based on data flow, and conversions can take 24ā€“48 hours to appear across your ad platforms.

Avoiding duplicate tracking

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

šŸ’” Pixels unrelated to you, such as from another marketer, 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 Moshtix

Seeka captures your funnel events and 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 Moshtix events. [VERIFY with Dan: confirm final event list for Moshtix]

Confirming it's working

  1. Open your Seeka dashboard and look for incoming events from your Moshtix pages

  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.

Troubleshooting common issues

No events appearing in Seeka

  1. Double-check that all three identifiers (Organisation ID, Public Key, Scope ID) are in the correct Seeka fields in Moshtix. A mismatched identifier is the most common reason data doesn't flow.

  2. Confirm the integration is applied to the event you're testing - the connection is per event, so a new event won't be tracked until you repeat the setup on it.

  3. Confirm you clicked Save in Moshtix after pasting the identifiers.

  4. Check that the event has live sales activity to generate events.

Conversions are appearing in Seeka but not in your ad platforms

  • Allow 24ā€“48 hours from the first event - this is normal processing time.

  • Confirm your data destinations (Meta, TikTok, Google Ads, etc.) are connected in Seeka under Apps.

  • Destinations only receive events from the point they're connected - check whether the destination was connected before or after the events fired.

Duplicate conversion events

The most likely cause is the same pixel firing from both Seeka and a native Moshtix tracking code slot. See the Avoiding duplicate tracking section above, and remove any duplicate pixel installations before re-testing.

If you've worked through the above and are still stuck, start a chat with us and include your Organisation ID and which events you're not seeing.

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:

Cross-domain tracking

Cross-domain tracking is required if you're running ads to your own website and then sending users through to your Moshtix 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 Moshtix, which impacts attribution.

Example: You run ads on your official website, and a user then clicks through to your Moshtix event page to buy a ticket. Set your Source domain to your official site URL and your Destination link to your Moshtix 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.

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 your Moshtix Dashboard or its settings - contact Moshtix support.

Related Articles
Did this answer your question?