How measurement works

Review events, matching, and result delivery before a technical discussion.

Book a demo Explore the tour

From fields to measurement rules

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

Choose a technical review areaEvent fieldsMatchingResult delivery

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

ResultEvent definition and identifier
DestinationAddress, authentication, and permissions
AcknowledgementResponse, retries, and duplicate handling

Preparing a postback

Three contracts to agree

Events

What happened, when, in which game, and under which identifier.

Matching

How a source connects to a session and how repeat visits are counted.

Postback

How a result reaches the destination and how retries are handled.

Events Matching and metrics Postbacks

Before the technical discussion

Prepare a data-flow diagram, field inventory, and anonymized example. For a real integration, request an approved specification, environment addresses, authentication method, and support contact.

Integration plan

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

Analyze

Attribute

Act

For game teams

For traffic teams

Find your use case

Explore the product

Work with data

About Playerly