​
Introduction

Sending events from your website can be performed in two ways: using a Google Tag Manager® Web Container, or by using Google® gtag.js directly.
MethodProsCons
Google® gtag.js
  • Easiest setup
  • Requires some Javascript knowledge
Google Tag Manager®
  • Guided setup with UI

​
Authenticating Requests

During alpha, domain verification is not available. Join and say hello in our Slack community to get a workspace for your domain!
Events sent to OneView from a Frontend Source are authenticated using . This allows your workspace to receive events for your domain.

​
Idempotent Requests

During alpha, idempotency on the frontend is not available. You can use a Backend Source if you need out of the box deduplication for your Conversion Events.

​
Sending Events

1

Add a Server URL

To send data to OneView, you need to add server_container_url to your config command:
  gtag('config', 'TAG_ID', {
    // your other config options here
    // ...
    'server_container_url': 'https://collect.oneview.eu.com',
  });
2

Review your configuration

If you choose to enable url_passthrough you must know that it will only keep Google Ads-related Click IDs in URLs, disproportionately favoring Google Ads over other sources in attribution results. Learn more. We suggest to set this to false.
If you choose to enable ads_data_redaction you must know that it will only redact Google Ads-related Click IDs from URLs, disproportionately hurting Google Ads more than other sources in attribution results. Learn more. We suggest to set this to false.
OneView is fully compatible with Google Consent Mode. No configuration required.