Page Comparison

This article explains how you can track preezie user behaviour within your own Google Analytics (GA) reports.

...

🚀 4 easy steps

1. Contact your Customer Success representative to turn on your ‘data layer’ preezie events

2. Create custom variables to pass what you see in the data layer values into your Google Tag Manager (GTM)

3. Create custom tags in your GTM to pass the data to your GA

4. 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.

...

🖇️ Step 2: Pass preezie data into Google Tag Manager (GTM)

2a. Create the GTM

...

Data Layer Variables

This will allow any GTM tags to use the preezie data variables (as GA4 parameters) in various ways.

First go to your GTM account:

...

• Repeat these 4 steps to create the other 7 data layer variables needed:

Variable name (8 Data Layer

Variable

Variables)	Data Layer Variable Name	What it captures
preezie.trigger	preezie.trigger	How the journey was triggered (note, workflow = embedded)
preezie.journey	preezie.workflow	The name of the journey
preezie.connector	preezie.selector	The name of the journey connector (aka a workflow selector)
preezie.questionref	preezie.ref	The short version of the question
preezie.answer	preezie.answer	The text of each answer the user gives
preezie.productid	preezie.product.unique	The unique id of the clicked product in the results (as defined by your product feed attributes in the preezie CMS)
preezie.position	preezie.product.

resultsThe products that were recommended on page 1

position	The position the clicked product was ranked in the recommendation results
preezie.

productclick

productname

preezie.product.name

The name of the product that was clicked on. Note, you can add/change

to

if you have other product attributes you need as shown in your data layer, e.g. price: Image Modified

• Now to join the above to Data Layer events, repeat this the above steps 5 times but instead use variable type Custom Event - just ensure the variable names match these below:

You now have your new variables, they should look like this:

...

2b. Create the GTM triggers for your tags

In your GTM account, create these triggers before you create your tags:

preezie ‘load’ event

• Triggers > New

• Name: preezie.load

• Trigger Type: Custom Event

• Event name: preezie.load

• Save

Now repeat these steps for the other Triggers4 triggers:

...

🥽 Step 3: Create GA4 tags

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:

...

These events now need to be configured in GA4.

3b. Mapping your Custom events into GA4

Each GTM event will automatically fire into GA4 however you now need to set up the additional ‘values’ sent with each event. This means you’ll be also able to see things like answer text.

• In GA4 > Settings > Custom definitions

• Create custom dimensionAdd

  Image Added

• Then add each of these values for these events:

Dimension name	Scope	Description	Event parameter *note, must match your GTM parameter names!
preezie_trigger	Event	How the preezie widget was triggered	journey_trigger
preezie_journey	Event	Which journey was loaded and clicked on	journey_name
preezie_answer	Event	The text of each answer the user gives	journey_answer
preezie

_result

_product_id	Event	The unique ID of the clicked product (as defined in your Admin > Database > Product attributes > Unique) Image Added	journey_product_id
preezie_product_name	Event	The

products that were seen and clicked

product_name

name of the clicked product	journey_product_name
preezie_product_position	Event	The rank position of the clicked product in the preezie results	journey_product_position
preezie_user	User	Which journeys the user loaded and clicked on	journey_user

...

...

...

That’s it!

...

📊 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.

• Engagement with preezie i.e. how many clicked on preezie when it was loaded?

• Which triggers are most engaging?

• Journey click through performance by preezie.journey name

• Trigger method (embedded workflow/embedded selector/cta/popup) i.e. how they saw that journey

• Which answers are the most popular for new users?

Definition guide

• preezie.load = any time the widget is loaded, this is like a page view and can happen multiple times on the same page if you have different triggers, e.g. embedded + CTA

• preezie.click = any click to the NEXT button on a question, i.e. they answered that question

• preezie.completed = clicking on GET RESULTS, i.e. they completed the last question and now see product results

• <trigger method> =

  • workflow_ OR selector_ i.e. it was embedded on the page

  • cta_ i.e. triggered via a cta fixed to the side of the page or a custom link within your content

  • exitintent_ i.e. appeared as an exit intent pop up

  • popup_ i.e. appeared as a time delay pop up

A full event definition guide can be found here: Using the Data Layer with preezie

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

Example GA Universal Analytics reports for preezie journeys

\uD83D\uDCCB Related articles

...

• In GTM > Tags > New

• Create and Publish the below tags with these values:

...

...

• 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