linkrunway.
Implementation guide

Understand where credit comes from.

Deterministic rules make your reports easier to explain.

Get started
Business professionals discussing a presentation of charts in a meeting room
The essentials

First-touch credits the earliest eligible click. Last-touch credits the most recent eligible click before the event. A lookback window limits both; server-verified identity connects customer events to their eligible touches.

Before you begin.

  • Eligible link clicks
  • Server-verified customer identity
  • A chosen attribution model and lookback window

Start with an eligible click.

A real redirect or SDK resolve can create a click. Bots, HEAD requests, privacy-suppressed traffic, and blocked clicks do not receive eligible credit. A valid signed token proves the click belongs to the workspace; it does not override eligibility.

Connect the person on your server.

When someone signs up, pass their click token and your authenticated customer ID with a server key. LinkRunway stores eligible touchpoints for that customer. A client-supplied ID alone is not trusted identity.

Choose a rule you can explain.

Imagine a customer follows a newsletter on Monday, a partner link on Wednesday, and pays on Friday. If both clicks are inside the window, first-touch selects Monday; last-touch selects Wednesday.

  • Only touches before Friday’s payment are considered.
  • The window is measured against event time, not reporting time.
  • The stored event keeps its chosen click even if you later edit the link or model.

Read the whole picture.

Use the ordered funnel for progression, cohorts for exact-day retention, and LTV for net revenue per acquired customer. Compare cost and revenue only within the same currency. An unattributed payment still contributes to verified revenue.

  • A cohort must be old enough to enter day 7 or day 30 retention.
  • Non-paying customers remain in the LTV denominator.
  • Apple aggregate postbacks are kept separate from identified customer events.

Find the missing connection.

A partner has clicks but no commission

Check whether the payment is verified, its click is eligible, the partner is active, and the amount is positive.

A returning customer has no new credit

Their earlier touch may be outside the window. This is not an unlimited lifetime affiliate policy.

Dashboard numbers differ from provider numbers

Compare event time, timezone, currency, attribution rule, source coverage, and bot filters. Different attribution systems need not select the same source.

Reviewed October 10, 2026 · LinkRunway documentation

A little clarity

Good questions.
Clear answers.

Why is a verified payment unattributed?

The payment can be real while its acquisition source is unknown. Missing, expired, future, privacy-suppressed, or blocked clicks do not qualify for attribution.

Can a click after payment earn credit?

No. The click must occur before the event and inside the lookback window. The time the event is reported does not change that ordering.

Does a settings change rewrite existing events?

No. Stored events preserve the attribution selected when they were ingested. Use a consistent model and window when comparing reporting periods.

See the platform
Your next chapter

Let’s see where
a little link takes you.

Start for free Explore pricing