Spotlight features

Feature collections

Data collection

Data integration

The aim with Engage is to create one central instance for all your data handling. Instead of implementing multiple trackers for data collection and numerous integrations to 3rd party services, Engage will let you activate all your needed destination with a push of a button. At the same time as only one single tracker is being utilized for data collection.

Analytics

Knowing your data is key to a successful business and Engage will support you on this mission. Within this section the continuously growing scope of reports are listed. If you are missing a report, please let us know and we can discuss the possibility to add it to our roadmap.

Additional features for ecommerce clients

Personalization

Increase customer satisfaction and lift your sales using the AI-driven product recommendations from Engage.

Learn how to use Engage to collect data and use it to improve your store operations, marketing and third party tools.

What is Engage?

Engage is a Customer Data Platform (CDP) that manage the complete data collection for site owners. The data, will in the next step, be used for improved operations, insights and personalization. Using Engage, a site owner gets all the tools required to drastically enhance the results of everything from Conversion Rate and ROAS to automation and reduced manual labor.

For ecommerce clients, Engage offers an industry solution that activates profound features designed to support store owners in optimizing their online business.

Even though there is a lot of different features within the platform to select from, clients can pick and chose features that fulfills their needs, always having the knowledge that Engage has more to offer when there is a new demand.

How can Engage help you?

Streamline your data collection

Collect your data once, and use it for marketing, analytics, personalization and much more.

Know your customers

Gain insights and more knowledge about your customers. Use it to improve store operations, marketing and customer support.

Automate marketing

Optimize marketing by letting Engage create and sync granular audiences to your preferred ad network.

Personalization

Let your data work for you. Use product recommendations, automated customer audiences and insights to personalize every touch point with your customers.

Start sending data to Engage

Data can be ingested to Engage in many ways using our API. But most start with our easy-to-use JavaScript tracker or, for those being ecommerce clients, using one of the plugins available for the major e-commerce platforms.

Integrations are a fundamental part of Engage that enables our users to send data from various sources to the most critical 3rd party applications that merchants use to succeed with their e-commerce business.

Sources

Ingest data from one, or more, sources to feed Engage and any 3rd party destination with the data they need. Using the sources, you can track and collect the data you need to improve your business or internal processes, and to outperform your competitors.

Destinations

Most merchants use multiple 3rd party applications to run and understand their business. Engage makes it easy to connect well structured, clean and consistent data across all applications.

Welcome to Engage! This guide helps you familiarize yourself with Engage, and takes you through the tasks required to get you up and running.

Create an account

First thing first, sign up for an account to get started. When your user account is created, Engage automatically creates a team account for you. The team account is used to manage your sources, destinations and features within Engage. You can also invite other users to the team to collaborate with you.

Add a source

Engage runs on data. To start using Engage you need to add one or more sources that send data to Engage. The vast majority of our customers uses the JavaScript tracker, which is fully customizable, to get data flowing into Engage.

For Ecommerce clients the quickest way to get started is to use one of the prebuilt plugins to get a pre-packaged setup in place, but you may of course use any of the available sources and APIs to get started.

Add a source:

1. Go to Data Platform > Integrations

2. Select the All sources tab

3. Click the source you want to use and follow the instructions

Explore the features

As you've connected your site and have data pouring into Engage you may start to explore the features of Engage. If you've setup a plugin source, or any of the other sources that provide the required data, you will soon be able to view our analytics reports, use our product recommendations and segment customers and visitors.

Add a destination

A destination is often a third party application or tool that consume data to provide some kind of business value to you. Our most frequently added destinations are Analytics, and Advertising destinations.

Add a destination:

1. Go to Data Platform > Integrations

2. Select the All destinations tab

3. Click the destination you want to use and follow the instructions

Engage needs data to run, and excels in the simplicity of which you can provide data to the platform. When you install Engage, you will need to add some code to your site.

1. Start by adding the code that sends messages to Engage with event data. This is data that holds information about whats going on on your website. It can be when a customer adds a product to cart, when a purchase is made, when a customer signs up for a subscription or when a visitor looks at the pricing page. You can collect any data this way, but we have defined some information Engage requires to run well.

2. In addition to the code that provides Engage with event data you also have the option to send master data (products, categories and settings) and transactional data (orders) using the APIs provided by Engage. This is optional but enables additional features on the platform.

This guide will walk you through installing and setting up Engage. A basic installation is typically completed within 30-45 minutes.

Before you begin

To follow this tutorial you need to have an account with us, and your Engage API key. If you haven't already, complete the following steps before you begin.

Setup the source

To get running with Engage, you will need to activate the flow of data. Below are the listed sources to be considered.

Install the tracker

Provide product data

Provide order data

Unless you're using one of the platform plugins we've made available for the major e-commerce platforms, you need to send order data to Engage using the Order History API.

Add a destination

You'll need the measurement id from Google Analytics. Log into Google Analytics 4, and go to your data sources to find your measurement id (starting with "G-").

Add the destination:

1. Go to Data Platform > Integrations

2. Select the All destinations tab

3. Click the Google Analytics (GA4 & UA) source

4. Provide your measurement id in the GTAG ID field

5. Leave everything else as is for this basic setup

That's it! You are setup and data is flowing to Engage, and on to the destination you've setup. Now you can explore the features of Engage, and additional destinations to use.

The Facebook Marketing API lets Engage communicate and send data to Facebook (Meta). Use it to send custom audiences that are frequently updated to be as efficient and useful as possible.

The Marketing API allows you to build target Custom Audiences from customer, or visitor, information collected by Engage. This has become increasingly important as third party data collection has been, and will continue to be, heavily restricted across most browsers.

Use your own data to improve your marketing and target the correct audience with the right message. Engage keeps your audiences up to date to enable marketers to serve more relevant ads. For example, you may want to target customers that recently made a purchase with one specific ad, and then with a different one when that customer has re-visited your store. You can build out audiences that follows your customer journey and serve ads to them based on where in the journey they currently resides. And when they perform an action Engage will automatically move them to another audience.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Facebook Marketing API

Requirements

Active sources

This destination requires one of the following sources to be active

Facebook Ad Account ID

1. Log into your Facebook (Meta) Ads Manager account

2. Head to the dashboard where you will find the account id

Start using the Marketing API

When the Facebook Marketing API destination is enabled in Engage, the first thing to do is to create an Audience (based on visitors) or a segment (based on customers) in Engage. Follow the guide below to get started with dynamic audiences using the Marketing API.

This guide will walk you through installing and setting up Engage using a specific platform such as Shopify or Woocommerce. This is the fastest way to get started with Engage, the installation is typically completed within 15-30 minutes.

Before you begin

To follow this tutorial you need to have an account with us, and your Engage API key. If you haven't already, complete the following steps before you begin.

1. Create an Engage account

2. Log in and find your API key at the top of the dashboard

Setup recommended sources

To run the recommended setup on Engage, you need the following three data sources:

1. Event data

2. Product data

3. Order data

Luckily, all these are included in platform plugins provided by Engage. Select your platform below.

Add a destination

It's time to setup your first destination! In this tutorial we will walk you through setting up a basic Google Analytics 4 destination. You can read more about the destination here, but this tutorial have you covered on the basics below.

You'll need the measurement id from Google Analytics. Log into Google Analytics 4, and go to your data sources to find your measurement id (starting with "G-").

Add the destination:

1. Go to Data Platform > Integrations

2. Select the All destinations tab

3. Click the Google Analytics (GA4 & UA) source

4. Provide your measurement id in the GTAG ID field

5. Leave everything else as is for this basic setup

That's it! You are setup and data is flowing to Engage, and on to the destination you've setup. Now you can explore the features of Engage, and additional destinations to use.

Overview

The Engage platform destinations are third party applications and databases that receive data from Engage. Some destinations receive data using live streams directly from our core tracker, while other destinations receive batch data sent on a set interval from Engage.

Live stream destinations

Live stream destinations are generally third party applications that consume event data such as conversions, signups or other actions taken on your website. Setup your Engage tracking once, and send the data to all your third party apps consuming event data using our destinations.

The following live stream destinations are currently available:

Batch data destinations BETA

Batch data destinations are storage destinations like databases or blob storage. These destinations receive data on a scheduled interval and can include enriched data from Engage machine learning features, such as customer traits and characteristics. Use these destinations to setup your own data warehouse from which you can then connect BI and analytics tools to further explore your data.

The following batch data destinations are currently available (contact us to use them):

• Facebook Marketing API

• Google Analytics 4 - Audiences

• Amazon S3 BETA

• AWS Redshift PREVIEW

• AWS PostgreSQL PREVIEW

• Azure SQL - Synapse PREVIEW

• Google BigQuery BETA

• Snowflake PREVIEW

The Facebook Conversion API is used by Engage to send server side events and conversions to Facebook (Meta).

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Facebook Conversion API

4. Select the events to be sent

5. Optionally, override the default currency and update the events and hit save

Requirements

Active sources

This destination requires one of the following sources to be active

Facebook Pixel ID

2. Navigate to Events Manager

3. Here you'll find your Pixel ID

4. If you don't have a Pixel ID you may create it

Access token

2. Navigate to Events Manager

3. Here you'll find your Pixel ID

4. Click on it and select the settings tab

5. Scroll to the Conversion API section

6. Click Generate access token and follow the instructions

The Google Analytics 4 Server Side integration lets Engage send data server side to Google Analytics 4.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the GA4 Server Side

Requirements

Active sources

This destination requires one of the following sources to be active

Measurement ID

1. Log into your Google Analytics account

2. Go to Admin > Data Streams and click on the stream

3. You'll find your Measurement id in top right corner (G-xxxxxxxxxx)

API Secret

1. Log into your Google Analytics account

2. Go to Admin > Data Streams and click on the stream

3. Scroll down and click on Measurement Protocol API Secrets

4. Click Create in the top right corner to create your secret

5. Set any nickname you like and click Create

The Google Ads API lets Engage communicate and send data to Google. Use it to send custom segments as Customer Match lists that are updated in near realtime to be as efficient and useful as possible.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Google Ads API

Requirements

Active sources

This destination requires one of the following sources to be active

Customer ID

1. Log into your Google Ads account

2. You'll find your customer id in top right corner (xxx-xxx-xxxx)

Use Customer.io to send targeted emails, push notifications, and SMS to lower churn, create stronger relationships, and drive subscriptions. The Customer.io integration makes it easy to connect to Customer.io and get started with their services.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select Customer.io

3. Set your Site ID and select the events to be included

Requirements

Active sources

This destination requires one of the following sources to be active

Credentials

Mapped events

The Google Enhanced Conversions use the Google Ads API to send additional data to Google for conversion events. This is useful to improve the reporting in Google for conversions.

Activate Enhanced Conversions

You have to activate Enhanced Conversions in Google Ads for the conversion action you want to enhance.

1. Log into your Google Ads account

2. Go to Tools and Settings > Measurements > Conversions

3. Click on the conversion action you want to use and scroll down to Enhanced Conversions

4. Click the Turn on Enhanced Conversions, then select API and click Next > Save

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select Enhanced Conversion

3. Select the conversion event you want to enhance (We recommend not changing this)

Requirements

Active sources

This destination requires one of the following sources to be active

Google Ads Account ID

1. Log into your Google Ads account

2. You'll find your id in top right corner (xxx-xxx-xxxx)

Conversion Action ID

1. Log into your Google Ads account

2. Go to Tools and Settings > Measurements > Conversions

3. Click on the conversion action you want to use and scroll down to Enhanced Conversions

4. In the browser URL, find &ctId= and copy the value between ctId= and the next &

5. This is your Conversion action id (ctId=123456789&)

The GTAG integration works with GA4 (Google Analytics 4) out of the box, and with UA as long as the corresponding events are defined in your Universal Analytics setup. The integration activates the site tag client side, which means it sends the events to google analytics directly from the browser. Much like setting up a Google Analytics tracker yourself, but with predefined events mainly for e-commerce.

Add this destination

1. Log into your engage account

2. Go to Data Platform > Integrations and select the Google Analytics (GA4 & UA)

3. Set the GTAG ID and select the events to be included

   1. GTAG ID (measurement ID) for Google Analytics 4 (G-XXXXXXXXXX)

   2. GTAG ID (tracking ID) for Universal Analytics (UA-XXXXXXX-X)

4. Track Google Ads conversions by adding a Conversion ID and Conversion Label.

   2. Make sure to include AW- in the Conversation ID

Mapped events

The following events are mapped out-of-the-box for you when you activate the Google Global Site Tag integration. All of these events will be available in Google Analytics, and all data in Google Analytics can be used for dynamic ads and remarketing in Google Ads.

Requirements

Active sources

This destination requires one of the following sources to be active

Get your Measurement ID

1. Log into your Google Analytics account

2. Go to Admin > Data Streams and click on the stream

3. You'll find your Measurement id in top right corner (G-xxxxxxxxxx)

Get your Conversion ID

Follow these steps to get your conversion ID. If you don't have any setup yet, create a new one in step 3.

1. In your Google Ads account, click Goals in the menu.

2. Select Summary, which opens to the Conversion Actions table.

3. Select the name of the conversion that you want to use from the Conversion action column (You cannot use goals that have Google Analytics 4 as source). Or create a new Conversion action.

4. Expand the tab for Tag setup to view the tag details.

5. Select Use Google Tag Manager.

6. Scroll to the code snippet section and look for the Conversion ID.

7. Get the Conversion ID.

Get your Conversion Label

Continue from the instrucitons above.

1. On the same page as you found your Conversion ID, just below you will find your Conversion Label.

2. Get the Conversion Label.

Test implementation of GA4 or UA

2. Add a domain
3. Browse the store and make sure to perform all the action from which you expect to receive an event.

4. Evaluate the result by checking all the events that has been collected

Improve your ads performance with the TikTok Pixel integration. The TikTok Pixel optimizes your TikTok Ads with event and conversion tracking.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the TikTok Pixel

3. Set your TikTok Pixel ID and select the events to be included

Mapped events

The following events are mapped out-of-the-box for you when you activate the TikTok Pixel integration. These cover all the standard functionality of the Pixel.

Note that page views are automatically tracked by the TikTok Pixel.

Requirements

Active sources

This destination requires one of the following sources to be active

TikTok Pixel ID

Log into TikTok and create a new pixel. Select Developer mode.

Click through all steps until you get the to the code snippet, then find the Pixel ID here.

The Google Analytics 4 integration lets Engage communicate and send data to Google Analytics. Use it to tag users with custom segments from Engage that can be used to create audiences for improved marketing.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Google Analytics 4 - Send audience data

Requirements

Active sources

This destination requires one of the following sources to be active

Measurement ID

1. Log into your Google Analytics account

2. Go to Admin > Data Streams and click on the stream

3. You'll find your Measurement id in top right corner (G-xxxxxxxxxx)

API Secret

1. Log into your Google Analytics account

2. Go to Admin > Data Streams and click on the stream

3. Scroll down and click on Measurement Protocol API Secrets

4. Click Create in the top right corner to create your secret

5. Set any nickname you like and click Create

Engage uses source integrations to collect and ingest data to the platform. You generally need at least one active source to use Engage, but most customers end up using multiple sources to fulfil their intended use cases. When you first sign in to Engage you will be required to setup your first source integration.

Available sources

Platform plugins

We have built out plugins for a number of platforms to effortlessly integrate your source to Engage. These plugins combine API connections for data extraction with implementation of the Engage javascript tracker for realtime event tracking. All you need to get started.

Javascript and APIs

Our javascript tracker is the most comprehensive event tracker to capture granular data from realtime event. Use it standalone or together with one of our APIs for additional data.

Improve your ads performance with the LinkedIn Pixel integration. The LinkedIn Pixel optimizes your LinkedIn Ads with event and conversion tracking, and enables remarketing.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the LinkedIn Pixel

3. Set your LinkedIn Pixel ID and select the events to be included

Requirements

Active sources

This destination requires one of the following sources to be active

LinkedIn Pixel ID

1. Log into your LinkedIn Campaign Manager account

2. Open the Account Assets dropdown and select Insight Tag

3. Within your JS tag you'll find your Pixel ID

4. Look for the linkedin_data_partner_id variable

Track events and send conversion data to Klaviyo using this integration. No additional setup is needed to integrate Klaviyo with your store.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Klaviyo

Requirements

Active sources

This destination requires one of the following sources to be active

Klaviyo ID

1. Log into your Klaviyo account

2. Navigate to Account > Settings > API Keys and note your Public API Key.

Track events and send conversion data to Klaviyo server side using this integration. No additional setup is needed to integrate Klaviyo with your store.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Klaviyo Server Side

Requirements

Active sources

This destination requires one of the following sources to be active

Klaviyo ID

1. Log into your Klaviyo account

2. Navigate to Account > Settings > API Keys and note your Public API Key.

Improve your ads performance with the Facebook Pixel integration. The Facebook Pixel optimizes your Facebook Ads with event and conversion tracking, and enables the use of dynamic ads and remarketing.

Add this destination

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Facebook Pixel

4. Save

Requirements

Active sources

This destination requires one of the following sources to be active

Facebook Pixel ID

• Navigate to Events Manager

• Here you'll find your Pixel ID

• If you don't have a Pixel ID you may create it

Events

Mapped events

The following events are mapped out-of-the-box for you when you activate the Facebook Pixel integration. These cover all the standard functionality of the Pixel.

Adding events

You may send additional or custom events to the Facebook Pixel by adding the event in the Facebook Pixel integration setting. Any standard or custom event can be added to the integration but make sure to adhere to Facebooks Personally Identifiable Information (PII) guidelines. The following information should not be sent to Facebook, and we automatically remove them from the standard events.

• Email

• First name

• Last name

• Gender

• City

• Country

• Phone

• State

• Zip code

• Birthday

Dynamic Product Ads

Our Facebook Pixel integration is built to support Facebooks Dynamic Product Ads. These are ads that typically performs much better than regular ads since they have the ability to display the exact product the customer was looking at, but did not buy yet. Remarket the products of interest to a potential customer across the entire reach of Facebook.

Get started with dynamic ads

To start using dynamic ads you need to provide a product catalog to Facebook, and design a dynamic ads template that Facebook can use to display your products. We have already taken care of setting up the Facebook Pixel for dynamic ads, so there is no further steps to complete for the tracking.

Steps to complete:

1. Set up the required tracking - Already done

2. Provide a Facebook Product Catalog

3. Design the Ads template to use

• Product Seen

• Product Viewed

• Added to Cart

• Order Completed

Troubleshooting

Are the events received by Facebook?

Engage will start to send events 45 minutes after you activate the Facebook Pixel destination. After that you can log into the Facebook event manager to see events as they are registered by Facebook.

This is the core component of engage used to collect information about your visitors and customers, and the actions they take on your website. Collect clean and structured data for use in any integration or service on engage. This source also enables on page product recommendations in your store.

Add this source

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Javascript tracker

Next step

How it works

Engage connects to your store using a plugin to implement an event tracker and to open an API connection to your store. The API connection is used to retrieve store data to the Engage platform and the tracker send us event based data from the actions taken in your store.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

In Magento 2, the recommendations are served backend using the plugin. If the recommendation call fails, for any reason, the recommendations fails silently not showing any error on the page. This is important to ensure a good customer experience.

Sometimes it is handy to serve recommendations using javascript instead. Engage let you serve recommendations via the tracker script on any page that includes the tracker script.

Getting started

Installing

Engage are installed using the plugin for Magento 2 stores. Simply install the latest plugin from us and follow the on screen instructions. Basically, you create an account with us and allow the plugin to connect the store to us.

Next step

Uninstalling

Deactivate, or uninstall the plugin to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan.

How it works

Engage connects to your store using a plugin to implement an event tracker and to open an API connection to your store. The API connection is used to retrieve store data to the Engage platform and the tracker send us event based data from the actions taken in your store.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

In Magento 1, the recommendations are served backend using the plugin. If the recommendation call fails, for any reason, the recommendations fails silently not showing any error on the page. This is important to ensure a good customer experience.

Sometimes it is handy to serve recommendations using javascript instead. Engage let you serve recommendations via the tracker script on any page that includes the tracker script.

Getting started

Installing

Engage are installed using the plugin for Magento 1 stores. Simply install the latest plugin from us and follow the on screen instructions. Basically, you create an account with us and allow the plugin to connect the store to us.

Next step

Uninstalling

Deactivate, or uninstall the plugin to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan.

The Google Product Feed source introduce an alternative way to provide product data to Engage. This source can be used standalone to source product data to Engage, or in combination with other sources as a complement.

Add this source

1. Log into your Engage account

2. Go to Data Platform > Integrations and select the Google Product Feed

3. Provide the full URL to your product file

Next step

Included events

The following events are defined out-of-the-box for you when you use the AbiCart plugin. These cover all the standard functionality required.

Adding custom events

You may track additional or custom events in your store by adding the corresponding zlt.track(); javascript function on your website.

This is our official AbiCart plugin to fetch data from your store. This plugin takes care of all setup needed to get data flowing from your store to Engage. This includes batch data ingestion as well as advanced javascript tracking. Continue reading to get started with the AbiCart plugin.

How it works

Engage connects to your store using the standard Abicart API to retrieve current and historical data to the Engage platform. In addition an event tracker is required to gather actions taken by the users in your store. These events are used in analytics and product recommendations to improve the insights and personalization capabilities.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

Abicart is a Single Page Application (SPA) platform, which requires the implementation of the tracker to be done manually. We have prebuilt a template to capture all the required events out-of-the-box. And often there is no additional work required to get started. Adding custom events will however require manual procedures.

Recommendations are delivered using javascript and are fully customizable.

Getting started

Installing

1. Log into your Engage account

2. Go to Data platform > Integrations and select the AbiCart plugin

5. Activate the AbiCart Tracker add-on.

Uninstalling

Deactivate the source in Engage to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan. Finally remove the tracker script from your site.

Required parameters and scripts

API Key

1. Log into your store admin area

2. Navigate to Settings > Apps > API keys and click Edit

3. Click Add and setup your API key

4. Make sure to check the Activate checkbox before saving

Shop ID

1. Log into your store admin area

2. Find your Shop ID in the top left corner

API Endpoint

The API Endpoint is simply your store URL with the below add-on appended:

/backend/jsonrpc/v1/

Tracker add-on

To automate tracking of e-commerce events, the tracker need an extension for AbiCArt. Add the below code snippet as a tracker add-on.

// Tracker add-on for AbiCArt
var zl_addon={zl_eg:function(t){return[t=document.querySelectorAll(t),t.length]},zl_dc:function(t){return 0<t},zl_attr:function(t,n,e){return t.querySelector(n).getAttribute(e)},zl_src:function(t,n){return t.querySelector(n).src},zl_val:function(t,n){n=t.querySelector(n);try{return parseInt(n.value)}catch(t){return 0}},init:function(){"complete"===document.readyState&&setTimeout(function(){zl_addon.zl_initiate()},2e3)},itext:function(t,n){return t.querySelector(n).innerText},itextint:function(t,n){return parseInt(t.querySelector(n).innerText.match(/\d/g).join(""))},none:function(t,n){return""},url:function(t,n){return t.querySelector(n).href},timer:function(t){setTimeout(t,5)},cus1:function(t){return document.querySelectorAll("body[class*=article-]")[0].className.match(/(article-\d+)/)[0].replace("article-","")},cus2:function(t,n){return t.querySelector(n).className.split(" ")[1].split("-")[5]},get_data:function(t,n,e){return zl_addon.dict_loop(t,n,e)},bind_button:function(e,d,t,o){t.forEach(t=>{t.addEventListener("click",function(){var n=zl_addon.get_data(e,d,t);"Removed From Cart"==o?setTimeout(function(){document.querySelectorAll(zl_addon.zl_mm.mmrm).forEach(t=>{t.addEventListener("click",function(){zl_addon.timer(zlt.track(o,n))})})},500):(zl_addon.timer(zlt.track(o,n)),setTimeout(zl_addon.zl_crte,3e3))})})}};history.pushState=(n=>function(){var t=n.apply(this,arguments);return window.dispatchEvent(new Event("pushstate")),window.dispatchEvent(new Event("locationchange")),t})(history.pushState),history.replaceState=(n=>function(){var t=n.apply(this,arguments);return window.dispatchEvent(new Event("replacestate")),window.dispatchEvent(new Event("locationchange")),t})(history.replaceState),window.addEventListener("popstate",()=>{window.dispatchEvent(new Event("locationchange"))}),zl_addon.zl_tspv=function(t){t=zl_addon.get_data(zl_addon.zl_mm.swci,zl_addon.zl_spm,t),zl_addon.timer(zlt.track("Product Viewed",t))},zl_addon.zl_spel=function(){var t=zl_addon.zl_eg(zl_addon.zl_mm.satc)[0];zl_addon.bind_button(zl_addon.zl_mm.swci,zl_addon.zl_spm,t,"Added To Cart")},zl_addon.zl_tcpv=function(){},zl_addon.zl_cael=function(){var t=zl_addon.zl_eg(zl_addon.zl_mm.catc)[0];zl_addon.bind_button(zl_addon.zl_mm.cws,zl_addon.zl_cpm,t,"Added To Cart")},zl_addon.zl_gsct=function(){console.log("<--M--O--N--Y--\x3e")},zl_addon.zl_crte=function(){var t=zl_addon.zl_eg(zl_addon.zl_mm.crmq)[0];zl_addon.bind_button(zl_addon.zl_mm.ctpw,zl_addon.zl_ctpm,t,"Removed From Cart")},zl_addon.or_cd=function(){try{var t=parseInt(location.pathname.split("/")[2]);!isNaN(t)&&0<document.querySelectorAll(".tws-checkout-success").length&&zl_addon.timer(zlt.track("Order Completed",{order_id:t}))}catch(t){}},zl_addon.zl_helper={innerText:zl_addon.itext,innerTextInt:zl_addon.itextint,custom1:zl_addon.cus1,val:zl_addon.zl_val,"":zl_addon.none,href:zl_addon.url,custom2:zl_addon.cus2,src:zl_addon.zl_src,none:zl_addon.none},zl_addon.zl_mm={cws:"",catc:"",satc:".buy-button-wrapper",srfc:"",ctpw:".tws-opc-cart--item",crmq:".tws-opc-cart--item-remove-action",swci:".bountiful--article-top",cpid:".opc-checkout",cinit:".tws-mini-cart",mmrm:".tws-checkout-success",cinitbool:!1},zl_addon.zl_cpm={name:{n:".tws-util-heading--heading",t:"innerText"},product_id:{n:".tws-article-list--grid-item-link",t:"custom2"},price:{n:".tws-api--price-current",t:"innerTextInt"},image_url:{n:".tws-img--container img",t:"src"}},zl_addon.zl_spm={name:{n:".tws-article-name",t:"innerText"},product_id:{n:"",t:"custom1"},price:{n:".tws-api--price-current",t:"innerTextInt"},image_url:{n:".tws-img--container img",t:"src"},quantity:{n:".input-group input[name='quantity']",t:"val"}},zl_addon.zl_ctpm={name:{n:".tws-opc-cart--item-info-name",t:"innerText"},price:{n:".twsPriceCurrent",t:"innerTextInt"},quantity:{n:".tws-opc-cart--item-info-quantity input",t:"val"},product_id:{n:"",t:"none"},product_url:{n:".tws-opc-cart--item-info-name a",t:"href"},image_url:{n:".tws-img--container img",t:"src"}},zl_addon.dict_loop=function(t,n,e){var d=e.closest(t);const o={};for(const a in n){var l=n[a],c=l.n;const r=zl_addon.zl_helper[l.t];o[a]=r(d,c)}return o.currency="SEK",o},zl_addon.zl_initiate=function(){var t=zl_addon.zl_eg(zl_addon.zl_mm.swci),n=zl_addon.zl_eg(zl_addon.zl_mm.ctpw),e=(zl_addon.zl_eg(zl_addon.zl_mm.cpid),zl_addon.zl_eg("#zlt_product_01")),d=zl_addon.zl_eg("#zlt_product_02");zl_addon.zl_dc(t[1])&&(zl_addon.zl_tspv(t[0][0]),zl_addon.zl_spel()),zl_addon.zl_dc(n[1])&&(zl_addon.zl_crte(),zl_addon.zl_gsct()),zl_addon.or_cd();try{zl_addon.zl_dc(e[1])&&zlt.rec(zl_addon.cus1(""),"zlt_01","",{currency:"SEK",decimals:0}),zl_addon.zl_dc(d[1])&&zlt.rec(zl_addon.cus1(""),"zlt_02","",{currency:"SEK",decimals:0})}catch(t){}},zl_addon.init(),document.addEventListener("readystatechange",t=>{zl_addon.init()}),window.addEventListener("locationchange",function(){zl_addon.init()});

Next step

This is our official Prestashop module that connects Engage with your store. This module takes care of all setup needed to use Engage with Prestashop.

Getting started

How it works

Engage connects to your store using a plugin to implement an event tracker and to open an API connection to your store. The API connection is used to retrieve store data to the Engage platform and the tracker send us event based data from the actions taken in your store.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

In Prestashop, the recommendations are served backend using the plugin. If the recommendation call fails, for any reason, the recommendations fails silently not showing any error on the page. This is important to ensure a good customer experience.

Sometimes it is handy to serve recommendations using javascript instead. Engage let you serve recommendations via the tracker script on any page that includes the tracker script.

Installing

After the installation you will be asked, form within the module, to provide an API key.

Next step

Uninstalling

Deactivate, or uninstall the plugin to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan.

Download the module

How it works

Engage connects to your store using the standard Wikingruppen API to retrieve current and historical data to the Engage platform. In addition an event tracker is required to gather actions taken by the users in your store. These events are used in analytics and product recommendations to improve the insights and personalization capabilities.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

Wikingruppen is a Single Page Application (SPA) platform, which requires the implementation of the tracker to be done manually. We have prebuilt a template to capture all the required events out-of-the-box. And often there is no additional work required to get started. Adding custom events will however require manual procedures.

Recommendations are delivered using javascript and are fully customizable.

Getting started

Installing

First step is to create an account with us. Then select Wikingruppen as the first source to use and follow the on screen instructions.

Engage is installed by providing an API key for us to use to connect to your store. Then you place the tracker code in the header section of Wikingruppen.

Next step

Uninstalling

Deactivate the source in Engage to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan. Finally remove the tracker script from your site.

This is our official Shopify plugin to fetch data from your store. This plugin takes care of all setup needed to get data flowing from your store to engage. This includes batch data ingestion as well as advanced javascript tracking.

How it works

Engage connects to your store using a plugin to implement an event tracker and to open an API connection to your store. The API connection is used to retrieve store data to the Engage platform and the tracker send us event based data from the actions taken in your store.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

In Shopify, the recommendations are served backend using the plugin. If the recommendation call fails, for any reason, the recommendations fails silently not showing any error on the page. This is important to ensure a good customer experience.

Sometimes it is handy to serve recommendations using javascript instead. Engage let you serve recommendations via the tracker script on any page that includes the tracker script.

Getting started

Installing

Engage are installed using the plugin for Shopify stores. Simply install the latest plugin from the marketplace and follow the on screen instructions. Basically, you create an account with us and allow the plugin to connect the store to us.

2. Copy your API key from the Engage platform.

1. Paste the API key in the Shopify APP

Next step

Uninstalling

Deactivate, or uninstall the plugin to stop using our services.

Included events

The following events are defined out-of-the-box for you when you activate the Prestashop module. These cover all the standard functionality required.

Adding events

You may track additional or custom events in your store by adding the corresponding zlt.track(); javascript function on your website.

/* Example of a custom event */
zlt.track('My Custom Event', {
    param_one: 'Some value',
    param_two: 123
});

Included events

The following events are defined out-of-the-box for you when you activate the Shopify plugin.

Custom events

You may track additional or custom events in your store by adding the corresponding zlt.track(); javascript function on your website.

/* Example of a custom event */
zlt.track('My Custom Event', {
    param_one: 'Some value',
    param_two: 123
})

Checkout Started

zlt.track('Checkout Started', {
  cart_id: '',
  checkout_id: '',
  order_id: '',
  total: 17.50,
  subtotal: 12.50,
  revenue: 15.00,
  shipping: 2,
  tax: 3,
  discount: 2.5,
  coupon: '',
  currency: 'USD',
  products: [
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Payment Info Added

zlt.track('Payment Info Added', {
  checkout_id: '',
  order_id: '',
  payment_method: ''
});

Added To Cart

zlt.track('Added To Cart', {
  cart_id: '',
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: ,
  currency: '',
  quantity: 1,
  coupon: '',
  on_sale: false,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Removed From Cart

zlt.track('Removed From Cart', {
  cart_id: '',
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: ,
  currency: '',
  quantity: 1,
  coupon: '',
  on_sale: false,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Cart Viewed

zlt.track('Cart Viewed', {
  cart_id: '',
  products: [
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Insufficient data

All functionality in engage requires data. In some cases it takes a while to gather the data needed to purposefully use a function. When that happens we display a notification to inform you that the data requirements are not yet met for the particular function.

What can you do?

Ensure the active data source is capturing the data required for the function. The javascript source is able to capture all required data for you, but it requires that you have defined the events needed, and it takes a while to gather enough data for some functions.

If you instead use the API, these may not supply the required data for the given function. In that case you can add the javascript source in addition to the APIs.

If you are using one of the plugins you already have both the APIs and the javascript source installed automatically, but you may need to add particular javascript events that aren't captured by the plugin by default.

Included events

The following events are defined out-of-the-box for you when you activate the Woocommerce plugin. These cover all the standard functionality required.

Adding events

You may track additional or custom events in your store by adding the corresponding zlt.track(); javascript function on your website.

/* Example of a custom event */
zlt.track('My Custom Event', {
    param_one: 'Some value',
    param_two: 123
});

Engage let you track and capture data on how your visitors engage with your videos. The selectors defined should be as close to the actual video in the DOM as possible. But when iframes are used it should be no deeper than the iframe.

// Add this to capture video events on Vimeo.

//Example 1 
function zubi_vimeo_events(){
  const zl_vimeo_elements = document.querySelectorAll("video")
  zlt.track_video_vimeo("",['play','pause','seeked','seeking','ended','error','bufferstart','bufferend','loaded','qualitychange' , 'fullscreenchange'] , zl_vimeo_elements )
}

//Example 2 
function zubi_vimeo_events(){
  const zl_vimeo_elements = document.querySelectorAll("#video_1")
  zlt.track_video_vimeo("",['play','pause'], zl_vimeo_elements)
} 

//Example 3
function zubi_vimeo_events(){  
const zl_vimeo_elements = document.querySelectorAll(".video_1")
  zlt.track_video_vimeo("",['play','pause','ended'], zl_vimeo_elements)
} 

// Use multiple selectors
function zubi_vimeo_events(){
  const zl_vimeo_elements = document.querySelectorAll(".video, iframe, #video , video");
  zlt.track_video_vimeo("",['play','pause','seeked','seeking','ended','error','bufferstart','bufferend','loaded','qualitychange' , 'fullscreenchange'] , zl_vimeo_elements )
}

// Add this to capture Youtube video events
zlt.track_video_yt =  { id : "ID OF YOUTUBE IFRAME" }

Vimeo Supported Video Events

-Event name , -Maps to

1. play - "Video Played"

2. pause - "Video Paused"

3. seeked - "Video Seeked"

4. seeking - "Video Seeking"

5. ended - "Video Ended"

6. error - "Video Error"

7. bufferstart - "Video Buffer Start"

8. bufferend - "Video Buffer End"

9. loaded - "Video Loaded"

10. qualitychange - "Video Quality Change"

11. fullscreenchange - "Video Fullscreen Change"

Most of the events include the total duration - played duration - percentage of video watched with each event

duration: 61.857
percent: 0.485
seconds: 30

Video Error includes these values

message: "#984220 does not meet minimum contrast ratio. We recommend using brighter colors. (You could try #d35e30 instead.) See WCAG 2.0 guidelines: http://www.w3.org/TR/WCAG/#visual-audio-contrast"
method: "setColor"
name: "ContrastError"

YouTube Supported Video Events

1. "Video Played"

2. "Video Paused"

3. "Video Ended"

4. "Video Buffering"

5. "Video Cued"

6. "Video Quality Changed"

7. "Video Loaded"

Even though the attached events can be controlled on Vimeo , The way YT is currently working we attach all the possible related events

Events on YT Will send back current video duration only

Error codes :

• 2 – The request contains an invalid parameter value. For example, this error occurs if you specify a video ID that does not have 11 characters, or if the video ID contains invalid characters, such as exclamation points or asterisks.

• 5 – The requested content cannot be played in an HTML5 player or another error related to the HTML5 player has occurred.

• 100 – The video requested was not found. This error occurs when a video has been removed (for any reason) or has been marked as private.

• 101 – The owner of the requested video does not allow it to be played in embedded players.

• 150 – This error is the same as 101. It's just a 101 error in disguise!

All event tracking is done using an async javascript code snippet that gathers the information and push it to our servers where it is stored for you. The tracker is built to never interfere with your sites performance or functionality. It will fail silently in the event something would go wrong and it will queue up messages when it's not able to send them right away.

Note on Data Privacy

Setup

The setup is pretty straight forward. To initialize the tracker, add the following code to your page header.

/* Initiate the tracker */
<script type="text/javascript">const TRACKER_KEY="[ADD YOUR TRACKER KEY]";window.zlt_queue||(window.zlt_queue=[]),window.zlt_queue2||(window.zlt_queue2=[]),window.zlt=function(){},window.zlt.rec=function(u,w){w={p:u,d:w};window.zlt_queue2.push(w)},zlt.track=function(u,w){var n={};n[u]=w,window.zlt_queue.push(n)};</script>
<script async src="https://assets.zubitracker.io/v1/tracker/track.js"></script>

Prepare for product recommendation

The following two events are required in order to run product recommendations.

Requirements

Active sources

This feature requires one of the following sources to be active

This is our official Woocommerce plugin to fetch data from your store. This plugin takes care of all setup needed to get data flowing from your store to engage. This includes batch data ingestion as well as advanced javascript tracking.

How it works

Engage connects to your store using a plugin to implement an event tracker and to open an API connection to your store. The API connection is used to retrieve store data to the Engage platform and the tracker send us event based data from the actions taken in your store.

In Engage, we process your data, clean it and make it ready for use. We then start to build the analytics datasets, the recommendation models, search index, etc. As we complete these tasks the data becomes available in our platform for you to use.

In WooCommerce, the recommendations are served backend using the plugin. You can use short codes to determine exactly where and what to display. If the recommendation call fails, for any reason, the recommendations short code fails silently not showing any error on the page. This is important to ensure a good customer experience.

Sometimes it is handy to serve recommendations using javascript instead. Engage let you serve recommendations via the tracker script on any page that includes the tracker script.

Getting Started

Installing

Engage are installed using the plugin for WooCommerce stores. Simply install the latest plugin from the marketplace and provide your Engage API key.

2. Copy your API key from the Engage platform.

1. Paste the API key in the WooCommerce Plugin

1. Follow the on screen instructions to authorize Engage to access your store.

Next step

Uninstalling

Deactivate, or uninstall the plugin to stop using our services. If you have a paid plan you wish to cancel you must do so on the Engage platform. Simply login and go to subscriptions to cancel your plan.

Product Reviewed

Order Completed

zlt.track('Order Completed', {
  email: '',
  billing_address_first_name: '',
  billing_address_last_name: '',
  billing_address_company: '',
  billing_address_zip: '',
  billing_address_phone: '',
  billing_address_address1: '',
  billing_address_address2: '',
  billing_address_city: '',
  billing_address_province: '',
  billing_address_province_code: '',
  billing_address_country: '',
  billing_address_country_code: '',
  shipping_address_first_name: '',
  shipping_address_last_name: '',
  shipping_address_company: '',
  shipping_address_zip: '',
  shipping_address_phone: '',
  shipping_address_address1: '',
  shipping_address_address2: '',
  shipping_address_city: '',
  shipping_address_province: '',
  shipping_address_province_code: '',
  shipping_address_country: '',
  shipping_address_country_code: '',
  order_id: '',
  checkout_id: '',
  payment_method: '',
  total: 17.50,
  subtotal: 12.50,
  revenue: 15.00,
  shipping: 2,
  tax: 3,
  discount: 2.5,
  coupons: [
    {
      coupon_id: '',
      amount: '',
      percentage: false
    }
  ],
  currency: 'USD',
  products: [
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ],
	created_at: '',
	updated_at: ''
});

Order Refunded

zlt.track('Order Refunded', {
  order_id: '',
  total: ,
  currency: 'USD',
  products: [
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Order Cancelled

zlt.track('Order Cancelled', {
  order_id: '',
  total: 30,
  subtotal: ,
  revenue: 25.00,
  shipping: 3,
  tax: 2,
  discount: 2.5,
  coupon: '',
  currency: 'USD',
  products: [
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      product_id: '',
      variant_id: '',
      sku: '',
      name: '',
      price: ,
      quantity: ,
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Promotion Viewed

zlt.track('Promotion Viewed', {
  promotion_id: '',
  creative: '',
  name: '',
  position: ''
});

Promotion Clicked

zlt.track('Promotion Clicked', {
  promotion_id: '',
  creative: '',
  name: '',
  position: ''
});

Product Clicked

zlt.track('Product Clicked', {
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: 18.99,
  currency: 'eur',
  quantity: 1,
  on_sale: false,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Product Viewed

This event should fire when the product page of a specific product is viewed.

zlt.track('Product Viewed', {
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: ,
  quantity: 1,
  currency: 'eur',
  on_sale: false,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Product Seen

Register this event when a product is visibly displayed for the visitor on pages that isn't the particular products designated product page. E.g. in search results, start page or category listings.

zlt.track('Product Seen', {
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: ,
  currency: 'eur',
  on_sale: false,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Category Viewed

zlt.track('Category Viewed', {
  category_id: '',
  category: '',
  products: [
    {
      row: 1,
      column: 1,
      product_id: '',
      sku: '',
      name: '',
      price: ,
      currency: '',
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      row: 1,
      column: 2,
      product_id: '',
      sku: '',
      name: '',
      price: ,
      currency: '',
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Products Searched

zlt.track('Products Searched', {
  query: 'blue roses',
  products: [
    {
      row: 1,
      column: 1,
      product_id: '',
      sku: '',
      name: '',
      price: ,
      currency: '',
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    },
    {
      row: 1,
      column: 2,
      product_id: '',
      sku: '',
      name: '',
      price: ,
      currency: '',
      category: '',
      product_type: '',
      on_sale: false,
      url: 'https://www.example.com/product/path',
      image_url: 'https:///www.example.com/product/path.jpg'
    }
  ]
});

Visitors are anonymously tracked using session ids throughout your site. But when visitors identify themselves at login, signup or checkout, you may pair a session id with a user to identify the entire chain of events one user has carried out over time.

/* Identify a user */
zlt.track('user', {
    'user_id':'[email protected]',
    'email':'[email protected]',
    'first_name':'John',
    'last_name':'Doe'
});

The user_id should be a unique identifier. It can be an email address or any other identifier of choice.

Engage Identities let you build enhanced and unified user profiles based on your customer or website visitor data. An Engage Identity represents a single view of your user and holds traits based on events, actions, customer data or custom data. Build and activate powerful custom audiences across your marketing tools.

How it works

Identities are based on user data tracked and collected from your site using the Engage Tracker. The profiles are then enhanced with customer data and other event based data as the user interacts with your business. Identities are also merged when identified across multiple channels, sessions or devices to provide a single view of the user base.

Identity resolution

Resolve and unify your visitor identities regardless of when, or what channel they used to visit your site. Avoid maintaining multiple records for the same user and connect external IDs used on various platforms to one Engage Identity.

Customer data

Identities use customer data such as location, preferred currency and order data to compute customer traits that can be used to segment a group of customers.

Visitor data

Visitor data is any event based data gathered from the visitors actions on your site. Data such as what pages/products was viewed or added to cart, actions taken on site such as sign up for newsletter, request for quotation, etc. All events are later added to the user identity for use in further analysis and segmentation.

Smart traits

Engage derives useful traits such as customer life cycles, predicted gender and lifetime value to enable narrow, specific user segmentation for use in highly personalized marketing.

Using your Identities

Build powerful user lists

Create lists of users that match conditions or criteria defined by you. Then activate your user list within Engage or push them to marketing tools for personalized advertisement. User lists can be built using events, smart traits and more.

Visitor audiences

Engage audiences are lists of site visitors that haven't necessarily become customers yet. Often these visitors are anonymous or identified via external ids, login, newsletter signup or other forms where the user fill out an email address or other identifier. Audiences are defined mainly based on actions taken on the site, such as users who added a product to cart but did not checkout or a user browsed pricing but did not sign up for a subscription. A lot more filters and conditions can be defined in the audience builder.

Customer segments

Customer segments allow you to create customer cohorts based on various events and characteristics of the customers. Segments are then kept up-to-date automatically by Engage and you may use them in analytics and reports on Engage or sync them to your marketing tools.

Sync with marketing tools

Personalize the store experience

Customers expects a personalized experience when visiting e-commerce stores today. Identities enables hyper-personalized solutions to meet these expectations from the customer.

Product recommendations

Recently viewed products

Help your visitors keep track and easily find what products they've already browsed using recently viewed products. Or greet your returning visitors with a block helping them to pick up where they left off, or to re-order the products they bought last time.

Customer segmentation is the process of dividing a customer base into smaller groups based on shared characteristics, such as demographics, interests, behaviors, or needs. The goal of customer segmentation is to better understand and target specific groups of customers, and to tailor marketing efforts and products to these groups in a more personalized and effective way.

Granular segments

Ad networks often let you create segments based on demography, geolocation and interests. Engage lets you build segments based on granular events and visitor activities, such as products viewed or added to cart, videos played or forms submitted. Tailor the segment for which you like to run marketing campaigns and keep them updated during the entire campaign.

Segment synchronization

Keep your segments in sync and optimize your ROAS (Return On Ad Spend) using up to date segments in your campaigns. Engage let you define very specific segments for narrow targeting, but this often means that a customer should be in that segment only from the moment one event is taken and only up to the moment the next event action is performed. Hence, we need to be able to update segments automatically as new events occurs.

Similar to above, Engage also enables suppression of individual customers as actions are performed. Typical examples are to stop showing advertisement to a customer that performed a purchase, or to stop tracking a user that declined the cookie consent popup. All of which are made possible with our automated segment synchronization feature.

Improved target audience matching

Due to Apple's iOS 14 update, GDPR, CCPA and other privacy regulations, platforms like Meta (Facebook) and Google are changing how they collect and store data. This has a negative impact on the audience match rates on those platforms. In short, this means that for example the data collected from the Pixel is now less likely to be usable to match the user to a Facebook user, which in turn makes it harder to target that user.

Using first party data (collected via Engage) we can send segments to the ads networks with more, better and more reliable data for the network to use to match it to its users. The result is better audience matching, more targeted campaigns and higher ROAS.

Requirements

Active sources

This feature requires one of the following sources to be active

Added To Wishlist

zlt.track('Added To Wishlist', {
  wishlist_id: '',
  wishlist_name: '',
  product_id: '',
  sku: '',
  category: '',
  product_type: '',
  name: '',
  brand: '',
  variant: '',
  variant_id: '',
  price: 18.99,
  currency: '',
  quantity: 1,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});