Advanced Tracking Configurations

This document covers

  • Filtering Pages From Being Tracked
  • Cross Domain Tracking
  • Content Privacy Management (Masking / Whitelisting)
  • Using A Custom DataLayer Name
  • Single Page Application Tracking (Tracking URL changes)

Filtering Pages From Being Tracked

By default, website activity and behaviours will be tracked on all pages that include your Insightech tracking code. If you decide that you'd like to track only a selection of these pages, you can do this by switching the setting below from All Pages to Some Pages.

From here, all you need to do is to include the set of conditions to either identify the hostname/path/URLs that you would like included or excluded.

There are plenty of conditions that you can choose from including using regex to specifically capture the pages you want to focus on.

Cross Domain Tracking

Once you have done this, you'll need to also add in all of your domains into your profile settings, under Admin --> Profile Settings.

Simply input all of your domains in the Domains input field. Each domain should be on a new line, and it is recommended that you remove the prefix of your website (no http://, and no www.). In removing the prefix of your websites, this ensures that all subdomains of your websites will also be included.

Once complete, simply hit and then your cross-device tracking is setup.

Content Privacy Management (Masking / Whitelisting)

At Insightech, we take user privacy very seriously and we have developed features to specifically help protect the privacy of your users, and their personally identifiable information (PII) as they interact with your website.

Masking Content

There are two methods available for PII removal:

  1. Insightech automatically masks all input fields by default
  2. Custom PII masking (Using css selectors set in your profile custom tracking)

On the Tracking code page, input your CSS selectors in the Mask PII Content input field, on separate lines for each CSS selector to be masked.

Example:

Once this is saved, your platform will automatically roll out the changes across your website.

Whitelisting Fields

The same method as Custom PII masking can be used to whitelist fields, within your profile custom tracking.

Here is an Example:

Using A Custom DataLayer Name

Any data layer item can be looked up in the Insightech system. If your data layer object has the default name of "dataLayer", then Insightech will automatically identify and capture your data layer. If you are using another data layer name, this can be updated in the platform settings.

Pointing Insightech At Your DataLayer

If you are using "dataLayer" as the name of your custom data later, then you do not need to update this.

If you are using an alternate name for your custom data layer, then you will need to follow the steps below.

  1. Click on Admin —> Tracking Code to go into the tracking code settings
  1. Click on the Advanced Tracking Configurations button
  2. Once in the Advanced Tracking Configurations, navigate to the dataLayer Object Name field. Input your custom data layer name, and Insightech will begin to capture this in your data.

Note: Your dataLayer object name will be set to "dataLayer" by default.

Look at Using Your Custom DataLayer In Insightech for a full explanation on leveraging your datalayer (including searching datalayer attributes in Insightech).

Single Page Application Tracking (Tracking URL Changes As Separate Pages)

If you are using Single Page Applications (SPA) across your website, you may want to track each dynamic page as separate pages.

In the Advanced Tracking Configurations page, you will see a section to Track URL Changes as Separate Pages as below:

By default this will be set to Enabled. This means that in the instance that your Single Page Application (SPA) is also updating the URL of the page, Insightech will treat these page changes as individual pages.

Once setup, Insightech will identify each stage of your single page application as individual pages, making it easier to analyse the full flow of your Single Page Application in session replays and in all other reports (E.g. click maps).


How did we do?


Powered by HelpDocs

Powered by HelpDocs