Skip to content

Postback types

A postback is an HTTP request that Integr8 fires to a publisher’s system when a tracked action occurs. There are three postback types, one for each trackable action in the platform. This page explains what each does and the order they fire in.

The three types

Section titled “The three types”
Type When it fires Use case
Conversions When the advertiser fires an approved conversion postback CPA, CPL, CPS campaigns where the publisher gets credit
Paid Clicks (CPC) When a publisher’s tracking link is clicked CPC campaigns, click confirmation for fraud systems
Events When a post-conversion event is recorded In-app events, secondary purchases, LTV tracking

A Conversion postback must be received before any Event postback can fire. There is no standalone event postback; events always follow a conversion.

How postbacks sequence

Section titled “How postbacks sequence”
  1. The publisher’s user clicks the tracking link. Integr8 generates a transaction_id.
  2. The transaction_id is passed to the advertiser’s landing page.
  3. The advertiser fires a conversion postback to Integr8 with the transaction_id.
  4. Integr8 fires a Conversion postback to the publisher’s system.
  5. If the user triggers additional events (for example, an in-app purchase), the advertiser fires event postbacks.
  6. Integr8 fires Event postbacks to the publisher for each event.

Common pitfalls

Section titled “Common pitfalls”
  • Configuring an event postback with no upstream conversion. Events without a parent conversion never fire.
  • Forwarding rejected conversions when the publisher only wants approved. Set the Firing Status filter when configuring the postback.
  • Mixing postback types in one configuration. Each postback URL handles exactly one type.
Section titled “Related”