linkrunway.
Implementation guide

Your first link starts here.

A short path from a blank workspace to a measurable connection.

Get started
A developer using a laptop while sitting in a yellow chair
The essentials

Start with a workspace and a link to an HTTPS destination. Open it in a browser, inspect the click, then connect a server-verified signup using the signed token from the destination URL.

Before you begin.

  • A LinkRunway deployment and account
  • An HTTPS destination you control
  • A server integration for verified conversions

Create a place for your links.

Open Start for free, create an account, and name your workspace. Keep each client or business in its own workspace.

  • Choose a name your team recognizes.
  • Open Settings to review the attribution model and lookback window.
  • Create a server key in Integrations and save it in your backend’s secret manager.

Make your first connection.

Open Links → Create link. Start with the destination and add only the context you need.

  • Enter a title and an HTTPS destination.
  • Set a source and campaign, such as newsletter and launch-october.
  • Save, copy the short URL, and open it in a real browser.

Follow it to a signup.

An eligible redirect adds lr_token to the destination URL. Pass that token to your authenticated backend at signup. Report the signup once, using the customer ID from your own session.

Server request · replace the placeholders
curl "$LINKRUNWAY_API/v1/track" \
  -H "Authorization: Bearer $LINKRUNWAY_SERVER_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "eventId": "signup_unique_123",
    "type": "SIGNUP",
    "externalUserId": "customer_123",
    "clickToken": "SIGNED_CLICK_TOKEN",
    "consent": true
  }'

See the result.

Open Events and find your signup ID. Review its attribution, then open Analytics to inspect the funnel. A test in your own workspace is real workspace activity; use a dedicated test workspace when you want to keep it separate.

  • Repeat the same signup request: it should return duplicate: true.
  • Open the destination on mobile and desktop.
  • Test expiry and privacy signals before publishing a campaign.

Find the missing connection.

401 from the API

Check the Bearer header, key scope, and whether the key was revoked.

The event exists but is unattributed

Check token validity, consent, click eligibility, event time, and the workspace lookback window.

The custom domain does not resolve

Verify DNS ownership and configure routing and HTTPS with your hosting provider.

Reviewed October 10, 2026 · LinkRunway documentation

A little clarity

Good questions.
Clear answers.

Why did my test not get an attribution token?

Bots, HEAD requests, DNT or GPC signals, and blocked traffic do not receive eligible attribution tokens. Test with a real browser and the consent settings appropriate to your app.

Do I need my own domain immediately?

No. You can use the deployment’s configured short-link host first. Add and verify your own domain when you are ready to configure its DNS and HTTPS routing.

Where do I find API keys?

Open Integrations or Settings in your workspace. An owner can create publishable and server keys. Copy the secret once and store server keys outside client code.

See the platform
Your next chapter

Let’s see where
a little link takes you.

Start for free Explore pricing