Use acquisition context in your lifecycle journeys

Q: Which customer engagement platforms does Linkrunner integrate with?

Braze, CleverTap, MoEngage, Netcore and WebEngage. Braze, MoEngage and Netcore receive lr_campaign and lr_ad_network on the user. CleverTap and WebEngage receive an install event with source and campaign.

Q: What is the difference between organic_install and inorganic_install?

inorganic_install means Linkrunner attributed the install to a campaign, with utm_source set to the ad network and utm_campaign to the campaign. organic_install means no campaign was matched, and utm_source is organic.

Q: Can attribution reach the platform before a user signs up?

Yes, where the platform has a device ID. Send the Braze device ID to Linkrunner right after init, or pass the Netcore device GUID. WebEngage uses the install instance ID when no user ID exists yet.

Q: How do I update users who installed before I connected?

Run the sync for Braze, CleverTap, MoEngage or Netcore. It updates profiles after you add credentials or spot a mismatch with Linkrunner's attribution.

Q: Which regions and data centers are supported?

CleverTap: EU, IN, US, SG, SK, ID and UAE. MoEngage: DC-01 to DC-06, read from your dashboard URL. Braze uses your REST endpoint and Netcore your API endpoint.

Connect Linkrunner to Braze, CleverTap, MoEngage, Netcore or WebEngage. Build onboarding and return journeys using the source that brought a user to your app.

Start measuring free Read the docs

Into Linkrunner

Out to every profile

Attributed installcampaign, network

Ad network clickclick ID

Linkrunner

Brazecustom attributes

CleverTapinstall event

MoEngageuser attributes

Netcoreuser attributes

WebEngageinstall event

Into Linkrunner

Attributed install

Ad network click

Linkrunner

Out to every profile

Brazecustom attributes

CleverTapinstall event

MoEngageuser attributes

Netcoreuser attributes

WebEngageinstall event

Five engagement platforms

Use the credentials and matching identifiers required by your platform, as listed in the engagement setup guides. Verify a user profile before turning acquisition-based journeys on. Product analytics tools such as Amplitude and Mixpanel are covered under analytics tools.

How data moves

Acquisition source on the profile, before the first message

Attributes for Braze, MoEngage and Netcore

lr_campaign and lr_ad_network land on the profile, matched on the user ID you already send, so journeys can branch by campaign.

ProfileUser attributes

user_idu_48213
platformandroid
lr_campaign18342
lr_ad_networkMeta

Lands in

An install event for CleverTap and WebEngage

organic_install or inorganic_install lands on the timeline with utm_source and utm_campaign, ready to trigger an onboarding journey.

User u_48213Event timeline

inorganic_install10:42
utm_sourcemetautm_campaigndiwali_sale_androidplatformandroid
Onboarding journey entered10:43
Push opened11:05

What lands on the profile, and how users match

Platform	What Linkrunner sends	Matched on
Braze	lr_campaign and lr_ad_network custom attributes	Your changeUser ID, or the Braze device ID
CleverTap	An organic_install or inorganic_install event with utm_source and utm_campaign	The CleverTap ID from the CleverTap SDK
MoEngage	lr_campaign and lr_ad_network user attributes	Your MoEngage user ID
Netcore	lr_campaign and lr_ad_network user attributes	Your setUserIdentity ID, or the Netcore device GUID
WebEngage	An organic_install or inorganic_install event with utm_source and utm_campaign	Your app user ID, or the install instance ID before sign-up

Match the acquisition source to the right profile

Welcome users by campaign

Start an onboarding journey that matches the ad a user installed from, not a generic one.

Split organic from paid

CleverTap and WebEngage receive an organic or inorganic install event you can segment on directly.

Message before sign-up

Send the Braze device ID right after init, and attribution reaches Braze before the user creates an account.

Retarget with context

Pair segments with Linkrunner deep links so a lapsed user returns to the screen your message talks about. Reinstalls and deep-link re-engagements are re-attributed.