Use a custom domain - OneView Documentation

By using your domain for both your website and data collection servers, you can comply with Apple Safari® Intelligent Tracking Prevention (ITP) requirements

Using your domain technically means sending data using the same origin (essentially, the same IP address) of your website, for both your:

Data collection server: the server that processes your data
Web server: the server that hosts your website pages, images, and other assets

This means dedicating a of your (FQDN) to data collection purposes, for example:

https://www.example.com/metrics

Purpose	Benefits	Applies to
Sending events	Ad-Blockers events from being sent from the browser Website data will be no longer deleted after 7 days of inactivity on Apple Safari®. Learn more.	All Browsers
Serving scripts	Ad-Blockers scripts from working on the browser	All Browsers

In order to use your domain to improve your data quality, you need to set up a reverse proxy on your website.

In Enterprise plans, configuration is included. In Standard plans, it is community-supported.

This can be achieved in one of different ways, depending on how your website is hosted

Configuring the reverse proxy

You can send events using your website own domain, by using a to serve all your customer-facing traffic.

If using AWS, see Amazon CloudFront
If using Google Cloud, see Google Cloud Load Balancing
If using Azure, see Azure Front Door
If using Cloudflare Enterprise, see Origin Rules

Sending events to your domain

You neet to review the method you use to send Frontend Events from your website to OneView, and change the URL from

collect.oneview.eu.com

to the subpath you have chosen, for example www.example.com/metrics

When switching to a custom domain, the client_id is stored in an http-only cookie.

Serving scripts from your domain

This requires following the Google Tag Manager Server-Side Guide, which goes in depth in explaining how to serve scripts from your domain.

Sending Events