Amplitude

Add acquisition context to Amplitude user analysis

Connect attributed users to their campaign and ad network in Amplitude. Compare activation and retention by acquisition source in the charts your product team already uses.

Join 400+ growth teams using Linkrunner.

    • ABCoffee logo
    • Alle logo
    • AugustAI logo
    • Bounce Daily logo
    • Buku Warung logo
    • CraftMyPlate logo
    • Eira Club logo
    • Elefant logo
    • Fold logo
    • Fuaark logo
    • Grapevine logo
    • HashFame logo
    • Hypd logo
    • IPF logo
    • Karobar App logo
    • Kulfi logo
    • Lingopanda logo
    • Matiks logo
    • Meatigo logo
    • Omli Kids logo
    • Playo logo
    • Pocketful logo
    • Richie Club logo
    • Saras logo
    • Shopping logo
    • Sid's Farm logo
    • Stratzy logo
    • Stylezen logo
    • Tal Boss logo
    • The Tatva logo
    • Utsav logo
    • Zave logo
What it does

What lands in Amplitude

Campaign and network properties

lr_campaign (the Linkrunner campaign ID) and lr_ad_network are set through Amplitude's Identify API with $setOnce, so existing values are kept.

Pre-login attribution

Pass your Amplitude device ID with setUserData right after init, or apply attribution in the app with getAttributionData, to tag onboarding events.

Sync for existing users

Sync with Amplitude sends profile updates for users attributed before you connected.

In the dashboard

The Amplitude settings in Linkrunner

Setup

Set up Amplitude in 4 steps

01

Add your API key

Copy the API key from Amplitude Settings, Projects, API Keys, and enter it under Integrations, Amplitude.

02

Match user IDs

Set the same account ID with Amplitude setUserId and Linkrunner signup.

03

Tag early events (optional)

Apply attribution from your app before the first onboarding event if reporting depends on pre-login events.

04

Verify on an event

Group a later event by lr_campaign in a chart, then compare against Linkrunner analytics. A populated profile alone doesn't prove earlier events carry it.

Notes and limits

Worth knowing before you launch

Amplitude doesn't add new user properties to earlier events. An event tracked before the update can show (none) even when the profile has the campaign.

The automatic integration sends the campaign ID, not the campaign name. Map campaignData.name to your own property if you need the name. Mixpanel receives the same two properties.

Sync doesn't rewrite historical events. Use it when you add the integration for existing users. Segments built from campaign data inside Linkrunner live in Audiences.

Frequently asked questions

Review acquisition cohorts in Amplitude

Connect the integration, pass the matching user or device identifier and verify the attribution properties on a test profile.