> ## Documentation Index
> Fetch the complete documentation index at: https://oneviewhub.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Enhanced Conversions

> Automatically includes PII in conversions for increased match rates and placement optimization.

<Check>
  OneView automatically includes hashed PII in conversions for higher match rates with advertising platforms. No configuration required.
</Check>

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

<Info>
  **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.
</Info>

## How Enhanced Conversions work

OneView automatically enriches conversions with identifiers from your [Identity Graph](/docs/platform/features/processing/identity-resolution) and includes them in Conversion API requests:

| Scenario              | Identifiers Included                | Match Rate Impact |
| --------------------- | ----------------------------------- | ----------------- |
| **User signed up**    | Email, phone (if provided), user ID | High match rate   |
| **Anonymous visitor** | Client ID, device ID                | Lower match rate  |
| **Cross-device**      | All identifiers from linked devices | High match rate   |

<Check>
  Enhanced Conversions are automatically enabled for all [Conversion API integrations](/docs/integrations/overview) that support them. You can disable this feature per integration in your workspace settings.
</Check>

## Automatic enrichment

OneView uses your Identity Graph to automatically include the most complete set of identifiers available:

| Source             | Identifiers Used                                       |
| ------------------ | ------------------------------------------------------ |
| **Identity Graph** | Email, phone, user ID from linked sessions             |
| **Event payload**  | Identifiers sent with the conversion event             |
| **Cross-device**   | Identifiers from other devices linked to the same user |

<Warning>
  Enhanced Conversions require user consent for `ad_user_data` and `ad_personalization`. OneView automatically respects consent and only includes PII when consent is granted.
</Warning>

## Privacy and compliance

OneView automatically hashes all PII using SHA-256 before including it in Enhanced Conversions:

| PII Type         | Hashing        | Storage                   |
| ---------------- | -------------- | ------------------------- |
| **Email**        | SHA-256        | Never stored in plaintext |
| **Phone number** | SHA-256        | Never stored in plaintext |
| **User ID**      | Included as-is | If provided               |

<Check>
  All PII is automatically hashed using SHA-256 before processing or storage. OneView never stores plaintext sensitive data.
</Check>

## Platform support

<Info>
  Platform-specific implementation details vary. OneView automatically adapts Enhanced Conversions to each platform's requirements and API specifications.
</Info>

Check out the [Conversion API integrations](/docs/integrations/overview) page to see which platforms support Enhanced Conversions.

## Common questions

<AccordionGroup>
  <Accordion title="What identifiers are required for Enhanced Conversions?">
    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.
  </Accordion>

  <Accordion title="How does OneView get identifiers for Enhanced Conversions?">
    OneView uses your [Identity Graph](/docs/platform/features/processing/identity-resolution) to automatically enrich conversions with identifiers from:

    * The current event payload
    * Linked sessions and devices
    * Previously connected identifiers

    No manual configuration required.
  </Accordion>

  <Accordion title="Can I disable Enhanced Conversions?">
    Yes. You can disable Enhanced Conversions per integration in your workspace settings under **Settings** → **Accounts** → **\[Platform]** → **PII Handling** → **None**.

    <Warning>
      Disabling Enhanced Conversions reduces match rates, especially when click identifiers are blocked or expired. This may impact campaign optimization accuracy.
    </Warning>
  </Accordion>

  <Accordion title="How does consent affect Enhanced Conversions?">
    Enhanced Conversions require `ad_user_data` consent. OneView automatically:

    * Includes PII only when `ad_user_data` is granted
    * Excludes PII when consent is denied
    * Respects consent settings across all platforms

    No additional configuration needed.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Identity Resolution" icon="users-viewfinder" href="/docs/platform/features/processing/identity-resolution">
    Learn how OneView builds Identity Graphs to enrich Enhanced Conversions.
  </Card>

  <Card title="Consent Enforcement" icon="user-shield" href="/docs/platform/features/collection/consent-enforcement">
    Understand how OneView automatically enforces consent for Enhanced Conversions.
  </Card>
</CardGroup>