Legacy Implementation through GTM
This manual describes how to implement Roivenue Measurement in your web that does use Google Tag Manager.
Last updated
This manual describes how to implement Roivenue Measurement in your web that does use Google Tag Manager.
Last updated
The following tracking script sets cookies into the users device. It tracks data which may be used for marketing optimization, content optimization or user segmentation. In some legislations the user needs to make an explicit consent before this code can be legally executed on his or her device.
As we only act as a data processor, you are responsible for obtaining consent in accordance with applicable legislation. If our tracking script gets activated and you have not complied with the applicable rules in obtaining user consent, you may be at risk of sanctions for which we are not responsible.
If you are using Google Tag Manager on your website, this is the fastest way to implement Roivenue Measurement.
Your implementation will differ depending on the system you use for consent collection. If you use the default mechanism in Google Tag Manager for consent management, follow the steps here. If you are using a custom consent management system, click here.
Property ID - You will need this to set up your script correctly. Contact your account manager to obtain it.
Download the GTM container here.
Go to your GTM (at https://tagmanager.google.com/ )
Go to Admin tab select “Import container”, select the container file you have downloaded. Select the workspace you want to import to and set “merge” option - as on the picture bellow.
Go to section “Variables”
Click on roivenue.tracking.config and change the values in the JSON object:
property_id - Insert a Property Id provided by your account manager
api_url - Check that "https://tr.roivenue.com” is filled in.
currency_code - the default currency code that will be used for tracking purchases used in case that the currency is not specified in purchase object
event_types - leave this blank unless otherwise agreed with your Account Manager.
In this step, you are setting up when Roivenue Measurement script should run. By default it runs with every page view.
Navigate to Tags section.
Select roivenue.tracking code.
Go to the section “Triggering” and add all triggers when you want Roivenue Measurement script to run
that fire on all your conversion types and all events indicating a change in consent.
The expected additional triggers are those which fire on all of your conversion events and also a trigger indicating a change in consent from a visitor. (By including this, you can switch between cookie and anonymous tracking within one session, if the consent is collected after the start of that session.)
Roivenue Anonymous Tracking can be used to track users without using any cookies and to tracks users in a limited scope.
Continue the configuration of roivenue.tracking tag in the tag section.
Change consent settings to “Not set“.
The default settings requires analytics_storage permission to be given and tracks users only if this permission was given. If you change it to "Not set", Roivenue Measurement will measure in the following way:
when analytics_storage is granted, cookies are used for tracking the user.
when analytics_storage is not granted, all user data is stored in sessionStorage of the browser. It means that cookieless tracking is enabled.
As we only act as a data processor, you are responsible for setting up the Roivenue Measurement in line with applicable legislation in your country.
If you already have ecommerce.purchase event in dataLayer, you do not need to implement anything because we will use the following fields to track a purchase conversion.
value - the conversion value
tax - the tax
currency - three letter ISO-4217 code of currency
transaction_id - the transaction ID
And we save them into these variables in Roivenue:
conversionType: 'purchase'
conversionId: transaction_id
conversionValue: value - tax
currencyCode: currency
This is how the event in your dataLayer should look like.
In case you would like to track more conversions than just a purchase or you are sending purchases to your dataLayer in a format which is different from the example above, you can.
It is possible to track any number of conversions by pushing conversionevent int the dataLayer.
If you want to send additional conversion, these are the parameters you need to send in the conversion event:
conversionType - What type of conversion it is.
converisonValue - the value without tax in specified currency
currencyCode - Three letter ISO-4217 code of currency
conversionId - an optional parameter which we recommend using in case you want to identify unique conversions later.
Any other event you track can be also set to be treated as a conversion but it needs to be set up in Roivenue app as well as in the roivenue.tracking.config variable so please contact your Account Manager if you would like to use this option.
If you have a single page website you need to inform us about page views by pushing page_view event into the dataLayer.
If ‘user’ object is set in any event item in dataLayer, we use the user.id as the unique user identifier. This is then used for identifying users and connecting their path across multiple devices. Eg:
The User ID should not be a personal sensitive information. For privacy protection reasons it is recommended to use an artificial identifier or a hash.
Property ID - You will need this to set up your script correctly. Contact your account manager to obtain it.
Download the GTM container here.
Go to your GTM (at https://tagmanager.google.com/ )
Go to Admin tab select “Import container”, select the container file you have downloaded. Select the workspace you want to import to and set “merge” option - as on the picture bellow.
Go to section “Variables”
Click on roivenue.tracking.config and change the values in the JSON object:
property_id - Insert a Property Id provided by your account manager
api_url - Check that "https://tr.roivenue.com” is filled in.
currency_code - the default currency code that will be used for tracking purchases used in case that the currency is not specified in purchase object
event_types - leave this blank unless otherwise agreed with your Account Manager.
In this step, you are setting up when Roivenue Measurement script should run. By default it runs with every page view.
Navigate to Tags section.
Select roivenue.tracking code.
Go to the section “Triggering” and add all triggers when you want Roivenue Measurement script to run
that fire on all your conversion types and all events indicating a change in consent.
The expected additional triggers are those which fire on all of your conversion events and also a trigger indicating a change in consent from a visitor. (By including this, you can switch between cookie and anonymous tracking within one session, if the consent is collected after the start of that session.)
Roivenue Anonymous Tracking can be used to track users without using any cookies and to tracks users in a limited scope.
Go to Variables.
Open the roivenue.tracking.enabled
Set up the variable in a way that it will return “True” in case the visitor should be tracked (either in a cookie mode or anonymous mode, this will be set up later). In a case you want to completely exclude user from tracking, this variable should return “False”
Open the roivenue.tracking.persistence variable.
Set it up in a way it returns localStorage+cookie in case you want to measure a user using cookies. If you want to measure this user in an anonymous mode, this variable should return sessionStorage.
When a user changes his consent, you should reflect this change in the value returned by roivenue.tracking.persistence and potentially also in the roivenue.tracking.enabled depending on your implementation.
You are using a custom consent management system and because of that, the steps above are more generic and you need to implement it using outputs from that CMS.
As we only act as a data processor, you are responsible for setting up the Roivenue Measurement in line with applicable legislation in your country.
If you already have ecommerce.purchase event in dataLayer, you do not need to implement anything because we will use the following fields to track a purchase conversion.
value - the conversion value
tax - the tax
currency - three letter ISO-4217 code of currency
transaction_id - the transaction ID
And we save them into these variables in Roivenue:
conversionType: 'purchase'
conversionId: transaction_id
conversionValue: value - tax
currencyCode: currency
This is how the event in your dataLayer should look like.
In case you would like to track more conversions than just a purchase or you are sending purchases to your dataLayer in a format which is different from the example above, you can.
It is possible to track any number of conversions by pushing conversionevent int the dataLayer.
If you want to send additional conversion, these are the parameters you need to send in the conversion event:
conversionType - What type of conversion it is.
converisonValue - the value without tax in specified currency
currencyCode - Three letter ISO-4217 code of currency
conversionId - an optional parameter which we recommend using in case you want to identify unique conversions later.
Any other event you track can be also set to be treated as a conversion but it needs to be set up in Roivenue app as well as in the roivenue.tracking.config variable so please contact your Account Manager if you would like to use this option.
If you have a single page website you need to inform us about page views by pushing page_view event into the dataLayer.
If ‘user’ object is set in any event item in dataLayer, we use the user.id as the unique user identifier. This is then used for identifying users and connecting their path across multiple devices. Eg:
The User ID should not be a personal sensitive information. For privacy protection reasons it is recommended to use an artificial identifier or a hash.
