Audience

Visits vs. Events

 In Analytics Suite, the technical properties only had a visiting scope, so their value was fixed and could not change during the visit.

In Piano Analytics, these same properties have an event scope. This means that the values that could not change during the visit, can now change for each event during the visit.

In this example we can see that in Analytics Suite, the stored value is the first value retrieved during the visit, whereas in Piano Analytics, if the user changes the language of the browser during the visit, the information will be updated in the data.

To identify whether a property is open for visits or events, simply check its description.

Country and continent (geo_country and geo_continent)

 In Analytics Suite, in addition to partner detection we had an extra layer of value transformation. In order to stick as closely as possible to our service provider as well as to the ISO standards we have removed this transformation. Therefore, we can observe the value for the country St. Martin (French part) becoming France. Changes can also take place for the continent, as Turkey is in Asia with Analytics Suite and is now in Europe in Piano Analytics.

Example n°1:

Example n°2:

The location of some countries may change, such as Turkey, whose continent changes between Analytics Suite and Piano Analytics.

In Analytics Suite, Turkey was located in Asia via the AT Internet catalogue, whereas in Piano Analytics our partner locates this country in Europe.

Region (geo_region)

In Analytics Suite, in addition to partner detection we had an extra layer of value transformation. To stick as closely as possible to our service provider as well as to the ISO standards we have removed this transformation. For example, in Analytics Suite the regions of England were displayed, while in Piano Analytics our partner displays the counties.