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

# How OneView Works

> A zero-configuration conversion gateway.

<Frame caption="OneView is a conversion gateway between your website and advertising platforms.">
  <img noZoom src="https://mintcdn.com/oneview/OnD2YHFzehKxxAVW/assets/oneview-schema-simple.png?fit=max&auto=format&n=OnD2YHFzehKxxAVW&q=85&s=8fea06c8771869f13bce11879e9e6abc" alt="Diagram showing website events flowing into OneView, which processes and deduplicates data before sending to Meta, Google, and TikTok APIs." style={{height: "100%"}} className="rounded-lg" width="1328" height="754" data-path="assets/oneview-schema-simple.png" />
</Frame>

OneView is a **full server-side tracking platform** that acts as a conversion gateway between your website and advertising platforms.

Unlike proxy solutions that simply relay events, OneView is a **stateful platform** that handles data collection, compliance, deduplication, and integrations automatically.

## How it works

<Check>
  OneView is **stateful** — it maintains memory and context between requests. This enables capabilities that other solutions cannot provide.
</Check>

OneView processes events through a complete pipeline:

| Stage                | Process                           | Feature                                                                                                                                                                                |
| -------------------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1. Collection**    | Events sent from your website     | [Cookieless Advertising](/docs/platform/features/collection/cookieless-advertising) stores Click IDs in workspace                                                                           |
| **2. Compliance**    | Consent signals verified          | [Consent Enforcement](/docs/platform/features/collection/consent-enforcement) respects user consent                                                                                         |
| **3. Enrichment**    | Identifiers linked across devices | [Identity Resolution](/docs/platform/features/processing/identity-resolution) builds Identity Graph                                                                                         |
| **4. Deduplication** | Duplicate events blocked          | [Deduplication](/docs/platform/features/processing/deduplication) prevents double-counting                                                                                                  |
| **5. Attribution**   | Platform credit determined        | [Merit-Based Routing](/docs/platform/features/processing/merit-based-routing) applies your model                                                                                            |
| **6. Delivery**      | Conversion sent to platform       | [Enhanced Conversions](/docs/platform/features/delivery/enhanced-conversions), [Error Handling](/docs/platform/features/delivery/error-handling), [Retries](/docs/platform/features/delivery/retries) |

## Common questions

<AccordionGroup>
  <Accordion title="What does OneView actually do?">
    OneView acts as an intelligent conversion gateway between your website and the ad platforms you use.

    It collects the events you send, validates and enriches them, removes duplicates, and delivers verified conversions through each platform's official API.

    By providing cleaner, more complete conversion data, OneView improves bidding accuracy and campaign optimization — all without ongoing engineering work.
  </Accordion>

  <Accordion title="How is OneView different from GTM Web?">
    GTM Web runs entirely in the browser and depends on client-side JavaScript execution. This means data collection can be affected by **asynchronous script loading**, **single-page-app routing**, **network latency**, flaky **retry logic**, or **users navigating away** before events finish sending.

    OneView runs server-side, where events are processed deterministically and independently of the user's device or browser.
  </Accordion>

  <Accordion title="How is OneView different from GTM Server-Side?">
    GTM Server-Side is a configurable proxy that forwards events as they arrive.

    OneView is a **stateful platform** — it maintains context between events, automatically enforces consent, retries failed deliveries, and deduplicates conversions.

    The result is higher data quality and zero maintenance — no custom servers, containers, or scripts to manage.

    OneView's stateful architecture enables features that stateless proxy solutions cannot provide:

    | Feature                      | GTM Server-Side                                                                                                                                 | OneView                                                                                                                                               |
    | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
    | **Retry Failed Events**      | ❌ Lose data to network errors                                                                                                                   | ✅ [Automatic retries](/docs/platform/features/delivery/retries)                                                                                            |
    | **Conversion Deduplication** | ❌ No                                                                                                                                            | ✅ [Deduplication](/docs/platform/features/processing/deduplication) + [Merit-based routing](/docs/platform/features/processing/merit-based-routing)             |
    | **Cookieless Advertising**   | ❌ Tag-specific Cookies<br />⚠️ Conversion Linkers<br />⚠️ Cookie Expiration                                                                     | ✅ [Master Cookies](/docs/platform/features/collection/cookieless-advertising)                                                                              |
    | **Consent Enforcement**      | ⚠️ Manual setup                                                                                                                                 | ✅ [Automatic across all platforms](/docs/platform/features/collection/consent-enforcement)                                                                 |
    | **Conversion API**           | ⚠️ Manual config                                                                                                                                | ✅ [Official API Integrations](/docs/integrations/overview)                                                                                                 |
    | **Conversion API Errors**    | ❌ Lose data to API errors                                                                                                                       | ✅ [Contextual Error Handling](/docs/platform/features/delivery/error-handling)                                                                             |
    | **Enhanced Conversions**     | ❌ Only with provided IDs<br />⚠️ Manual hashing                                                                                                 | ✅ [Identity Resolution](/docs/platform/features/processing/identity-resolution) + [Enhanced Conversions](/docs/platform/features/delivery/enhanced-conversions) |
    | **Apple® ITP Compliance**    | ✅ <Tooltip tip="You need to use a reverse proxy or traffic mirroring setup on your website to achieve full ITP compliance.">Available</Tooltip> | ✅ <Tooltip tip="You need to use a reverse proxy or traffic mirroring setup on your website to achieve full ITP compliance.">Available</Tooltip>       |
  </Accordion>

  <Accordion title="How does OneView handle consent and privacy?">
    OneView automatically enforces user consent across all connected ad platforms using [Consent Enforcement](/docs/platform/features/collection/consent-enforcement).

    Only events from users who have granted valid consent are forwarded, ensuring compliance with GDPR and other data protection frameworks.

    Learn more in our [Consent](/docs/platform/compliance/consent) and [GDPR](/docs/platform/compliance/gdpr) articles.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Events" icon="code" href="/docs/platform/concepts/events">
    Learn about events and how OneView processes them.
  </Card>

  <Card title="Conversions" icon="bullseye-arrow" href="/docs/platform/concepts/conversions">
    Understand how conversions are attributed and delivered.
  </Card>
</CardGroup>