Main Implementation
Implementation of Roivenue Measurement
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.configand change the values in the JSON object:property_id- Insert a Property Id provided by your account managerapi_url- Should be "https://tr.roivenue.com” unless you implement a custom tracking domain. In that case, change the parameter accordingly.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- List of dataLayer events that are automatically being captured when the measurement tag is triggered. More about possible changes in the Capturing Events section. Remember that you still need to set the tag triggers!

Setting up Triggers
Navigate to Tags section.
Select
roivenue.trackingcode.Go to the section “Triggering” and add all triggers when you want Roivenue Measurement script to run

Capturing Events
By default these event types are being tracked automatically:
page_viewconversionpurchaseecomm_purchase
Tracking Page Views
Tracking Users
Tracking Purchases and Other Conversions
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.
Setting up Consents and Anonymous Tracking

By default when Roivenue Measurement tag is triggered, It automatically reads the consent settings from dataLayer and use different persistence settings based on setting of analytics_storage consent variable.
How to set up consent when the Google Tag Manager's consent system is not used
Go to Variables.
Open the
roivenue.tracking.enabledSet 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.persistencevariable.Set it up in a way it returns
localStorage+cookiein 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.persistenceand potentially also in theroivenue.tracking.enableddepending on your implementation.
Cross Domain Tracking in Cookieless Mode
with enabled cookeis, then the events will be connected a single visit. But if user does the same in cookieless mode, there would be a second visit at checkout.yourshop.com and all conversions then would be tracked with www.yourshop.com as a referrer traffic source.
To prevent this:
1. Set write_cross_domain_info in roivenue.measuerement.config to true.
A referrer policy needs to be set to allow this mechanism to work.
Roivenue platform uses PostHog for analytics. PostHog is licensed under the MIT License. For more details, please see PostHog's GitHub repository or the full MIT License text.
Last updated
Was this helpful?