From traffic source to in-game activity
How a game provider can connect a campaign to acquired players' behavior and identify sources worth testing next.
Start with the campaign-to-player connection
The total number of launches shows activity volume, but it does not explain a particular partner's contribution. To do that, connect the acquisition source to a player and their game events. Record a campaign or partner identifier and check where that connection is retained. An event without a source tag remains part of overall analytics, but cannot automatically be attributed to the chosen campaign.
Look at behavior after the launch
A game launch, a session, spins, and a return answer different questions. The launch shows initial contact, session events describe interaction, and a return helps assess continuing interest. Read them alongside GGR and the selected period. Each metric needs a clear definition: for example, a return rate refers to a specified starting cohort and a completed observation window.
Compare sources under comparable conditions
Two campaigns with similar player counts may differ by game, country, and acquisition period. Start by selecting comparable groups. Then check event completeness and whether the return window has finished. Only then compare activity and retention. Traffic cost and commercial terms remain a separate part of the evaluation: one return metric alone does not describe the full partnership outcome.
Turn an observation into the next question
If one source shows a higher return rate, ask whether the difference repeats in the next cohort and other games. Use the observation to frame the next test rather than treat it as a universal rule. In Playerly, a provider can start with overall activity and explore sources, games, and GEOs. A demo is most useful when it addresses the specific question the team wants to answer.
See which sources bring your players
Explore real-time game analytics and player attribution across acquisition sources in a demo.
Book a demo