Configuration

Mapping

Creating variables is not enough if you want to fix your tagging, for example. In this case, you would have to map these variables to objects in order to find their values within the dimensions available Piano Analytics.

For example, if you created a variable whose purpose is to rename a page, you must then map it to the “Pages” property of the “Pages” object.

Correlation tables

Correlation tables allow you to change the value of a variable according to a key.

There are two types of correlation tables. Basic tables are based on a set of “Keys/Values”, while advanced tables are based on a set of “Sites/Keys/Values”.

Basic correlation tables are used most frequently. They allow you to create a simple correlation (translating text, for example).

Advanced correlation tables are used for virtual sites. They are used to map different values, depending on the site. For example, let’s say you use a campaign ID and you want to apply a rule to it, but the same ID exists on both site A and site B. In this case, you can use a correlation table to choose which values will be retrieved from site A and site B.

To fill out a correlation table, you can enter content for each line manually, duplicate an existing table and edit it as needed, or even import an Excel file containing your entire table.

Hit exclusion

In addition to changing values, variables can also be used to exclude traffic.

In the “Hit exclusion” menu, select a variable and apply the verification of your choice.

Please remember that the entire hit will be excluded. For example, if a page hit contains a level 2 site and a custom object, and you create a rule to exclude the level 2 site, all of the information from this page will be excluded.