Skip to main content

​
Introduction

Before sending events to OneView, you need to configure your workspace. This includes setting up your API key, connecting advertising platforms, and configuring which events should be sent as conversions.
Most workspace settings are optional. You can start with just an API key and add integrations later.
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

Connect your advertising platforms (Optional)

Connect the advertising platforms where you want to send conversions:
OneView supports over 30 advertising platforms including:Ad Networks:
  • Google Ads, Meta (Facebook/Instagram), TikTok, Microsoft Ads, LinkedIn, Pinterest, Snapchat, Twitter/X, Reddit, Quora, Spotify
Affiliate Networks:
  • Awin, CJ Affiliate, FinanceAds, Impact, Partnerize, Rakuten, Tradedoubler
DSPs:
  • Amazon DSP, Criteo, Google DV360, Outbrain, Quantcast, Stackadapt, Taboola, The Trade Desk
See the full list of supported integrations and their setup guides.
  1. Go to Settings > Ad Accounts
  2. Click Connect next to the platform you want to add
  3. Follow the OAuth flow to authorize OneView
Each platform has specific setup requirements. See the individual integration guides for detailed instructions.
Once connected, OneView can automatically:
  • Send conversions to the platform’s Conversion API
  • Include Enhanced Conversions (hashed PII) for better match rates
  • Handle API errors and retries automatically
  • Respect user consent across all platforms
Learn more about how integrations work and Enhanced Conversions.
3

Configure conversion events (Optional)

Choose which events should be sent as conversions to your advertising platforms:
Conversion events are specific actions you want to track (like purchases, sign-ups, or form submissions). OneView will:
  • Process these events through attribution
  • Send them to your connected advertising platforms
  • Include Enhanced Conversions for better match rates
Learn more about how conversions work.
  1. Go to Settings > Conversions
  2. Select which events should be treated as conversions
  3. Configure attribution model for each event (optional)
You can configure different attribution models for different events. For example, use first-touch for brand awareness events and last-touch for purchase events.
You can configure attribution on a per-event basis:
  • First-Touch - Credits the first marketing interaction (best for long sales cycles)
  • Last-Touch - Credits the final interaction before conversion (best for e-commerce)
  • Multi-Touch - Distributes credit across multiple touchpoints (not available for all platforms)
Learn more about attribution models and how OneView routes conversions.
4

Configure Enhanced Conversions (Optional)

Enhanced Conversions include hashed email addresses and phone numbers to improve match rates with advertising platforms.
Yes. Enhanced Conversions are automatically enabled for all platforms that support them. OneView automatically:
  • Hashes email addresses and phone numbers using SHA-256
  • Includes identifiers from your Identity Graph
  • Respects user consent (only includes PII when consent is granted)
No configuration needed. Enhanced Conversions work automatically.
Yes. You can disable Enhanced Conversions per platform:
  1. Go to Settings > Accounts > [Platform Name]
  2. Click PII Handling > None
Disabling Enhanced Conversions reduces match rates, especially when click identifiers are blocked or expired. This may impact campaign optimization accuracy.
OneView automatically enriches conversions with identifiers from your Identity Graph:
  • If a user signed up: Includes email, phone (if provided), and user ID
  • If anonymous: Includes client ID and device ID
  • If cross-device: Includes all identifiers from linked devices
Learn more about Enhanced Conversions and Identity Resolution.
5

Configure UTM sources (Optional)

Configure which utm_source values should be recognized as your advertising platforms.
When click identifiers (like gclid, fbclid) are blocked or missing, OneView uses utm_source to identify which platform should get attribution credit.
This is especially important for cookieless advertising scenarios and Intelligent Tracking Prevention compliance.
  1. Go to Settings > UTM Sources
  2. Map your utm_source values to your advertising platforms
  3. OneView will use these for attribution when click IDs are unavailable
Learn more about how UTM fallback works in OneView.

​
What Happens Automatically

Once your workspace is configured, OneView automatically handles:
  • ✅ Attribution - Routes conversions to the platform that wins attribution using Merit-Based Routing
  • ✅ Deduplication - Prevents the same conversion from being counted multiple times
  • ✅ Enhanced Conversions - Includes hashed PII for better match rates
  • ✅ Consent Enforcement - Respects user consent across all platforms automatically
  • ✅ Error Handling - Automatically resolves API errors and retries failed requests
  • ✅ Identity Resolution - Builds Identity Graph to link users across devices and sessions
Want to understand how this all works together? See How OneView Works for a complete overview.

​
Workspace Settings Reference

API Key

Learn about API authentication and security.

Integrations

See all supported platforms and setup guides.

Conversions

Understand how conversions are processed.

Attribution Models

Learn about attribution models and routing.

Enhanced Conversions

Understand Enhanced Conversions and match rates.

Identity Resolution

Learn how OneView builds Identity Graphs.

​
Troubleshooting

Go to Settings > API Key in your OneView workspace. If you don’t see this option, make sure you have the correct permissions.
You’ll need your API key to configure the GTM Server tag.
  1. Go to Settings > Ad Accounts
  2. Find the platform you want to disconnect
  3. Click Disconnect
When you disconnect a platform, all credentials are deleted from OneView and access revocation is requested automatically. Learn more in the integration guides.
If your workspace exceeds session or conversion limits, OneView will:
  • Mark affected sessions under the “Unknown” channel
  • Exclude them from attribution to preserve model integrity
  • Show them in reports for diagnostics
Review your workspace limits and recent volume trends. Contact support if you need to increase your quota.