GTM - Tracker settings

Introduction

All the parameters needed for the tracker to communicate with Splio web tracking collector are stored in a Snowplow v3 Settings variable.

This page will guide you through the creation of this variable.

📘

The default settings for all Snowplow tags will use one unique variable created from a template

⚠️

If you manage multiple sites with the same Google Tag Manager container, create one distinct variable for each of them, as the property Tracker Options > Collector endpoint will be different

List of the settings that will be changed throughout this page

Section

Property

Value

Tracker Options

Tracker Name

Any unique name you prefer for this tracker.
⚠️** Note that if you have already configured a Snowplow Tracker you will have to setup here a different name.**

Example :ecommerceMarketingTracker

Tracker Options

Collector Endpoint Hostname

Splio CDP endpoint url, compatible with various web tracker event protocols, including Snowplow. It is provided by your project manager during integration

Example : https://web-collector.splio.com/collector/v1/e911bba6-aedf-41ff-a744-cbd706fdc666

Tracker Options, sub section Javascript Tracker

Snowplow JavaScript Tracker Library

You can keep default jsDelivr which is a free CDN dedicated to open source projects, where Snowplow Opensource tracker is available

Tracker Options, sub section Javascript Tracker

Library version

Setup the last version as specified by your project manager. Supported version: from 3.17.0 to 3.24.6included.
See release list for available versions

Application Settings

Application ID

Your unique identifier, specified with the project manager that should be your tenant name by default.

Example :

my_store_fr

Privacy

Respect "Do Not Track"

Always select "True" on Respect "Do Not Track

Cookie Settings

State Storage Strategy

Use a “Cookie and Local Storage” strategy. Note that it will be a first party cookie.

Cookie Settings

Cookie Name

Adapt the default cookie Name to your preferences. For example sp_marketing

Cookie Settings

On all other properties

Keep default configuration

Steps

  1. Create a new Variable named Default SP Settings

  2. In Variable Configuration, choose Snowplow v3 Settings

    You may have to click on “Discover more variable types in the Community Template Gallery "

  3. Fill the following fields

    • Tracker Name : Arbitrary name for the tracker. Example value: ecommerceMarketingTracker
      ⚠️ If multiple snowplow tracker are defined, each one of them should have a different name
    • Collector Endpoint Hostname
      Splio CDP endpoint url, compatible with various web tracker event protocols, including Snowplow. It is provided by your project manager during integration
  4. Define the Javascript Tracker settings

    • Snowplow Javascript Tracker Libary
      You can keep default jsDelivr which is a free CDN dedicated to open source projects, where Snowplow Opensource tracker is available
    • Library version
      Setup the last version as specified by your project manager. Supported version: from 3.17.0 to 3.24.6included.
      See release list for available versions
  5. In the Application Settings section, fill in the Application ID (app_id) field with the value provided by the Project Manager

  6. In the Privacysection, set the Respect "Do Not Track" at True

  7. In the Cookie Settingssection, you can change the following settings as follow:

    • State Storage Strategy: Use a “Cookie and Local Storage” strategy. Note that it will be a first party cookie
    • Cookie Name: Adapt the default cookie Name to your preferences. For example sp_marketing
  8. Save the variable