Versions Compared

Old Version 40

changes.mady.by.user Graham Ralls (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Graham Ralls (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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.

...

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

Variable name (8 Data Layer VariableVariables)

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

The position the clicked product was ranked in the recommendation results

preezie.productname

preezie.product.name

The name of the product that was clicked on.

Note, you can add/change if you have other product attributes you need as shown in your data layer, e.g. price:

...

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 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
Custom Event

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
Custom Event

journey_name

{{preezie.journey}}{{preezie.connector}}

journey_answer

{{preezie.answer}}
OR
{{preezie.questionref}}_{{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
Custom Event

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
Custom Event

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
Custom Event

journey_name

{{preezie.journey}} {{preezie.connector}}

...

Info

All events have just event parameters, with the exception of preezie_click which has event AND user parameters (per screenshot).

These events now need to be configured in GA4.

...

  • In GA4 > Settings > Custom definitions

  • Create custom dimensionAdd

    image-20240216-031140.pngImage 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_product_id

Event

The unique ID of the clicked product
(as defined in your Admin > Database > Product attributes > Unique)

journey_product_id

preezie_product_name

Event

The 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

...

Note

Make sure the event parameter names are identical to your GTM parameter Names

...

.
Note, all are Event scoped except for preezie_user.

...

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