Measure push notification re-engagement

Use RightLinks in push notifications to bring users back and measure the return as re-engagement.

Push notifications are a great way to bring existing users back into your app, and a RightLink lets you measure that return as re-engagement credited to the push campaign that drove it.

Push works differently from a normal link. You don't set the RightLink as the notification's tap URL — instead you put it inside the notification's custom data, and your app hands it to the AdShift SDK when the user taps. That last part needs a one-time developer setup.

Requires a developer step + push-capable SDK

This flow depends on the AdShift SDK reading the RightLink from your push payload. Your developer integrates this once (see the developer guide). Make sure your app uses an SDK version with push-notification support before relying on push attribution.

How it works

You create a RightLink set up for retargeting.
In your push tool (e.g. Firebase), you add the RightLink to the notification's custom data under an agreed key (for example as_push_link).
When a user taps the push, your app passes the payload to the AdShift SDK, which reads that key, opens the right screen, and runs attribution.
AdShift credits the visit as re-engagement from that push campaign.

Prerequisites

The AdShift SDK integrated with push support, and the developer step done (registering the custom-data key and forwarding the payload). See the developer guide.
A RightLink set up for retargeting (see the onboarding guide).
Re-engagement enabled in your App Settings.

Set up a push re-engagement link

In Engage → RightLink Management, create a link (Custom experience), set a media source and campaign name, and configure Retargeting (turn on Retargeting and Ignore active users for retargeting, set your Re-engagement window).
Set the Deep link value for the screen you want to open.
Copy the link URL.
In your push provider, add the link to the notification's custom data under the key your developer configured (e.g. as_push_link) — not as the notification's destination URL.
Give your developer the key name you used so the SDK reads the right field.
Test on a device that has the app installed: tapping the push should open the app to the right screen.

How the visit is attributed

The user already has the app → their return is credited as re-engagement, not a new install.
It's attributed to your push campaign for the duration of the re-engagement window.
See results under Analyze → Overview with the Retargeting view, filtered by your media source / campaign.

You don't add device IDs to the link — the SDK identifies the device. (Device IDs in the link only matter for paid retargeting through external networks; see the RightLinks overview.)

Troubleshooting

Nothing is attributed — most often the link was set as the notification's tap URL instead of placed in custom data, or the developer step (SDK push integration) isn't in place, or the SDK version doesn't support push yet.
Attributed as a plain open, not re-engagement — check that Retargeting + Ignore active users for retargeting are on for the link, and that re-engagement is enabled in App Settings.
Wrong screen after tapping — the deep link value doesn't match what your app routes on.