Content

Case Sensitivity

In Analytics Suite, the contents (pages, clicks etc.) were stored in a non-case sensitive way. In Piano Analytics, case is taken into account. For example:

In Analytics Suite, special characters were deleted if they were not encoded. In Piano Analytics, they are kept.

On-site advertising

On-site advertising property (onsitead_type)

In Analytics Suite, the first version received was stored and retrieved for all the other versions that existed (differences in capitalisation of values in particular).

In Piano Analytics, it is the information present in the tagging that is retrieved.

On-site advertising campaign properties (onsitead_campaign / onsitead_campaign_id)

In Analytics Suite, as soon as a label/identifier combination was collected, the label was applied to all incoming events with the same identifier. In Piano Analytics, it is mandatory to always fill in the label.

Internal engine

Internal Engine Property (ise_click_rank)

In Analytics Suite, processing was applied to obtain only positive rank values. In Piano Analytics, we obtain the value present in the tag without reprocessing.

Internal Engine Property (ise_keyword)

In Piano Analytics, by default we put all the keywords received in lower case.

For example, this enables you to merge the values "iPhone" and "iphone" into a common value: "iphone".

It is possible to delete this rule.

Internal Engine Property (ise_page)

In Analytics Suite, for any page number greater than 50, 50+ was the default value. In Piano Analytics, we keep the value sent by the tag without reprocessing.

Custom Indicators

In Analytics Suite, when the indicator rose to '0' it was ignored. In Piano Analytics, we keep the value sent by the tag without reprocessing.

Text format (character string)

In Analytics Suite, custom metrics in text format had to have their values in square brackets [] to ensure that the correct value was taken into account. Without square brackets the values were considered numeric. In Piano Analytics, we keep the value sent by the tag without reprocessing. 

The full digital format

In Analytics Suite, values that were not entirely numerical for numerical variables were ignored. In Piano Analytics, we keep the first numeric found.

Example:

IDs

In Analytics Suite, if the ID was not declared, no value would appear. In Piano Analytics, if the ID is not declared it will be kept as a value.

Custom order indicators

In Analytics Suite, the custom order indicators only tracked order events. In Piano Analytics, they track all types of events.

Event-specific properties

In addition to the existing properties, some have been added.

Namely: event_collection_platform | event_collection_version | event_url_domain | event_duration

Proprerty event_time

The timestamp of this property has evolved between Analytics Suite and Piano Analytics. It is now more accurate as it is no longer in seconds but in milliseconds.

event_url properties | full_event_url

In Analytics Suite, the URL Pages dimension was optionally enabled. Depending on the option, the Query String was filled in. In Piano Analytics, the URL is automatically stored without Query String in event_url and with Query String in event_url_full.

Chapters

Additional chapters (page_full_name click_full_name)

In Analytics Suite, when a page or a click contained more than 3 chapters (marked with the "::" characters), all additional chapters were concatenated in the label and the "::" were replaced by an underscore.

In Piano Analytics, only level 1, 2 and 3 chapters are concatenated.

In Analytics Suite, in case the first chapter had no value, it was replaced by an underscore. In Piano Analytics, the value is disregarded. For example for the property page_full_name: