Insights Tracking
Sending the right events helps conducting performance analysis with precision.
To conduct a performance analysis of your Experiments, Personalizations, components and Audiences, any system requires two types of information:
What is a visitor seeing - Tracking individual components and Experiences that are seen help to identify what can be attributed to your conversions.
Conversions events - Knowing which visitors converted, including any additional properties of the conversion, make sure that the performance of your Experiences can be measured. At Ninetailed, conversions events are part of your regular track events.
In order to use Insights, these corresponding events need to be sent to Ninetailed. The following chapters explain how to do so. If you are already sending conversion events to a different analytics software such as Google Analytics, we recommend using the same set up, triggers and events for Ninetailed.
Sending view events
Ninetailed's Insights Plugin automatically sends events when any element wrapped in a Ninetailed SDK <Experience> component has been present within the user's viewport for a specified amount of time. This covers the majority of Ninetailed personalization and experiment implementations.
To track the visibility of Experiences not implemented using the SDK's <Experience> component, you should use the observeElement method available on the Ninetailed Instance to register a custom element for tracking.
Delivering Ninetailed Experiences requires a developer to implement code. Have a look at our developers section for details about our integrations and SDKs.
Sending Conversion Events
Conversion events can be sent to Ninetailed just like any other event, using the track method. These events can be sent in a number of ways.
Track events via Google Tag Manager
The easiest way to send conversion events is by sending track events from an existing tag manager. If you're using Google Tag Manager, we recommend leveraging the Ninetailed Google Tag Manager template to quickly create a tag to call track with your existing Google Tag Manager triggers.
This tag configuration would call:
each time YOUR_TRIGGER fires. Your event name and property keys & values can use data layer variables for dynamic population.
Track events via the SDK or API
Developers can send conversion events via our SDKs or API. For more information, see our sending events developers section and Experience API section.
Track events via Customer Data integrations
If you are using other customer data tools such as Segment, you can also send conversion events to Ninetailed via our Customer Data integrations.
Last updated
