Skip to main content
OneView setup

​
Introduction

OneView uses Google Tag Manager Server-Side as the primary method for sending events. This server-side approach provides improved reliability, better data quality, and full compliance with privacy regulations.
1

Get your API key

  1. Go to your OneView workspace
  2. Navigate to Settings > API Key
  3. Copy your API key
Keep your API key secure. You’ll need it to configure the GTM Server tag. Never share it publicly or commit it to code repositories.
Your API key is used to authenticate requests from your Google Tag Manager Server Container. Learn more in the API reference.
2

Install OneView Tag template from Google Tag Manager® Gallery

Server Tag

Import the open source OneView Tag template in Server-side Tag Manager®.
The template is open source and available on GitHub. You can review the code, report issues, or contribute improvements.
3

Configure the tag template

After importing the template, create a new tag using the OneView Server Tag template and paste your API key into the API Key field. You can also configure the following:
You can provide an idempotency key to prevent duplicate events. OneView converts your string into a UUID v5, which becomes the Event ID. Events with the same Event ID are deduplicated: only the first is processed.
Use a string that is guaranteed to be stable across events you want to deduplicate (e.g., transaction_id, event_name + user_id).
You may optionally provide an idempotency key to prevent duplicate events. OneView internally uses a high-efficiency UUID format to store each Event ID.OneView will generate a UUID v5 for you, based on your provided string. Multiple events with the same Event ID are considered duplicates, and only the first occurrence will be processed.
Configure additional user identifiers beyond what’s automatically collected. The template supports:
  • 💻 Client ID - Anonymous browser/device identifier
  • 👤 User ID - Authenticated user identifier
  • 🏢 Organization ID - Organization or account identifier
  • 📧 Email Address - User’s email (automatically hashed)
  • 📞 Phone Number - Phone number in E.164 format (automatically hashed)
All identifiers from your Server Container’s Common Event Data are automatically included. Use this section to add identifiers not available in Common Event Data. Learn more about user identifiers.
How it works: The template automatically collects all event data from your Server Container’s Common Event Data, extracts user identifiers (client ID, user ID, email, phone) from event payloads, and captures event metadata including page location, referrer, and UTM parameters.Privacy protection: Email addresses are automatically hashed using SHA-256, phone numbers are hashed in both E.164 and numeric formats, and first and last names are automatically hashed. Plaintext PII is removed from requests (configurable).
4

Configure triggers

Set up triggers to fire the OneView tag for the events you want to track. Common triggers include:
  • All Pages - For page view tracking
  • Custom Events - For conversion events (purchases, sign-ups, etc.)
  • GA4 Events - When using GA4 as a source
You can use the same OneView tag with multiple triggers to track different event types.
5

Test and publish

Test your configuration in preview mode, then publish your Server Container.
The template automatically handles PII hashing, consent extraction, and request formatting. No additional configuration needed.

​
Advanced Configuration

Custom Domain

Set up a reverse proxy to use your own domain for improved SEO and ITP compliance.

User Identifiers

Learn about all identifier types and how to configure them.

​
Troubleshooting

  1. Check that your API key is correct
  2. Verify the tag is firing in Preview Mode
  3. Enable debug mode in your Server Container to see request logs
The template logs all requests and responses to the console when debug mode is enabled.
If your Tag Manager® Server Container receives events from your website but is served from a different IP address (e.g., from a subdomain), you may need to configure a reverse proxy to ensure compliance with Apple Safari® Intelligent Tracking Prevention requirements.
See the Custom Domain guide for details on setting up a reverse proxy.