Provider
Game event source, test environment, and session identifiers.
Connect the game and the source
Integration starts with available events, identifiers, and the system that should receive the result.
PlayerlyWorkspaceFrom an event to the full picture
Game eventspartner_id · visitor_id · game_id
PlayerlyData matchingResult analysisGame · partner · period
Game event inspection
Select a row to inspect its fields14:32:06.108betvisitor-172.00
- partner_id
- partner-01
- game_id
- game-04
- visitor_id
- visitor-17
- event_type
- bet
- amount
- 2.00
- timestamp
- 2026-10-18T14:32:06.108Z
14:32:05.842winvisitor-094.50
- partner_id
- partner-01
- game_id
- game-04
- visitor_id
- visitor-09
- event_type
- win
- amount
- 4.50
- timestamp
- 2026-10-18T14:32:05.842Z
14:32:05.217betvisitor-171.00
- partner_id
- partner-01
- game_id
- game-04
- visitor_id
- visitor-17
- event_type
- bet
- amount
- 1.00
- timestamp
- 2026-10-18T14:32:05.217Z
Event semantics, currency, and duplicate handling are agreed before launch.
Two integration paths
Tracker or advertising system
Original tag, result format, and delivery acknowledgement.
Integration for your system
Tell us about your game event source and traffic management system. The Playerly team will review available identifiers, the exchange format, and your integration use case.
What to bring to the discussion
Prepare the player journey, available identifiers, an anonymized event example, and destination requirements. These help define the integration approach and pilot scope.
Explore your goals with Playerly
Explore the right scenario for your games or traffic sources: player analytics, attribution, and collaboration between providers and affiliates.
Book a demo