Affiliate Partner Integration

Send Linkrunner your clicks and receive server-to-server postbacks on installs and in-app events

Overview

Linkrunner is a Mobile Measurement Partner (MMP). When you run traffic to an advertiser who uses Linkrunner, the integration works in two directions:

1. You send us clicks. You point your traffic at a Linkrunner tracking link and append your own identifiers (most importantly your click ID). Linkrunner records the click and uses it to attribute installs.
2. We send you postbacks. When an install or a post-install event is attributed to your click, Linkrunner fires a server-to-server postback to your endpoint with the data filled into the macros you define.

Optionally, you can also send us impressions (the ad was shown but not tapped), so Linkrunner can credit an install to your ad view when there is no click. See View-through (optional).

This is the same model used across the industry, so if you have integrated with other MMPs the flow will feel familiar.

New affiliate partner? Start with Getting Started for the full setup checklist.

Your traffic
   │  click  (you append tid + s2/s3/s4 params)
   ▼
Linkrunner tracking link  ──►  install attributed to your click
   │
   │  postback (we fill your macros: click_id, event_name, revenue, ...)
   ▼
Your endpoint

How attribution works

The link between a click and a conversion is your click ID. You generate a unique ID for every click and pass it to Linkrunner on the tracking link as tid. When a conversion is attributed back to that click, Linkrunner returns the same value in the {click_id} and {tid} macros on the postback. You match the postback to your original click using that value.

Pass a unique tid on every click. Without it, Linkrunner cannot echo an identifier back to you on the postback, and you cannot reconcile conversions against your clicks.

View-through (optional)

If you report impressions through S2S impressions, an install with no click can be credited to an impression instead:

• Off by default. The advertiser turns on view-through for your partner account and sets your window, from 1 to 24 hours.
• Device ID only. The impression must carry the installing device's gaid or idfa.
• Clicks always win. An impression is credited only when no click, from any source, can be credited.

The postback carries the tid you sent on the impression, and {touch_type} is impression instead of click, so you can tell view-through installs apart.

What you can receive postbacks for

Conversion	When it fires
Install	A new app install is attributed to your click, or to your impression if you use view-through. Sent automatically.
Signup	The user completes registration, as defined by the advertiser. Sent automatically once a signup postback is set up.
In-app event	A post-install event the advertiser tracks (for example a purchase). Sent only for events that have an event mapping.

In-app events are not sent by default. Linkrunner sends an in-app event only after it is mapped, either by the advertiser (Integrations → your network → Event Mapping) or by you (Event Mapping in your affiliate dashboard). A mapping can rename the event to your goal name and can include revenue.

You provide one postback URL template per conversion you want to receive. See Event mapping for details.

Next steps

Create an affiliate account

Create your workspace and submit it for approval.

Create a campaign link

Create a link from the affiliate dashboard with your template parameters included.

Tracking links

The parameters included in your click tracking links.

Server-to-server clicks

Report clicks from your server when the user goes straight to the store.

Server-to-server impressions

Report ad impressions so installs without a click can be credited to your views.

Postbacks and macros

The macros Linkrunner fills into your postback URLs, with examples.

Event Mapping

Choose which events reach you and what they are called.

Postback Logs

Check whether each conversion reached your endpoint.

Need help? Contact support@linkrunner.io