...
To use this data typically a Tag Manager (such as 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.
...
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 platofmrplatform, 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
...
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
| Anchor | ||||
|---|---|---|---|---|
|
...
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 |
| Anchor | ||||
|---|---|---|---|---|
|
...
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 |
| Anchor | ||||
|---|---|---|---|---|
|
...
This event is fired when the journey is completed and the product results are seen.
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 |
| Anchor | ||||
|---|---|---|---|---|
|
...
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.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 |
| Anchor | ||||
|---|---|---|---|---|
|
...
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.product (object) | the name of the |
object containing all product |
Each product is referenced by [0] [1] [2] etc
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 |
| Anchor | ||||
|---|---|---|---|---|
|
...
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.visitorId |
| the visitor’s device id |
preezie.workflow |
| the name of the journey loaded |
preezie.workflowId |
| the id of the journey loaded |
Coming soon: more Data Layer events
...
| Anchor | ||||
|---|---|---|---|---|
|
event name: preezie.addtocart
This event is fired when each time an add to cart button is clicked on the journey results.
See this guide to turn on add to cart buttons.
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 |
| Anchor | ||||
|---|---|---|---|---|
|
event name: preezie.addalltocart
This event is fired when each time the add all to cart button is clicked on the journey results.
See this guide to turn on Stacks bundling.
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 |