Skip to main content

Installing Seeka for Oztix™

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

Seeka is designed to be 'no-code' for the majority of installation methods, so you don't need to be nerd level 9 to install. You just need the right access.

Installing Seeka on your outlet

The installation of Seeka on an Oztix Outlet takes around 1 minute and can be implemented by anyone with Admin access to Oztix Studio and the Seeka App.

When using Seeka on your Oztix Outlet, you must ensure the pixels you use with Seeka are not also placed in the browser tracking fields in 'tracking' in Oztix Studio, or events will double fire.

Pixels unrelated to you, such as from another marketing team, are fine to leave.

Video Version ⬇️

Screenshot Version ⬇️

Open Oztix Studio

  1. Open Oztix Studio.

  2. Select the event on which you want to install Seeka.

  3. Navigate to Tracking on the left-hand menu.

  4. Remove any other tracking pixels from platforms you will be connecting to Seeka.

    Note: Pixels you won't be using are ok to be in the browser tracking fields.

  5. Scroll to the bottom of the tracking options until you see the fields for Seeka.

Open the Seeka App

  1. Open the Seeka App and ensure you're in the correct Organisation and Brand.

  2. Click Apps in the left sidebar.

  3. In the All tab, search for Oztix, then click Connect

  4. Copy the Organisation ID from the Seeka App and paste it into the Organisation ID field in Oztix Studio.

  5. Copy the Public Key from Seeka into the Public key slot in Oztix studio.

  6. Save your changes in Oztix Studio, then head back to the Seeka App and hit Complete Installation.

💡 It may take a few hours for the card to say "connected" in Seeka, based on data flow from Oztix, so don't worry if you don't see it in the product straight away!

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 (found in the Apps section of Seeka) and a Script tag that can be placed in the header code of most platforms.

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 (including your Oztix outlet) will automatically send that rich data to your connected destinations.

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

Events automatically tracked on your Oztix outlet

Your Oztix outlet will fire the following events automatically to any connected destinations via Seeka:

  • Page View

  • View Content

  • Add to cart

  • Initiate Checkout

  • Purchase

When your outlet is in pre-registration prior to an event going live, it will fire a 'Lead' event on form submission.

These events are automatically mapped to each destination platform, and their names will vary slightly per platform. The event map library is available HERE.

For festivals, venues, and artists, you would 100% want to set up events on any signup forms, including pre-registration or newsletter forms. Seeka's Express Setup Tool makes this fast and no-code.

Cross-domain tracking

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

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

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

Using the same Meta™ pixel across multiple outlets

If you use the same Meta™ pixel across multiple outlets, the two sections below help you isolate a single show for audiences and conversions. These steps are specific to multi-outlet ticketing setups.

Creating an Exclusion Audience in Meta™

If you use the same pixel across multiple outlets and want to create an excluded audience for a singular show, follow these steps.

  1. Navigate to Audience in Meta™

  2. Hit Create Audience

  3. In the 'Sources' section, select 'Website'

  4. Select the correct data source (pixel).

  5. Select 'Purchase' as your event

  6. Set the retention to 180 days

  7. Set URL or parameter to 'value'

  8. Set the next field to 'contains'

  9. Paste in your Outlet Event ID into the values field

  10. You can find your event ID in your outlet URL

  11. Paste your Event ID into the value field

Creating a Custom Conversion in Meta™

If you use the same pixel across multiple outlets and want to attribute and optimise for a singular event, follow these steps.

  1. In Meta™ Events Manager, navigate to Custom Conversions and hit the Create Custom Conversion button.

  2. Name your custom conversion. This can appear as a column in Meta™ Ads Manager, so keep it brief.

  3. Select your data source (Pixel)

  4. In the Action source field, select Website

  5. Select the event you want to create your custom conversion from. Example Purchase

  6. Go to the Rules section and select 'Event Parameters' in the first field dropdown.

  7. In the field to the immediate right, type 'contents'

  8. In the field dropdown to the far right, select 'contains'

  9. Paste in your Outlet Event ID into Parameter values

  10. Hit Create 🚀

  11. You can find your event ID in your outlet URL

Avoiding double fires on your outlet

After connecting your destinations, ensure the same accounts or pixels are not installed on your ticketing outlet or official website as well, or you will get double fires of events.

Avoiding double event fires on your Oztix outlet

For your Oztix outlet, this is easily monitored in Oztix Studio.

Avoiding double fires on other platforms

To avoid double fires on other platforms, such as your official website or a pre-registration platform, simply ensure that the same accounts or pixels are not installed directly or via plug-ins.

Avoiding double fires via Google Tag Manager

If you use Google Tag Manager, simply disconnect GTM from the platforms where Seeka is running to avoid double fires.

Related Articles
Did this answer your question?