Push Notification Providers

If you send push notifications through CleverTap, WebEngage, or MoEngage, you can track notification opens in Linkrunner without writing custom push-handling code. You set the campaign link as the notification’s click action in the provider’s dashboard, and your existing handleDeeplink setup does the rest.

Start with Push Notification Tracking if you haven’t yet. You need a Linkrunner campaign link and handleDeeplink implemented in your app before configuring a provider.

How it works with a provider

Create a campaign in the Linkrunner Dashboard and copy its link
In the provider’s campaign composer, set the campaign link as the notification’s click action (each provider calls this something different, see below)
On tap, the OS opens your app with the link and your handleDeeplink listeners pass it to Linkrunner
The open shows up in your campaign analytics

This flow relies on deep linking being set up for your campaign link domain. Without it, tapping the notification opens the browser instead of your app.

Provider setup

CleverTap
WebEngage
MoEngage

When creating a push campaign in CleverTap:

In the What step of the campaign, find the On click, navigate to setting
Select Deep Link/URL and paste your Linkrunner campaign link
Send the campaign as usual

On tap, CleverTap opens the link, your app receives it, and handleDeeplink attributes the open.Using key-value pairs instead: add a custom key-value pair (for example, link = your campaign link) under the campaign’s advanced settings. Then implement CleverTap’s CTPushNotificationListener, read the value from the payload in onNotificationClickedPayloadReceived, and pass it to handleDeeplink:

override fun onNotificationClickedPayloadReceived(payload: HashMap<String, Any>?) {
    val link = payload?.get("link") as? String
    if (link != null) LinkRunner.getInstance().handleDeeplink(link)
}

When creating a push campaign in WebEngage:

In the campaign’s Message step, set the Click Action (primary CTA) to your Linkrunner campaign link
Send the campaign as usual

On tap, WebEngage opens the link, your app receives it, and handleDeeplink attributes the open.Using key-value pairs instead: add a custom key-value pair (for example, link = your campaign link) in the campaign body. Then register a push notification callback, read the value from getCustomData() in the click callback, and pass it to handleDeeplink:

WebEngage.registerPushNotificationCallback(object : PushNotificationCallbacks {
    override fun onPushNotificationClicked(
        context: Context,
        data: PushNotificationData
    ): Boolean {
        val link = data.customData?.getString("link")
        if (link != null) LinkRunner.getInstance().handleDeeplink(link)
        return false // let WebEngage handle the default click action
    }

    // implement the remaining callbacks as no-ops
})

When creating a push campaign in MoEngage:

In Step 2: Messaging, open the Actions tab
Set the default click action to Deep-link to URI and paste your Linkrunner campaign link
Send the campaign as usual

On tap, MoEngage opens the link, your app receives it, and handleDeeplink attributes the open.Using key-value pairs instead: add custom key-value pairs (for example, link = your campaign link) in the campaign. Then extend MoEngage’s PushMessageListener, read the value from the payload in onNotificationClick, and pass it to handleDeeplink:

class CustomPushListener : PushMessageListener() {
    override fun onNotificationClick(activity: Activity, payload: Bundle): Boolean {
        val link = payload.getString("link")
        if (link != null) LinkRunner.getInstance().handleDeeplink(link)
        return false // let MoEngage handle redirection
    }
}

Use one Linkrunner campaign per push campaign so each provider campaign’s opens roll up separately in your analytics.

Other providers

Any provider that supports a click action URL, launch URL, or custom key-value pairs (Firebase, OneSignal, Braze, Netcore, etc.) works the same way. Follow the generic setup in Push Notification Tracking.

Troubleshooting

Tapping the notification opens the browser? Your campaign link domain is not set up for deep linking, so the OS treats it as a web URL. Set up deep linking, or switch to the key-value pair approach. Opens are not showing up in the campaign? Log the value reaching handleDeeplink and confirm it is the exact campaign link. If you use key-value pairs, check the key name matches what your code reads.

Need help? Contact support@linkrunner.io

Getting Started

SDK Guides

Links & Journeys

Analytics

Measurement & Privacy

Remarketing

Billing

Troubleshooting

SDK-less Integration

Push Notification Providers

How it works with a provider

Provider setup

Other providers

Troubleshooting

​How it works with a provider

​Provider setup

​Other providers

​Troubleshooting

How it works with a provider

Provider setup

Other providers

Troubleshooting