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

# Audience CDP

> Unify player data into profiles you can engage and analyze

<Card title="Audience CDP" icon="chart-line-up" href="https://www.immutable.com/free-demo?utm_source=docs&utm_medium=referral&utm_campaign=audience-overview">
  Contact us for a free demo and onboarding
</Card>

A **customer data platform (CDP)** collects player data from every touchpoint, resolves it into one profile per player, and makes that profile available to activate.

**Audience CDP** is collect → unify → activate. **[Attribution](/docs/products/attribution/overview)** measures which campaigns produced those players—on the same data.

## Built for Steam (and every other store)

Most PC games live or die on **Steam wishlists**. The store gives you a count, not a relationship:

| Steam wishlist alone                 | With Audience CDP                                                                      |
| ------------------------------------ | -------------------------------------------------------------------------------------- |
| Anonymous intent                     | Known players you can message                                                          |
| No email or Telegram reach           | Direct channels via [Engage](/docs/products/audience/engage)                           |
| One launch notification from Valve   | Months of nurture before and after launch                                              |
| No quality signal                    | See who is real vs low-intent traffic                                                  |
| Hard to tie ads to wishlist → player | Same profile for [Attribution](/docs/products/attribution/overview) and in-game events |

The usual pattern: run traffic to a [Funnel Page](/docs/products/attribution/funnel-page) (or your site with the Web SDK), keep wishlists as a parallel store goal, and use Engage so the people you *can* contact still convert when Steam’s email is not enough.

## Why it matters

Without a CDP, each channel keeps a partial view of the player:

| Source            | Partial view                               |
| ----------------- | ------------------------------------------ |
| Steam wishlist    | Intent, zero owned contact                 |
| Marketing site    | Clicks and anonymous sessions              |
| Discord / social  | Community activity, weak game link         |
| In-game telemetry | Behavior after install, weak campaign link |
| CRM spreadsheets  | Stale lists with no live events            |

Audience CDP merges those streams so Engage, Analytics, and webhooks share one definition of each player—and Attribution can credit the right source.

## How it works

Data enters from several sources, becomes one profile graph, then fans out to separate activation products—not a single blurry “activation” bucket.

```mermaid theme={null}
flowchart TB
  subgraph ingest [Ingestion]
    sdk[SDKs and REST API]
    funnel[Funnel Page]
    csv[CSV upload]
  end
  profiles[Unified player profiles]
  sdk --> profiles
  funnel --> profiles
  csv --> profiles
  profiles --> engage[Engage]
  profiles --> analytics[Analytics]
  profiles --> webhooks[Webhooks]
  profiles --> attribution[Attribution]
```

1. **Ingest** — Live events from SDKs, Funnel Page signups, and CSV lists. See [Ingestion](/docs/products/audience/ingestion).
2. **Unify** — Anonymous sessions, logins, Steam and other linked accounts become one profile.
3. **Activate separately** — Message with [Engage](/docs/products/audience/engage), explore with [Analytics](/docs/products/audience/analytics/overview), sync out with [Webhooks](/docs/products/audience/webhooks), measure spend with Attribution.

## In this product

<CardGroup cols={2}>
  <Card title="Ingestion" icon="cloud-arrow-up" href="/docs/products/audience/ingestion">
    How data enters the CDP
  </Card>

  <Card title="Engage" icon="heart-pulse" href="/docs/products/audience/engage">
    Turn wishlists and signups into launch players
  </Card>

  <Card title="Analytics" icon="chart-mixed" href="/docs/products/audience/analytics/overview">
    Quality, funnels, and segments
  </Card>

  <Card title="Webhooks" icon="webhook" href="/docs/products/audience/webhooks">
    Push CDP events to your systems
  </Card>
</CardGroup>

Instrumentation reference (Web, Unity, REST, Data Dictionary) lives under **Attribution** in the sidebar—the same SDKs feed both products.

## Next steps

<CardGroup cols={2}>
  <Card title="Engage" icon="heart-pulse" href="/docs/products/audience/engage">
    Wishlist-to-player messaging
  </Card>

  <Card title="Funnel Page" icon="browser" href="/docs/products/attribution/funnel-page">
    Capture players Steam will not let you contact
  </Card>
</CardGroup>