WebEngage

Use acquisition events in WebEngage journeys

Send install events to WebEngage with source and campaign fields. Build lifecycle segments using the acquisition context available for each user.

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 WebEngage

Install events

organic_install or inorganic_install lands on the user's event timeline for every attributed install. Segments built from the same campaign data live in Audiences.

Attribution fields

utm_source, utm_campaign, campaign_id, campaign_display_id, ad_network_id, ad_network_code and platform travel in eventData. Cohorts and retention by source also sit in Linkrunner analytics.

No extra SDK code

Events come from the normal Linkrunner install flow. No WebEngage ID needs to be passed to the Linkrunner SDK. CleverTap sends the same install events but needs the CleverTap ID.

In the dashboard

The WebEngage settings in Linkrunner

Setup

Set up WebEngage in 3 steps

01

Copy REST API credentials

In WebEngage, open Data Platform, Integrations, REST API and copy the License Code and the API Key for Team Member.

02

Paste them in Linkrunner

Under Integrations, Analytics, WebEngage, paste both and select your data center: India, Global/US, KSA or Europe (Frankfurt).

03

Sync existing installs

Click Sync with WebEngage to replay installs attributed before you connected. Linkrunner emails you when it's done.

Notes and limits

Worth knowing before you launch

Copy the License Code exactly, including a leading ~ if it has one.

If the wrong data center is selected, WebEngage can reject events even with the right credentials.

The API key is used server-side. Paste it only in the Linkrunner dashboard, never in your app.

If the user ID isn't known at install time, Linkrunner uses the install instance ID as the WebEngage userId. Measure return campaigns separately with retargeting.

Frequently asked questions

Verify acquisition events in WebEngage

Connect the right data centre, check user matching and inspect a test install event before building a journey.