Embedded Listings Marketing Support

Table of Contents

Where did the Basic and Marketing Helper options go? Standard Version with Marketing Support Note Standard Version with Marketing Support Setup Standard version with Marketing Support Integrations & Events Web Developer version with JSON output Web Dev JSON Output Logic Web Developer version with JSON output Setup Web Developer Version with JSON Output Metadata & Events

When using the Embed feature, it is essential to note the various levels of Marketing support. This is based on the selection of the below-embedded codes:

Standard Version with Marketing Support
- Provides marketing support for additional Event Listings integrated Marketing Accounts.
Web Developer Version with JSON Output
- Provides a snippet that will fire events from the iframe to the parent website for interpretation.

Where did the Basic and Marketing Helper options go?

The Basic and With Marketing Helper embed options are no longer shown in the Admin UI.

Existing embeds remain live and valid — you are not losing sales.

For new or updated embeds, use the two new options.

The option formerly called With Advanced Marketing Helper is now the Standard version with marketing support.

If you switch to the Standard version, ensure that your GA4 and Meta IDs are saved in the Marketing Accounts Integration section of Admin. Tracking will then be applied automatically (no need to add IDs into the embed code).

Standard Version with Marketing Support

The "Standard version with marketing support" code option provides marketing analytics to all "Event Listings" supported marketing attribution companies listed on the Marketing Accounts Integration Admin page (with some exceptions, such as Google Tag Manager).

Note

If a user opts out of cookies and tracking on the client's website, no marketing data will be pushed to third-party marketing attribution companies.

Standard Version with Marketing Support Setup

Copy and paste the snippet from the "Standard version with marketing support" into the desired location of your website.

To ensure marketing analytics flow through the "Standard version with marketing support" code, confirm that any desired "Event Listings" supported marketing attribution companies listed on the Marketing Accounts Integration Admin page have been populated and enabled.

Below is an example of tracking the embed firing the add to cart event to Snapchat through the Snap Pixel Helper Chrome extension.

All integrations for the Standard version with marketing support will only support one marketing attribution ID.

With the exception being any Event Listing supported marketing integrations that have been established in the Marketing Accounts Integration Admin page to support more than one ID (Ex: Google Analytics 4).

If you plan to use more than one ID per line of code, we recommend using the embedded 'Web Developer version with JSON output' option. If you need assistance with using this option, please get in touch with your website developer.

Standard version with Marketing Support Integrations & Events

The Standard version with marketing support is designed for users who need an embedded solution with marketing tracking that mirrors their Event Listings setup and requires minimal coding ability.

The Standard version with marketing support code supports the standard events setup to fire on existing Event Listings supported marketing integrations.

The following Event Listings marketing integrations are not supported with the advanced marketing helper.

Google Tag Manager

If you're looking for a broader range of marketing solutions, we recommend using either Event Listings non-embed or the 'Web Developer version with JSON output' embedded option.

Events reporting to real-time or same-day reporting in integrations like Meta and GA4 may take up to 30 minutes to appear in third-party reporting analytics.

Web Developer version with JSON output

The Web Developer version with JSON output option enables the firing of standard events from the embedded iframe to the 'listening' parent website.

Reminder: If a user opts out of cookies and tracking on your website, the webpage should respect these privacy settings before taking action on any events fired from the embedded iframe.

Web Dev JSON Output Logic

The Web Developer version with JSON output empowers the embedded iframe to transmit data related to checkout actions. When an action has a valid hook, the iframe will send a JSON-formatted object outside of itself to the browser window.

This data can be easily read and utilized to pass information to your marketing plugins or for any other JavaScript applications you may have.

Web Developer version with JSON output Setup

Copy and paste the snippet from the Web Developer version with JSON output into the desired location of your website.

Below is an example of the complete Web Developer version with JSON output code. When copying/pasting the code from ShowClix, ensure that you scroll all the way down in the code box to copy the entire snippet.

After placing the code onto your webpage, your web developer will need to set up listeners for actions occurring within the embedded iframe.

As mentioned earlier, when an action with a valid hook occurs, the iframe will push a JSON-formatted object outside of itself and into the browser window. To make this work, the web developer needs to define on their parent page 'what the library is and what is expected to be heard.' This typically involves using window.* where * represents the desired marketing analytics software like Google Tag Manager, Meta, or Snapchat, followed by specifying what message.actions ==.

Once the data is received from the iframe, you can read it and use it to pass information to your marketing plugins, marketing account integrations, or any other JavaScript applications you may have.

There is no current capability for a web developer to modify the marketing snippet through brute force. This means they cannot resize the iframe, change its styling/color, or add additional code to the script.

Web Developer Version with JSON Output Metadata & Events

The Web Developer version with JSON output is designed to fire data to the parent website and not to third-party marketing account integrations.

Metadata that is fired from the iframe can be seen in the JSON output format:

{
    "action": hookType, ("purchase","addToCart","removeFromCart","addPaymentInfo","viewCart","beginCheckout","pageView","reservationCreated","couponSubmitted")
    "eventID": event_id,
    "value": total_value_of_the_order_if_present,
    "currency": ISO_currency,
    "sellableItems": [ // present for reservation actions and/or payment
        {
            "sellableType": item_category, ("ticket", "product", "bundle")
            "sellableID": item_id,
            "sellableName": item_name,
            "quantity": quantity,
            "price": price,
        },
    ...
    ],
    "paymentItems": { // present for payments and finalizing
    "orderId": order_confirmation_code, //transactionID in GA4
    "paymentType": payment_type, ("Credit Card", "Buy Now Pay Later")
    "page": checkoutLocation, // present on "pageView" events e.g. ticketPicker
    "pageTitle": page_title_from_html,
        "coupons": [{couponCode: "..."}], // present on "couponSubmitted" events
}

The embed checkout logic flow is seen in the following image:

Developers may also use the ShowClix API at https://technically.showclix.com to reference data from the iFrame to endpoints on our ShowClix tables.

Below is a list of the fired marketing events associated with the Web Developer version with JSON output:

addPaymentInfo
addToCart
beginCheckout
cartExpired
clearCart
couponSubmitted
expiresIn (cart has 60 seconds left)
insuranceAccepted
insuranceChanged
insuranceDeclined
pageView - fires on reservation complete page or when a consumer takes action on the embed (such as clicking get tickets to load the ticket picker)
purchase
removeFromCart
reservationCreated
viewCart