These docs are aimed at those who are integrating Intilery into their marketing stack and will give you a guide to getting started, what you need to prepare to make sure you can build the best customer engagement automations for your business.
Intilery is a modern Customer Engagement Platform, combining a Customer Data Platform, Single Customer View, Dynamic Content, Audiences, Journeys and Campaign delivery, which means that we provide a platform that simplifies the collecting and using of data from customers of your digital (and offline) properties (websites, apps, EPOs, telematics, policy systems, etc). With Intilery , you can collect, transform, utilise, and send first-party customer data in a GDPR complaint we, with privacy at the heart of what we do. We simplify the process of collecting data and using it effectively, allowing you to spend more time using your data, and less time trying to format, transport and collect it.
You can also enrich the customer data you collect by connecting data from your other tools and integrations, and then aggregate it to monitor performance, inform decision-making processes, and create uniquely customized user experiences.
In its very simplest form, Intilery generates messages about what’s happening in your site or app, then translates the content of those messages into different formats for use by the products within the Intilery platform (email, journeys, audiences etc.). The Intilery servers also archive a copy of the data to build up the Intilery Single Customer View.
Intilery's libraries generate and send messages to our tracking API in JSON format. We provide a standard structure for the basic API calls, along with a recommended JSON structure (also known as the ‘Schema’) that helps keep the most important parts of your data consistent, while allowing great flexibility in what other information you collect and where.
When you implement Intilery, you add our code to your website, app, or server, which generates messages based on specific triggers you define. At its very simplest, this code can be a snippet that you copy and paste into the HTML of a website to track page views. It can also be as complex as Intilery calls embedded in a React mobile app to send messages when the app is opened or closed, when the user performs different actions, or when time based conditions are met (for example “ticket reservation expired” or “cart abandoned after 2 hours”).
The most basic Intilery message requires only a
anonymousID; all other fields are optional to allow for maximum flexibility. However, a normal Intilery message has three main parts: the common fields, the “context” object, and the properties (if it’s an event) or traits (if it’s an object).
The common fields include information specific to how the call was generated, like the timestamp and library name and version. The fields in the context object are usually generated by the library, and include information about the environment in which the call was generated: page path, user agent, OS, locale settings, etc. The properties and traits are optional and are where you customize the information you want to collect for your implementation.
The Intilery libraries generate messages about what happens on your interface, translate those messages into different formats for use by destinations, and transmit the messages to those tools.
There are several tracking API methods, which can be called to generate messages. The four most important methods are:
- Identify: who is the user?
- Page and Screen: what web page or app screen are they on?
- Track: what are they doing?
Every call shares the same common fields. When you use these methods it allows Intilery to detect specific type of data, and correctly translate it to send it on to the Intilery platform.