Audience CDP

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 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: The usual pattern: run traffic to a 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: 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.

1. Ingest — Live events from SDKs, Funnel Page signups, and CSV lists. See Ingestion.
2. Unify — Anonymous sessions, logins, Steam and other linked accounts become one profile.
3. Activate separately — Message with Engage, explore with Analytics, sync out with Webhooks, measure spend with Attribution.

​

In this product

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

​

Next steps