Site map
Explore the Playerly platform, solutions, resources, and documents. Choose a section to find the answer you need.
Platform
- Player analytics and attribution/platform/
- Attribute players to traffic sources/platform/tracking/
- Real-time analytics across your games/platform/analytics/
- Notice changes sooner/platform/alerts/
- Send the result back to the source/platform/postbacks/
- Connect the game and the source/integrations/
- Provider integration/integrations/provider/
- Tracker and postback review/integrations/trackers/
- Explore player analytics and attribution/demo/
Solutions
Resources
- Playerly analysis guides/customers/
- How to compare retention by source/customers/provider-scenario/
- From campaign to transparent partnership/customers/buyer-scenario/
- Choose the measurement layer you need/compare/
- Playerly and operator reports/compare/operator-reports/
- Playerly and affiliate trackers/compare/buyer-trackers/
- Playerly and in-house BI/compare/in-house-bi/
- Playerly blog/blog/
- From traffic source to in-game activity/blog/player-attribution/
- Additional traffic monetization: where to start/blog/traffic-monetization/
- How measurement works/docs/
- Game-session events/docs/events/
- Matching and metric definitions/docs/attribution/
- Postback contract/docs/postbacks/
- A shared language for measurement/glossary/
- Compare comparable groups/benchmarks/
- Platform changes/changelog/
Company
Legal
Find your starting point
For providers: player analytics, attribution, and source evaluation. For affiliates: traffic contribution and provider collaboration. For technical teams: events, integrations, and measurement methodology.
Data and documents
Review data handling in the trust, security, and legal sections. Every page includes language switching and a way to contact the Playerly team.