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

# Events

> Understanding events - the building blocks of digital marketing measurement.

## What is an Event?

An event is any action a user takes on your website that you want to track. Think of events as the moments that matter in your customer journey.

<Frame caption="Some events can be configured as Conversions">
  <img src="https://mintcdn.com/oneview/TckL7SwEG-laxVz8/platform/concepts/assets/conversion-events.png?fit=max&auto=format&n=TckL7SwEG-laxVz8&q=85&s=9f225b937144046582402d06f7eb8357" alt="Conversion Settings" style={{height: "100%"}} className="rounded-lg" width="1098" height="732" data-path="platform/concepts/assets/conversion-events.png" />
</Frame>

## Examples of Events

<Tabs>
  <Tab title="E-commerce">
    * **View Product** - User looks at a product page
    * **Add to Cart** - User adds item to shopping cart
    * **Purchase** - User completes checkout
    * **Sign Up** - User creates an account
  </Tab>

  <Tab title="B2B">
    * **Download PDF** - User downloads a whitepaper
    * **Book Demo** - User schedules a sales call
    * **Start Trial** - User begins free trial
    * **Subscribe** - User becomes paying customer
  </Tab>

  <Tab title="Media">
    * **Article View** - User reads an article
    * **Video Play** - User starts watching video
    * **Newsletter Signup** - User subscribes to emails
    * **Share** - User shares content
  </Tab>
</Tabs>

## How Events Work

Events flow through OneView's processing pipeline:

| Step                      | Action                                         | OneView Feature                                                                                       |
| ------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **1. Event sent**         | Your website sends event to OneView            | [Cookieless Advertising](/docs/platform/features/collection/cookieless-advertising) stores Click IDs       |
| **2. Consent checked**    | OneView verifies user consent                  | [Consent Enforcement](/docs/platform/features/collection/consent-enforcement) respects consent signals     |
| **3. Identifiers linked** | OneView connects user identifiers              | [Identity Resolution](/docs/platform/features/processing/identity-resolution) enriches with Identity Graph |
| **4. Duplicates blocked** | OneView prevents duplicate processing          | [Deduplication](/docs/platform/features/processing/deduplication) uses idempotency keys                    |
| **5. Conversion sent**    | If configured as conversion, sent to platforms | [Enhanced Conversions](/docs/platform/features/delivery/enhanced-conversions) includes hashed PII          |

<Check>
  OneView automatically processes all events through its pipeline, ensuring accurate tracking, compliance, and delivery without manual configuration.
</Check>

## Event Types

| Event Type           | Description                              | Can Be Conversion? |
| -------------------- | ---------------------------------------- | ------------------ |
| **Page View**        | User views a page                        | ❌ No               |
| **Conversion Event** | User completes a goal (purchase, signup) | ✅ Yes              |
| **Identify Event**   | User is recognized (login, signup)       | Optional           |

<Info>
  **Conversion Events** are events you configure as conversions in your workspace. These are sent to advertising platforms via Conversion API for campaign optimization. Learn more about [Conversions](/docs/platform/concepts/conversions).
</Info>

## Common Questions

<AccordionGroup>
  <Accordion title="How many events should I track?">
    Start with 3-5 key events:

    * Your main conversion (Purchase/Signup)
    * One mid-funnel action (AddToCart/Trial)
    * One top-funnel action (ViewContent)

    Add more as needed, but avoid over-tracking.
  </Accordion>

  <Accordion title="What if users do multiple events?">
    That's normal and good! The customer journey includes multiple events:

    ViewContent → AddToCart → Purchase

    Each event helps platforms understand user behavior. OneView's [Identity Resolution](/docs/platform/features/processing/identity-resolution) connects these events to the same user across devices and sessions.
  </Accordion>

  <Accordion title="Do pageviews count as events?">
    Yes. But you cannot create Conversions out of pageviews. Page views help OneView build your [Identity Graph](/docs/platform/features/processing/identity-resolution) and track user journeys, but only specific events can be configured as conversions.
  </Accordion>

  <Accordion title="What happens if the same event is sent twice?">
    OneView's [Deduplication](/docs/platform/features/processing/deduplication) system automatically prevents duplicate events from being processed using idempotency keys. The same event with the same idempotency key is processed only once.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Conversions" icon="bullseye-arrow" href="/docs/platform/concepts/conversions">
    Learn about conversion events and how OneView processes them.
  </Card>

  <Card title="Sending Events" icon="code" href="/docs/guides/sending-events/overview">
    Start tracking your events with OneView.
  </Card>
</CardGroup>