Using the Data Layer with preezie
- Graham Ralls (Unlicensed)
What the data layer does
The data layer is a standardised way to pass information about your user’s activity between different web applications. It uses a JavaScript object in the browser to expose details about what your users are doing in realtime, meaning different software applications can listen and react to data across different sources.
To use this data typically a Tag Manager (e.g. Google Tag Manager or Tealium) is used to pass data variables between different sources, for example preezie journeys can pass information directly into your Google Analytics.
When switched on, preezie passes journey activity data in realtime to your website’s data layer. For example,
journey answer text, e.g. Budget = “$200-$300”
product recommendations, e.g. Most ranked #1 = “Nike Air Jordans”
journey triggers, e.g. CTA = 80% of new user completions
If you haven’t already get in touch with your Customer Success representative or email support@preezie.com to turn on the data layer for your account!
What it can be used for
All of the data created by the preezie journey can be shared in realtime with any of your other relevant software applications. For example,
Send your journeys answers directly into Google Analytics, e.g. what is the AOV of users looking for Organic products?
Send preezie answers to your ad retargeting platform, e.g. create an audience based on all users who are buying a gift for their partner
Analyse which preezie trigger captures the most new user email addresses, e.g. report by trigger count of new user email submits
Tag managers supported
preezie currently supports the below tag managers:
Tag Manager Method | Event naming | Details |
|---|---|---|
Google Tag Manager |
| Available as Data Layer Variables in GTM |
Tealium OR custom JavaScript | Custom via: | |
Adobe Tag Manager (using Google Extension) |
(using |
preezie data available
When the data layer is activated for your account you will start firing data events in realtime from all preezie journeys. Here is a full list of the events and data available.
Event name | When it’s fired | Event details |
|---|---|---|
preezie.load | upon journey load | |
preezie.click | upon each answer click | |
preezie.completed | upon finishing the journey | |
preezie.results | upon seeing product results | |
preezie.resultclick | upon clicking a product result | |
preezie.email | upon submitting an email | |
preezie.addtocart | upon clicking add to cart button | |
preezie.addalltocart | upon clicking add all to cart button |
Event details
preezie load
event name: preezie.load
This event is fired whenever the preezie widget is loaded. It will fire each time the widget is viewed, and for each different method, e.g. embedded, CTA etc.
Data variable | example | Description |
|---|---|---|
preezie.trigger |
| how the preezie journey was triggered, possible values are |
preezie.page |
| the page url the journey was triggered on |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow / preeze.selector |
| the name of the journey loaded |
preezie.workflowId / preezie.selectorId |
| the id of the journey loaded |
preezie click
event name: preezie.click
This event is fired when each answer is clicked through in a preezie journey. It will fire each time the answer is clicked, even if they go back to change their answer.
Data variable | example | Description |
|---|---|---|
preezie.trigger |
| how the preezie journey was triggered |
preezie.answer |
| the question number and answer to the question |
preezie.duration |
| how many seconds the user took to answer the question |
preezie.question |
| the question number and the full question text |
preezie.ref |
| the question short name |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow / preeze.selector |
| the name of the journey loaded |
preezie.workflowId / preezie.selectorId |
| the id of the journey loaded |
preezie completed
event name: preezie.completed
Data variable | example | Description |
|---|---|---|
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey completed |
preezie.workflowId |
| the id of the journey completed |
preezie results
event name: preezie.results
Data variable | example | Description |
|---|---|---|
preezie.product (array) |
| the name of the array containing all product results. |
unique |
| the unique ID of the product, e.g. the SKU. This is mapped in Database > Product attributes |
name |
| the name of the product shown |
position |
| the product’s rank in the preezie results |
price |
| the price of the product |
+ any field attribute with Appears in Stats set to True in Admin > Database > Product attributes  |
| These will always be text string values. All field names are lowercase and use _ in place of spaces, e.g. dress_length |
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey completed |
preezie.workflowId |
| the id of the journey completed |
preezie.resultclick
event name: preezie.resultclick
Data variable | example | Description |
|---|---|---|
preezie.product (object) |
| the name of the object containing all product details that was clicked. |
unique |
| the unique ID of the product, e.g. the SKU. This is mapped in Database > Product attributes |
name |
| the name of the product shown |
position |
| the product’s rank in the preezie results |
price |
| the price of the product |
url |
| the url of the product clicked |
+ any field attribute with Appears in Stats set to True in Admin > Database > Product attributes |
| These will always be text string values. All field names are lowercase and use _ in place of spaces, e.g. dress_length |
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey completed |
preezie.workflowId |
| the id of the journey completed |
preezie.email
event name: preezie.email
Data variable | example | Description |
|---|---|---|
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey loaded |
preezie.workflowId |
| the id of the journey loaded |
preezie.addtocart
event name: preezie.addtocart
Data variable | example | Description |
|---|---|---|
preezie.product (object) |
| the name of the object containing all product details that was clicked. |
unique |
| the unique ID of the product, e.g. the SKU. This is mapped in Database > Product attributes |
name |
| the name of the product shown |
position |
| the product’s rank in the preezie results |
price |
| the price of the product |
+ any field attribute with Appears in Stats set to True in Admin > Database > Product attributes |
| These will always be text string values. All field names are lowercase and use _ in place of spaces, e.g. dress_length |
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey completed |
preezie.workflowId |
| the id of the journey completed |
preezie.addalltocart
event name: preezie.addalltocart
Data variable | example | Description |
|---|---|---|
preezie.product (array) |
| the name of the array containing all product results. |
unique |
| the unique ID of the product, e.g. the SKU. This is mapped in Database > Product attributes |
name |
| the name of the product shown |
position |
| the product’s rank in the preezie results |
price |
| the price of the product |
+ any field attribute with Appears in Stats set to True in Admin > Database > Product attributes |
| These will always be text string values. All field names are lowercase and use _ in place of spaces, e.g. dress_length |
preezie.trigger |
| how the preezie journey was triggered |
preezie.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey completed |
preezie.workflowId |
| the id of the journey completed |