Skip to main content
Linkrunner integrates with WebEngage to automatically send install attribution events, helping you understand which campaigns are driving user acquisition and engagement.

​
How it works

Every time an install is attributed by Linkrunner, we send an event to WebEngage’s Events API. Linkrunner sends one of two event names: The event carries these attribution fields in eventData: Linkrunner uses your app user ID when it is available. If the user ID is not available at install time, Linkrunner uses the install instance ID as the WebEngage userId so the install event is still captured.

​
Example

  • User came from a Meta campaign named Summer_Sale
  • In WebEngage, that user’s profile receives an inorganic_install event with utm_source set to meta and utm_campaign set to Summer_Sale
  • An unattributed install instead receives an organic_install event with utm_source set to organic

​
Prerequisites

​
Steps to set up

1

Copy REST API credentials from WebEngage

In WebEngage, copy the REST API credentials that Linkrunner needs to send install attribution events.
  1. Log in to your WebEngage dashboard
  2. Open Data Platform > Integrations > REST API
WebEngage dashboard sidebar showing Data Platform, Integrations, and the REST API View action
  1. In Project Credentials, click Show if the key is hidden
  2. Copy the License Code
  3. Copy the API Key for Team Member
  4. Confirm the data center used by your WebEngage account
WebEngage REST API screen showing Project Credentials with License Code and API Key for Team Member
Copy the License Code exactly as WebEngage shows it. If your license code includes a leading ~, include it in Linkrunner as well.
2

Paste credentials in Linkrunner

Add the WebEngage credentials to the Linkrunner project that owns your app.
  1. In Linkrunner, navigate to Integrations from the left-hand panel
  2. Under Analytics, select WebEngage
  3. Paste the WebEngage License Code into WebEngage License Code
  4. Paste the WebEngage API Key for Team Member into WebEngage API Key
  5. Select the matching Data Center Region
  6. Click Save
Linkrunner WebEngage integration drawer showing where to paste License Code, API Key, and Data Center Region
The WebEngage API Key is used by Linkrunner server-side and should be pasted only in the Linkrunner dashboard, not in your mobile app.
3

Select the matching data center

Select the WebEngage data center that matches your account. This controls the WebEngage API host Linkrunner sends events to.
If the wrong data center is selected, WebEngage can reject events even when the License Code and API key are correct.
4

Sync existing attributed installs

If you connected WebEngage after Linkrunner already attributed installs for this project, click Sync with WebEngage in the WebEngage integration screen.Linkrunner replays the eligible attributed install events to WebEngage and emails you when the sync is complete.
5

Install the Linkrunner SDK

WebEngage install attribution events are triggered from the normal Linkrunner install flow. No separate WebEngage ID needs to be passed to the Linkrunner SDK.
Important: Make sure your app calls the Linkrunner SDK initialization flow after install. Linkrunner uses that install data to determine whether the install is organic or inorganic before sending the WebEngage event.

​
Viewing Attribution Data

After the integration is complete and Linkrunner has sent install attribution events, you can view them in WebEngage:
  1. Navigate to a user profile in the WebEngage dashboard
  2. Look for the user’s event timeline
  3. You’ll see an organic_install or inorganic_install event with the attribution fields described above
For aggregate visibility, open Analytics > Events in WebEngage, add/select organic_install or inorganic_install, and view occurrences over time. WebEngage Event Analytics screen showing the inorganic_install event selected This data can be used to:
  • Create segments based on acquisition source
  • Trigger journeys based on organic or inorganic installs
  • Personalize messaging based on campaign origin
  • Analyze user behavior by acquisition channel