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.
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.
lr_campaign (the Linkrunner campaign ID) and lr_ad_network are set through Amplitude's Identify API with $setOnce, so existing values are kept.
Pass your Amplitude device ID with setUserData right after init, or apply attribution in the app with getAttributionData, to tag onboarding events.
Sync with Amplitude sends profile updates for users attributed before you connected.
Copy the API key from Amplitude Settings, Projects, API Keys, and enter it under Integrations, Amplitude.
Set the same account ID with Amplitude setUserId and Linkrunner signup.
Apply attribution from your app before the first onboarding event if reporting depends on pre-login events.
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.
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.
Connect the integration, pass the matching user or device identifier and verify the attribution properties on a test profile.