User attributes
lr_campaign and lr_ad_network appear in the user attributes of each attributed Netcore profile. Segments built from the same campaign data live in Audiences.
Netcore
Add campaign context to Netcore user profiles
Connect app attribution to Netcore so lifecycle teams can segment users by the campaign and network that acquired them. Match profiles using your configured identifiers.
Join 400+ growth teams using Linkrunner.
What it does
What lands in Netcore
Matched on your identity
Linkrunner matches on the ID you set with setUserIdentity, or on the Netcore device GUID if you don't use it.
Sync for existing users
Sync with Netcore updates profiles after you add credentials or spot discrepancies.
In the dashboard
The Netcore settings in Linkrunner
Setup
Set up Netcore in 3 steps
01
Get your API key and endpoint
Copy the API key and API endpoint from Netcore, following Netcore's getting started guide.
02
Configure in Linkrunner
Enter both under Integrations, Analytics, Netcore.
03
Pass the identifier
Send your setUserIdentity ID to Linkrunner signup, or pass netcoreDeviceGuid. WebEngage needs no ID at all.
Notes and limits
Worth knowing before you launch
Send the Netcore device GUID with setUserData right after init and attribution reaches Netcore before signup. Review cohorts and retention by source in Linkrunner analytics.
Works for iOS and Android apps with the Linkrunner SDK. Measure return campaigns separately with retargeting.
Frequently asked questions
What does Linkrunner send to Netcore?
How does Linkrunner match users in Netcore?
Can attribution reach Netcore before the user signs up?
Verify acquisition context in Netcore
Configure the endpoint and matching identifier, then inspect a test profile before using campaign attributes in messaging.