Skip to main content

​
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

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.
2

Configure the tag template

After importing the template, create a new tag using the OneView Server Tag template and configure the following:
Generate an API Key from Settings > API Key in your OneView workspace, then paste it into the API Key field in the tag template.
Keep your API key secure. Never commit it to version control or expose it in client-side code.
Optionally provide an idempotency key to prevent duplicate events. Multiple events with the same idempotency key are considered duplicates, and only the first occurrence will be processed.
Use a unique identifier for each event (e.g., transaction ID, event timestamp + user ID) to ensure reliable deduplication. See the API reference for details.
How it works: The template automatically formats events according to OneView’s API specification, adds required authentication headers, and includes your idempotency key for deduplication. Requests are sent to https://earth.oneviewhub.cloud/v1/sgtm.
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).
3

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.
4

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.