Skip to main content
Attribution answers which campaigns and channels produced which players and outcomes. It uses the same event stream and profiles as Audience CDP—you instrument once, then measure spend here and activate players in the CDP. For Steam titles, that means going beyond wishlist counts: credit the ads that created Funnel Page signups and, after ship, installs and in-game conversions—not only store wishlists you cannot message.

What you get

Audience CDP vs Attribution

Credit models

Credit paid, organic, influencer, referral, or direct for the signup.
Rank sources by paying and high-engagement players—not raw signup volume.
Example path: ad click → Discord → Funnel Page signup → email → game launch.
Player quality and segments are explored in Audience Analytics; Attribution focuses on source credit and conversion feedback.

Funnel Page

Send measurable traffic to a Funnel Page when you want a Play-hosted landing surface that also ingests into the CDP. For your own marketing site, use the Web SDK below.
  1. Define Conversion Goals.
  2. Connect networks and enable Conversion Postbacks.
  3. Use Hub source quality to exclude low-value traffic and build lookalikes.
  4. Re-engage cold signups with Engage.
Postbacks are server-to-server. No extra browser tags are required after the SDKs and Hub integrations are in place.

Instrument once

Same prerequisites and Web SDK snippets used across Audience and Attribution:

Install

Initialize

Then identify players after login and send game events from Unity or REST as needed.

Web SDK

Sites and web games

Unity SDK

Desktop and mobile Unity builds

REST API

Server-authoritative events

Data Dictionary

Event and attribution schemas

In Hub

Next steps

Funnel Page

Landing surface for measurable traffic

Conversion Goals

Define conversion events

Conversion Postbacks

Feed outcomes to ad networks

Audience CDP

Ingestion, Engage, and Analytics