Legacy Implementation through GTM
This manual describes how to implement Roivenue Measurement in your web that does use Google Tag Manager.
Legal Notice
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.
Implementation for default GTM Consent Management System
Prerequisites
Property ID - You will need this to set up your script correctly. Contact your account manager to obtain it.
Initial Setup
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 managerapi_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 objectevent_types
- leave this blank unless otherwise agreed with your Account Manager.

Setting up Triggers
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.)

Setting up Consents and Anonymous Tracking

Continue the configuration of
roivenue.tracking
tag in the tag section.Change consent settings to “Not set“.

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.
Setting up Conversions Tracking
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.
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 currencycurrencyCode
- Three letter ISO-4217 code of currencyconversionId
- an optional parameter which we recommend using in case you want to identify unique conversions later.
dataLayer.push({
'event' : 'conversion',
'conversionId': 'T_12345', // optional
'conversionType': 'goal1',
'conversionValue' : 123,
'currencyCode' : 'CZK'
});
Extra Step for Single Page Applications ONLY
If you have a single page website you need to inform us about page views by pushing
page_view
event into thedataLayer
.
Other Information
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.
Implementation for Custom Consent Management Solution
Prerequisites
Property ID - You will need this to set up your script correctly. Contact your account manager to obtain it.
Initial Setup
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 managerapi_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 objectevent_types
- leave this blank unless otherwise agreed with your Account Manager.

Setting up Triggers
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.)

Setting up Consents and Anonymous Tracking
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 returnsessionStorage
.When a user changes his consent, you should reflect this change in the value returned by
roivenue.tracking.persistence
and potentially also in theroivenue.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.
Setting up Conversions Tracking
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.
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 currencycurrencyCode
- Three letter ISO-4217 code of currencyconversionId
- an optional parameter which we recommend using in case you want to identify unique conversions later.
dataLayer.push({
'event' : 'conversion',
'conversionId': 'T_12345', // optional
'conversionType': 'goal1',
'conversionValue' : 123,
'currencyCode' : 'CZK'
});
Extra Step for Single Page Applications ONLY
If you have a single page website you need to inform us about page views by pushing
page_view
event into thedataLayer
.
Other Information
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.
Last updated
Was this helpful?