Connect affiliate clicks to the conversions you report

Keep the partner click ID attached to attributed installs and mapped events. Use postback logs to reconcile the conversions your affiliate program receives.

Affiliate traffic
Everflow
S2S clicks
Impressions
Linkrunner
Back to each partner
Install postbacks
Event postbacks
Rejections

Everflow, plus any partner that takes postbacks

Everflow has a native setup. Every other affiliate network or publisher connects through the same S2S flow from its own Linkrunner partner dashboard.

How data moves

The click ID travels all the way to the payout

Clicks carry tid, postbacks return it

The partner's click ID rides on the Linkrunner link, and every install and event postback sends it back so the partner credits the right affiliate.

  1. Clicklinks.yourapp.com/aff-q4?tid=8f2c91ab
  2. Install attributedtid 8f2c91ab matched
  3. Postbackpartner.example.com/postback?tid=8f2c91ab&event=install

Postback logs partners can act on

Every attempt is logged. Installs flagged by fraud rules go to partners with a rejection URL as a notice with reason codes.

PostbacksDelivery log
  • install18:21:07 · transaction_id 8f2c91abDelivered
  • purchase18:20:44 · amount 9.99Delivered
  • install18:19:52 · Click injectionRejected
  • sign_up18:19:30 · event_id 12Delivered

Follow the click ID from partner to conversion

The click ID is the thread that ties a payout to an install. Partners pass it as tid, and Linkrunner returns it as {click_id} and {tid}.

Clicks carry tid

The partner appends a unique tid to every click, plus optional s2, s3 and s4 passthrough values that come back on the postback.

S2S clicks for store-direct traffic

OEM store placements and in-app units that skip the browser report clicks from the partner's server. The API accepts AppsFlyer parameter names.

Impressions for view-through

Partners can report impressions with a device ID. View-through is off by default, set per partner from 1 to 24 hours, and a click always wins.

Postbacks on install, sign-up and mapped events

Installs and sign-ups post back automatically. In-app events go only once you or the partner maps them, with revenue when Send Revenue is on.

Rejections partners can act on

When Fraud Control rejects a conversion, the partner's rejection URL gets reason codes once, and the normal postback isn't called.

Postback logs

Every postback shows as delivered, retrying, failed, not sent, rejected or withheld, with the exact request and the endpoint's response.

A click and its install postback

Macros are lowercase in curly braces and URL-encoded for you. Postbacks are HTTP GET requests from 8.234.94.188 and 8.234.80.204. Tracking links, macros and S2S clicks are covered in the affiliate partner docs.

Click tracking link, after the partner fills its macros
https://track.example.com/?c=OgWmhiSXhG&tid=a1b2c3d4e5&s2=camp_88&s3=pub_4471&gaid=38400000-8cf0-11bd-b23e-10b96e40000d
Install postback template
https://partner.example.com/postback?tid={click_id}&event={event_name}&gaid={gaid}&s2={s2}&click_time={click_time}&install_time={install_time}
What Linkrunner sends
https://partner.example.com/postback?tid=a1b2c3d4e5&event=install&gaid=38400000-8cf0-11bd-b23e-10b96e40000d&s2=camp_88&click_time=1789653202&install_time=1789653349

Frequently asked questions

Reconcile your next affiliate campaign

Connect the partner, map the events and verify the click ID in a test postback before sharing live links.