Onsite behavioural data

The second stage consists in collecting two types of data on your site:

  • Browsing data

  • Conversion data

Browsing data is collected using two TagCommander tags called “MIX - Click and Site Tracking” and “MIX Site Tracking Only“. These tags, set up by your consultant at the beginning of the project, are available at the “SELECT” and “EDIT” stages of the TagCommander product, in the tags library.

The “MIX - Click and Site Tracking” tag retrieves all the visitor’s browsing details (number of pages viewed, bounce rate, visits, etc.), and its traffic source.

This must be called on all your site’s pages except for the confirmation page, where you should call the “MIX Site Tracking Only” tag and the “Measure –Conversion 3.5” tags. The “MeasureSite Tracking Only” tag is used to collect the visitor’s browsing information on the confirmation page without capturing the visit’s origins, in order to avoid seeing touchpoints from online payment platforms in the customer journey (e.g.: Ogone, PayPal, etc.).

Configuring the "MIX - Click & Site Tracking V3.5" tag

Step 1 – “EDIT”

You first add the “MIX - Click and Site Tracking V3.5” tag in the “SELECT” or “EDIT” step. Then add all the data it needs to generate full reports on the MixCommander interface. To do so, go to the “EDIT” tab of the TagCommander product.

Add the following variables to your “MixCommander Click and Site Tracking 3.5” tag:

The type of pages visited

  • Variable #PAGENAME# is the page name (generally external variable tc_vars[“page_name”] or URL of the current page)

  • Variable #PAGETYPE# must be mapped to the page’s template (generally external variable tc_vars[“env_template”])

Brand name details

These are optional and should only be completed if you wish to distinguish between brand SEO and non-brand SEO (NB: As Google no longer transmits the user’s search keywords, the brand/non-brand SEO data collected by the Commanders Act MixCommander product will not be exhaustive):

  • Variables #BRAND_NAME…# must be completed with the name(s) of your brand required to identify brand SEO.

User ID

This information is optional, it allows Commanders Act to match a given user’s journeys and conversions occurring on different devices (Note: for optimal performance, it is recommended that the user ID is made available during all of the user’s browsing).

  • The #USER_ID# variable has to be populated with your visitors’ User ID.

Sites to exclude from the “Referrer” channel

When a user clicks an untracked link and lands on your site, the touchpoint is attributed to “referrer”. If you wish to exclude sites from the “referrer” channel (ex: payment platforms), you need to specify their domain names.

  • The #EXCLUDED_REFERRER# variable has to be populated with the domain names or sub-domain names to exclude, separated by a coma. (It is not necessary to type “www”).

Ex: referrer1.com, referrer2.com

Additional search engines to consider for the “SEO” channel

Commanders Act has an up to date, comprehensive list of search engines, but you have the possibility to add more.

  • The #SEARCH ENGINES# variable has to be populated with the names of search engines that will be taken into consideration for SEO, as well as the value of the URL parameter containing the keyword that is searched for by the user. (ex: parameter “q” in the following URL : https://www.google.fr/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=keyword . The name of the search engine and the parameter’s name have to be separated with “|”. The names of search engines that are considered need to be separated with a comma.

Ex : searchengine1|param_searchengine1,searchengine2|param_searchengine2

Additional Social networks

Commanders Act has an up to date, comprehensive list of social networks, but you have the possibility to add more.

  • The #SOCIAL NETWORKS# variable needs to be populated with the names of the social networks to be taken into consideration and separated with a comma.

Ex : socialnetwork1,socialnetwork2

SEO Brand

In case you wish to count SEO visits without keywords that land on your website’s homepage as “SEO brand”.

  • The #BRAND_URSL# variable needs to be populated with the exact URLs of landing pages separated with a comma. (Remember to take the protocol into consideration and do not forget the “/” at the end of the URL if it is present). Ex: http://www.mysite.com/

Sites to consider as “internal” traffic

When a user clicks an untracked link and lands on your site, the touchpoint is attributed to “referrer”. If you do not want to consider internal traffic (ex: a brand’s satellite sites or other countries’ sites), you need to specify the websites.

  • The #SUBDOMAINS# variable has to be populated with the URLs of the sites you want to exclude, without the protocol and the query string. Each URL needs to be separated with a comma. Pay attention not to mention your own site’s domain name (i.e. the site on which the Measure tag is placed).

Ex : www.referer1.com/de (if the URL is: « http://www.referer1.com/de?param=test »)

All fields are limited to 255 characters.

Step 2 – “Rules”

The second step consists in adding the “MixCommander Click and Site Tracking 3.5” tag to all the pages on your site apart from the confirmation page.

You can create your rule on the “Rules” tab:

Configuring the "MIX - Site Tracking only V3.5" tag

Step 1 – “Edit”

You first add the “MIX - Site Tracking Only V3.5” tag in the “SELECT” or “EDIT” steps. AThen add all the data it needs to generate full reports on the MixCommander interface. To do so, go to the “EDIT” tab of the TagCommander product.

Your “MIX - Site Tracking Only V3.5” tag must be completed with:

The name of the viewed page

Variable #PAGENAME# must be completed with the name of the page (generally external variable tc_vars[“page_name”] or URL of the current page).

The type of page viewed

Variable #PAGETYPE# must be mapped to the page template (generally external variable tc_vars[“env_template”]).

Step 2 – “Rules”

The second step consists in adding the “MixCommander Site Tracking Only 3.5” tag to the confirmation page only.

You can create your rule on the “Rules” tab:

Configuring the "MIX - Conversion V3.5" tag

Conversion data is collected via a TagCommander tag called “MIX - Conversion V3.5“. This tag, set up by your consultant at the beginning of the project, is available in the “SELECT” or “EDIT” steps in the TagCommander product:

It retrieves all the conversion details: order ID, order amount at the very least. But also other details concerning conversions, such as segments (repeat/new customers, device, country, etc.).

It must be included on your site’s confirmation page.

Step 1 – “EDIT”

The first step consists in adding the “MIX - Conversion V3.5” tag in the “SELECT” or “EDIT” sections in the TagCommander product. Then, adding all the data it needs to provide conversion information in the reports.

Your “MIX - Conversion V3.5” tag must be completed with:

Details of the conversion ID

  • variable #TCIDORDER# must be completed with the conversion ID (generally external variable tc_vars[“order_id”]).

Conversion amount details

  • variable #TCAMOUNT# must be completed with the conversion amount (generally external variable tc_vars[“order_amount”]). If you do not have the conversion amount (e.g.: when conversions on your site consist in form-filling or registration), the value of this variable is “1”.

Details of the conversion currency

  • variable #TCCURRENCY# must be completed with the currency of your site (EUR by default).

You can also add other parameters to your conversion tag. Just fill in the line labelled “tC.msr.additional_params“.

In the example below, we have added 3 conversion segments to the tag “MixCommander Conversion 3.5“: a “device” segment to retrieve the device on which the conversion took place, a “customer_type” segment to determine user status (repeat or new customer), and a “country” segment to determine the country of conversion:

To retrieve more information, just add parameters like this:

Step 2 – “RULES”

The second step consists in adding the “MIX - Conversion V3.5” tag to the site’s conversion page.

You can create your rule on the “RULES” step (1) in the TagCommander module:

When the “MIX - Click and Site Tracking V3.5“, “MIX - Site Tracking Only V3.5” and “MIX - Conversion V3.5” tags are in place, Commanders Act is ready to collect all the needed information to generate Attribution reports.