Skip to content
Playerly

Matching and metric definitions

Before comparing results, agree sources, time windows, and counting rules. The following is a proposed review structure.

From fields to measurement rules

Event fields, identifier relationships, and result-delivery conditions belong in the same discussion.

Choose a technical review area
Game-event structureField / type / meaning
partner_idstring
Partner context
visitor_idstring
Visitor identifier
game_idstring
Game identifier
event_typestring
Agreed event type
amountnumber
Value under event rules
timestampISO datetime
Event time with timezone

Type semantics, currency, and adjustment rules are agreed during integration.

sourcevisitor_idgame event

A shared identifier needs an attribution rule

Define available identifiers, tag lifetime, and source priority. Account separately for events without an established source connection.

Measurement rules
  1. ResultEvent definition and identifier
  2. DestinationAddress, authentication, and permissions
  3. AcknowledgementResponse, retries, and duplicate handling
Preparing a postback

Connecting a source to a session

Define available identifiers, tag lifetime, priority among multiple sources, and repeat-visit behavior. Cross-device and probabilistic matching are not assumed.

Definitions to agree

Player

A distinct agreed identifier in the selected view, not a verified unique person.

Cohort

Players with a first observed launch in the same period.

W1 return

The player was observed in the first subsequent week. Define whether you use calendar weeks or a rolling window in advance.

GGR

Commonly: stakes minus payouts. Bonus, currency, and adjustment rules must be agreed.

Why results diverge

Reconcile timezone, currency, window, uniqueness rules, and extraction time. Identify unmatched events, duplicates, and incomplete cohorts separately.

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

Book a demo

Explore Playerly through your use case. We’ll message you on Telegram to clarify your goals and agree on a time.

Username of 5+ characters, a t.me link, or a phone number

Data Protection Policy

Protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service.