...
Contact your Customer Success representative to turn on your ‘data layer’ preezie events
Create custom variables to pass what you see in the data layer values into your Google Tag Manager (GTM)
Create custom tags in your GTM to pass the data to your GA
Create the custom variables in your GA4 to use them in your reports
...
Choose the Console tab, type dataLayer (it’s case sensitive!) and hit Enter, you will now see the fired events:
...
Depending on what action you performed you will see preezie events fired (full details) for:
preezie.load - fired everytime preezie widget is loaded
preezie.click - fired everytime someone answers a question
preezie.completed - fired everytime someone completes a preezie journey
preezie.results - fired when the first page of product results is shown
preezie.resultclick - fired everytime someone clicks on a product result
preezie.email - fired if someone submits their email address into the lead capture form
preezie.addtocart - fired if someone clicks an add to cart button
preezie.addalltocart - fired if someone add a Stacks bundle to their cart
...
You’re now ready to join this custom data to your GA using GTM.
...
Now repeat these steps for the other Triggers4 triggers:
Name (5 triggers) | Trigger Type | Event name | What it captures |
|---|---|---|---|
preezie.load | Custom Event | preezie.load | Each time a preezie journey loads on the page |
preezie.click | Custom Event | preezie.click | Each time the user answers a question |
preezie.completed | Custom Event | preezie.completed | When the user has completed the journey |
preezie.resultclick | Custom Event | preezie.resultclick | Each click to the product results |
preezie.email | Custom Event | preezie.email | Each time an email is captured at the end of the journey |
...
Now you need to create tags to tell GA what event data is available. Each event fired contains parameters, you can choose which parameters you’d like to send to GA4 (full details).
Note, events not covered in the below table are:
preezie.results - this is an array of products shown in the results, and therefore not easily represented in GA statistically
preezie.addtocart / preezie.addalltocart - but use these events to fire your existing GA4 add to cart event(s)
3a. Tag set up
In GTM > Tags > New
Create and publish these tags with the below values:
| Info |
|---|
If you want to include other parameters just use the same format with the variables from Step 2a. Note, : preezie_click has both event parameters and AND user parameters |
Tag name | Taq type | Configuration Tag | Event Name | Event Parameter Name | Value | Trigger (as per Step 2b) |
|---|---|---|---|---|---|---|
GA4 preezie_load | Google Analytics: GA4 Event | (Select your GA4 variable within GTM) | preezie_load | journey_trigger | {{preezie.trigger}} | preezie.load |
journey_name | {{preezie.journey}}{{preezie.connector}} | |||||
GA4 preezie_click | Google Analytics: GA4 Event | (Select your GA4 variable within GTM) | preezie_click | journey_trigger | {{preezie.trigger}} | preezie.click |
journey_name | {{preezie.journey}}{{preezie.connector}} | |||||
journey_answer | {{preezie.answer}} | |||||
User Properties | ||||||
journey_user | {{preezie.journey}} {{preezie.connector}} | |||||
GA4 preezie_completed | Google Analytics: GA4 Event | (Select your GA4 variable within GTM) | preezie_completed | journey_trigger | {{preezie.trigger}} | preezie.completed |
journey_name | {{preezie.journey}} {{preezie.connector}} | |||||
GA4 preezie_resultclick | Google Analytics: GA4 Event | (Select your GA4 variable within GTM) | preezie_resultclick | journey_trigger | {{preezie.trigger}} | preezie.resultclick |
journey_name | {{preezie.journey}} {{preezie.connector}} | |||||
journey_product_id | {{preezie.productid}} | |||||
journey_product_name | {{preezie.productname}} | |||||
journey_product_position | {{preezie.position}} | |||||
GA4 preezie_email | Google Analytics: GA4 Event | (Select your GA4 variable within GTM) | preezie_email | journey_trigger | {{preezie.trigger}} | preezie.email |
journey_name | {{preezie.journey}} {{preezie.connector}} |
...
| Info |
|---|
All events have just event parameters, with the exception of preezie_click which has event and AND user parameters (per screenshot). |
...
| Note |
|---|
Make sure the event parameter names are identical to your GTM parameter Names. |
...
That’s it!
| Info |
|---|
Note |
...
: It can take up to 24 hours for these events to show within your GA4. |
📊 Step 4: How to use the data in GA
These events will give you the ability to segment/group behaviour by starts (i.e at least 1 preezie.click) and completed (at least 1 preezie.completed event fire).
But you can also breakdown by matching exactly/partially on the text of the values, e.g.
...
A full event definition guide can be found here: Using the Data Layer with preezie
What’s next?
Getting started with GA4 reports
...
How to create a GA4 report with preezie data
Example GA4 reports for preezie journeys
Archive
[ARCHIVE] Universal Analytics reports
...
How do preezie users convert over time? Is it same session or after several?
Does preezie help new users stay on site and/or return to convert?
etc.
[ARCHIVE] You can see how to set up UA GA reports here: Example GA Universal Analytics reports for preezie journeys