Skip to main content
OneView automatically includes hashed PII in conversions for higher match rates with advertising platforms. No configuration required.

​
What are Enhanced Conversions?

Enhanced Conversions include hashed personally identifiable information (PII) along with conversion data, allowing advertising platforms to match conversions to their user base even when click identifiers are missing or expired.
Understanding match rates:When click identifiers (like gclid, fbclid) are unavailable due to:
  • Browser privacy features blocking tracking parameters
  • Expired click-through windows
  • Cross-device conversions
Enhanced Conversions use hashed PII (email, phone number) to maintain attribution accuracy by allowing platforms to match conversions on their end.

​
How Enhanced Conversions work

OneView automatically enriches conversions with identifiers from your Identity Graph and includes them in Conversion API requests:
ScenarioIdentifiers IncludedMatch Rate Impact
User signed upEmail, phone (if provided), user IDHigh match rate
Anonymous visitorClient ID, device IDLower match rate
Cross-deviceAll identifiers from linked devicesHigh match rate
Enhanced Conversions are automatically enabled for all Conversion API integrations that support them. You can disable this feature per integration in your workspace settings.

​
Automatic enrichment

OneView uses your Identity Graph to automatically include the most complete set of identifiers available:
SourceIdentifiers Used
Identity GraphEmail, phone, user ID from linked sessions
Event payloadIdentifiers sent with the conversion event
Cross-deviceIdentifiers from other devices linked to the same user
Enhanced Conversions require user consent for ad_user_data and ad_personalization. OneView automatically respects consent and only includes PII when consent is granted.

​
Privacy and compliance

OneView automatically hashes all PII using SHA-256 before including it in Enhanced Conversions:
PII TypeHashingStorage
EmailSHA-256Never stored in plaintext
Phone numberSHA-256Never stored in plaintext
User IDIncluded as-isIf provided
All PII is automatically hashed using SHA-256 before processing or storage. OneView never stores plaintext sensitive data.

​
Platform support

Platform-specific implementation details vary. OneView automatically adapts Enhanced Conversions to each platform’s requirements and API specifications.
Check out the Conversion API integrations page to see which platforms support Enhanced Conversions.

​
Common questions

It depends on the Media Partner. Most platforms accept:
  • Email (hashed)
  • Phone number (hashed)
  • User ID (if provided)
OneView automatically includes all available identifiers from your Identity Graph. Check each integration’s documentation for specific requirements.
OneView uses your Identity Graph to automatically enrich conversions with identifiers from:
  • The current event payload
  • Linked sessions and devices
  • Previously connected identifiers
No manual configuration required.
Yes. You can disable Enhanced Conversions per integration in your workspace settings under Settings → Accounts → [Platform] → PII Handling → None.
Disabling Enhanced Conversions reduces match rates, especially when click identifiers are blocked or expired. This may impact campaign optimization accuracy.

​
Next steps

Identity Resolution

Learn how OneView builds Identity Graphs to enrich Enhanced Conversions.

Consent Enforcement

Understand how OneView automatically enforces consent for Enhanced Conversions.