Sources

Source Detection

In order to enter the source, we base ourselves on the previous URL as well as the presence or absence of campaign tagging. From this, we natively feed these 3 properties for all types of events:

• ‘Source’ (src)
• ‘Source - Detail’ (src_detail)
• ‘Campaign / naturel’ (src_type)

Organic sources

To determine whether a source is organic or custom organic, we check that there is no campaign tagging, and we retrieve the previous URL of the event (src_url property provided organically).

In the absence of campaign tagging, the 'Campaign / natural' property (src_type) automatically takes the value 'organic'.

Marketing sources

In Analytics Suite, we continue to check for the presence of campaign tagging (xtor link or at_campaign). Campaigns must always be declared in the interface if the self-declaration option is not activated.

In Piano Analytics, the campaigns are filled in the tagging according to the Tag First model. The tagging must include the properties: 'Campaign' (src_campaign) and 'Campaign type' (src_medium). If this second property is empty, it will be filled in 'unclassified campaign'. It will be possible to add as many properties as necessary to describe the campaign, however we recommend the following nomenclature to have the same scope as the standard source properties: 'src_xxxx'.

When the 'Campaign' property (src_campaign) is populated, the 'Campaign / natural' property (src_type) automatically takes the value 'campaigns'.

Source Detection Rules

With the arrival of Piano Analytics, certain detection rules concerning sources have evolved. Thanks to the Tag First approach, it offers in particular greater flexibility in the processing of campaign collection. All these changes can therefore lead to switches from certain types of sources to different sources.

Unknown campaigns

In Piano Analytics, when campaigns come up with a numeric ID not declared in the interface and not belonging to a dynamic campaign range, all campaign properties are cleared.

If campaigns come up with a text ID then we collect and store all data received. The campaigns will then be retrieved as dynamic campaigns and all associated properties will be retained. The prior declaration of the campaigns is therefore no longer necessary in this case.

Note: If you use the automatic campaign declaration option then it doesn't matter if the ID is numeric or text type, the campaign information will be retrieved without declaration.

Campaign attribution

In the same way, campaign attribution can be disrupted. Previously, when we received an ID associated with a certain campaign type that did not match what was defined in the interface, the campaign was re-attributed to the type that had been declared. From now on, priority is given to the tag, and therefore to the type indicated in the tagging.

For example, if an emailing campaign with the ID 6 was collected, but the ID 6 had been declared for an affiliation campaign, then the campaign was considered as affiliation with the properties specific to this type of source. In Piano Analytics, it is the emailing type entered in the tagging that will have priority with the properties associated with the emailing.

Google Adsense

In Piano Analytics, the Google Adsense referrer is considered as an 'Affluent Sites' source. We find the following values for 'Previous URL - Domain' (src_url_domain):

• com
• doubleclick

In Analytics Suite, when Google Adsense was detected, we would retrieve the &url= parameter containing the user's original site.

In Piano Analytics, this information is lost, and we display the referrer from the now organic source, i.e. googleads, for example:

General properties

Preceding URL, preceding URL - domain, source full URL (src_url, src_url_domain, src_url_full)

In Piano Analytics, the preceding URL is available for any type of event, not just when the source was an 'Affluent Site'.

The preceding URL property (src_url) now contains the protocol and the '/' that may be present after the domain name.

Organic Sources

Social networks (src_social_networks)

A new native organic source "Social Networks" is now available with Piano Analytics.

For some organisations, this means that there may be a conflict in a dataset between the organic source and a former personalised source relating to social networks. In such cases, it is necessary to look at the priorities given to these sources.  It is then possible to:

• Rename the custom organic source (Recommended choice)
• Handle this break in analysis
• Update custom organic source ranking

Below is the list of social networks detected by default:

End of brand awareness

99% of the keywords searched for in search engines are no longer provided, therefore the source 'Notoriety' has been removed from our source detection in Piano Analytics.

Portal site (src_portal_site, src_portal_site_id, src_portal_url)

Previously, the option of portal sites was limited to the contract. This now extends to the entire organisation. It is therefore possible to detect new sites as portal sites.

Engine - Localisation (src_se_category)

In Piano Analytics, the value 'Search bar' becomes 'Search'.

Marketing Sources

Emailing - Clicked link (src_email_link)

In Analytics Suite, the 'clicked link' property of an e-mailing campaign could only be retrieved if the 'e-mail label' property had been filled in. In Piano Analytics all information in the tag is taken into account.

Campaign - Variant (src_variant)

In Analytics Suite, the 'variant' property of an advertising campaign could only be retrieved if the 'creation' property had been filled in. In Piano Analytics all information in the tag is taken into account.