> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement.md).

# Roivenue Measurement

Roivenue's own tracking script for websites and apps. What it measures, what you need before you start, and which guide to follow.

Roivenue Measurement is Roivenue's own tracking script. It collects the web data that Roivenue Attribution is built on, so implementing it is the first step of a full Roivenue implementation.

Once it runs on your website or in your app, it sends Roivenue:

* **Page views and page leaves**, with the traffic source of each visit from your UTM parameters.
* **Conversions**, such as purchases, leads, or registrations, with their values.
* **Ad impressions** from display campaigns, if you set up impression tracking.

Roivenue groups these hits into sessions and links the sessions of the same visitor into customer journeys. A returning visitor is recognised by the Roivenue cookie and, if your implementation supplies them, by a device or user identifier.

***

### What you need before you start

* **Property ID.** You need it to configure the script. Your Client Success Manager (CSM) gives it to you.
* **A technical contact** with access to Google Tag Manager or to your website code.
* **A consent solution.** The script sets cookies, so in many countries visitors must give consent first. You are responsible for collecting consent according to the applicable law. Each guide shows how to connect the script to your consent settings.

***

### How to implement Roivenue Measurement

1. **Add the script to your website.** Use [Implementation through GTM](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-through-gtm) if you use Google Tag Manager. It is the fastest way. Otherwise, use [Implementation without GTM](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-without-gtm).
2. **Set up conversion tracking.** Choose how conversions are sent to Roivenue. See [Conversion tracking](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-through-gtm/conversion-tracking).
3. **Add optional tracking**, such as [Impression Tracking](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/impression-tracking) for display campaigns, or tracking in your [mobile apps](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/roivenue-measurement-for-apps).
4. **Validate the implementation.** Check that events reach Roivenue. See [Implementation validation](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-validation). Then let your CSM know, so they can check the data with you.

***

### Guides in this section

| Guide                                                                                                                                                                                        | What it covers                                                                                                                                                                               |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Implementation through GTM](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-through-gtm)                                           | Implementing the script with Google Tag Manager. Start here if you use GTM. Its subpages also cover conversion tracking, tracking through your own subdomain, and custom page view tracking. |
| [Legacy Implementation through GTM](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/legacy-implementation-through-gtm)                             | The previous GTM setup, with separate steps for the default GTM consent mode and for custom consent management systems.                                                                      |
| [Implementation without GTM](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-without-gtm)                                           | Adding the script directly to your website code: visit tracking, events, consent and anonymous tracking, and disabling measurement.                                                          |
| [Impression Tracking](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/impression-tracking)                                                         | Tracking impressions of display campaigns in DSPs with a Roivenue tracking pixel, and how to build the pixel URL.                                                                            |
| [Implementation validation](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-validation)                                             | Checking in Chrome DevTools that events reach Roivenue, that consent settings work, and that the first page view is sent.                                                                    |
| [How Sessions and Traffic Sources Are Determined](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/how-sessions-and-traffic-sources-are-determined) | How Roivenue turns hits into sessions and assigns Source, Medium, and Campaign to each session.                                                                                              |
| [Roivenue Measurement for apps](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/roivenue-measurement-for-apps)                                     | Tracking in iOS and Android applications.                                                                                                                                                    |

***

#### FAQ

<details>

<summary>1. Where do I get my Property ID?</summary>

From your CSM. Without it, the script cannot send data to your Roivenue account.

</details>

<details>

<summary>2. Should I implement through GTM or without it?</summary>

If your website uses Google Tag Manager, implement through GTM. It is the fastest way and needs no changes to your website code. If you don't use GTM, add the script directly to your website code.

</details>

<details>

<summary>3. Does Roivenue Measurement need visitor consent?</summary>

The script sets cookies, so in many countries it may run only after the visitor gives consent. Roivenue acts as a data processor. Collecting consent according to the applicable law is your responsibility.

</details>

<details>

<summary>4. How do I know the implementation works?</summary>

Follow [Implementation validation](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/implementation-validation) to check that events reach Roivenue. Then tell your CSM, who checks the data with you before you rely on it.

</details>

<details>

<summary>5. Can I keep Google Analytics 4 on my website?</summary>

Yes. Roivenue Measurement is a separate script and does not change your GA4 tracking.

</details>