Postback contract
Agree which event your system receives, how it verifies the sender, and how it handles repeated delivery.
From fields to measurement rules
Event fields, identifier relationships, and result-delivery conditions belong in the same discussion.
Result structure
Define the identifier used to match a campaign, the event type, and time. Sender and destination must share each field’s meaning. Agree currency and accounting rules for monetary values.
Delivery and retries
Before launch, agree success responses, timeout, retry schedule, and a deduplication key. Receiving the same result twice should not create a duplicate credit in the destination system.
Protecting delivery
Define authentication or signing, secret rotation, and destination restrictions. Do not put player personal data or secrets into public URLs and logs.
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