Custom Tracking (Deprecated)


This documentation covers our pre August 2020 implementation. We strongly recommend upgrading to our latest JavaScript implementation to take advantage of performance improvements and additional features. Our migration guide can be found here.

One of our products, myReevoo Analytics, allow our customers to gauge what value Reevoo adds to their business via the visualisation of a number of metrics: publish rate, reviews collected, emails sent, conversion uplift, propensity impact, click through rate and time on site uplift.

Some of these metrics are fed by a number of tracking events that trigger automatically by our badges and embedded reviews widgets as users interact with them. When customers implement badges and embedded reviews in their websites using our ready-made web-components, nothing else needs to be done in order to have the tracking data flowing to Reevoo, this happens automatically, it is in-built in the web-components themselves.

Some other metrics needs to be triggered manually ("Purchase" and "Propensity to Buy" events)

Customers who prefer not to use our ready-made widgets to display badges and embedded reviews, and instead implement their own by using our API to get the data to display, will not benefit from the in-built tracking functionality offered by our web-components. So unless they replicate by themselves the tracking functionality as part of their widgets, most of the metrics offered by myReevoo Analytics will not be available to them.

This document is a guideline on how to implement tracking functionality in order to benefit from all the insight metrics offered by myReevoo Analytics.

What We Track and Why We Track It

We want to give users the information they want easily. In order to do this, we need to understand how users behave when using Reevoo’s services. To do this, we track information on what users do and don’t use. This involves tracking clicks on Reevoo content.

Every user has a different way of using our customers’ websites. We want to make sure that users can use Reevoo’s services, irrespective of their browser or device. We test out new features on a representative sample of devices and browsers to ensure compatibility. To determine what a “representative sample” is, we track information on what browsers and devices our users are using. We also track error messages, so we can investigate the issue and fix it for the future.

We need to prove to our customers that we are valuable to them. They usually have asked for Reevoo’s services in order to increase sales or the time spent on their website. In order to prove that we do this, we track information on how long users spend reading reviews. We also track when users read reviews and then go on to purchase the product.

We want to make sure our services are being used honestly. Trust is fundamental to Reevoo’s business, and if companies are hiding bad reviews or changing scores we need to do something about it. To ensure our services are being used correctly, we track information on requests for badges and reviews.

We do not track any information that is linked to an individual, such as a name or address. When you first visit a site you are given a unique number, and everything we track uses this number only.

What We Do With The Information

The information that we collect is stored in our database, depending on the service used to send the message. This data is usually aggregated as it comes into the database to reduce the amount of storage space it takes up.

This information is used within Reevoo for the reasons described in the sections above. Our customers also have access to this information for their own analysis.

Reevoo does not sell tracking information to anyone. We may share your information with the owner of the website you visited.

We do not use tracking information to filter what you see from our services.