Conversion tracking

A conversion is recorded when a transaction_id from a click is matched to a postback or pixel fire from the advertiser. Integr8 supports three methods: server-to-server postback, image pixel, and clickless postback. This page explains how matching works and helps you pick the right method.

Why it matters

Accurate conversion tracking is the foundation of every payout, every fraud signal, and every report. A misconfigured method silently loses revenue and erodes trust with publishers.

How conversion matching works

1. A publisher clicks your tracking link. Integr8 generates a unique transaction_id.
2. The transaction_id is passed to the advertiser’s destination URL, for example ?clickid={transaction_id}.
3. When the user converts, the advertiser fires a postback to Integr8 with the same transaction_id.
4. Integr8 matches the postback to the original click and records the conversion.

When to use which method

Method	Use when	Trade-off
S2S postback	The advertiser’s system can fire a server-side request on conversion.	Most reliable. Recommended default.
Image pixel	S2S is not available and the advertiser controls the thank-you page HTML.	Requires a custom tracking domain. Vulnerable to ad blockers.
Clickless postback	Conversions have no associated click, for example direct app installs attributed by IDFA.	Loses click-to-conversion attribution. Use only when no click exists.

S2S postback (server-to-server)

The advertiser’s server sends a GET request to your Integr8 postback URL when a conversion occurs. Two URL forms are available.

Global postback URL works with all offers on your account:

1. Go to Offers > Integration Settings.
2. Open the Tracking Links & Postbacks section.
3. Copy the Conversion Global Postback URL.
4. Send the URL to the advertiser to fire on each conversion.

Offer-level postback URL is tied to a single offer:

1. Go to Offers > Offers Management and open the offer.
2. On the General tab, expand the Conversion Tracking card.
3. Copy the postback URL and send it to the advertiser.

The URL format:

https://your.domain.com/?secure=YOUR_TOKEN&transaction_id=REPLACE

Replace REPLACE with the placeholder your advertiser uses for the click ID they received.

Image pixel

Use a 1x1 transparent image tag on the thank-you page when S2S is not available. Requires a custom tracking domain to be configured first.

<img src="https://track.yourdomain.com/pixel?secure=TOKEN&transaction_id=CLICK_ID" width="1" height="1" />

Clickless postback

For conversions with no associated click, use the clickless postback endpoint. Include the publisher and attribution data directly in the request:

Parameter	Description
publisher	Publisher ID
sub_id	Sub-publisher ID
session_time	Timestamp of the session
conversion_ip	User IP at conversion
user_agent	User agent string
revenue	Revenue amount
payout	Publisher payout amount
external_transaction_id	Publisher’s click ID
user_email	Hashed or raw user email

Common pitfalls

• Forgetting to include {transaction_id} in the offer redirect URL. Without it, the advertiser has nothing to pass back.
• Hardcoding the secure token in publisher-shared URLs. The token belongs in postback URLs only.
• Mixing global and offer-level postbacks. Pick one per integration to avoid duplicate conversions.

Related

• Tracking links for the click side of the flow.
• Affiliate postback setup for forwarding conversions to publishers.
• Conversion rejection for marking previously-recorded conversions as rejected.