Overview
Mobile personalisation covers three display surfaces, and each one has its own integration pattern.
The two mechanisms behind these patterns are: image swap, where the push platform points at a Reelevant link and the image is generated per recipient at display time; and resolve before send, where your push platform asks Reelevant for the content of each notification and injects the values in the message it sends.
Prerequisites
- A published Workflow with a Channel matching the surface: Push Notification Image, In-App Popup, or In-App Inbox.
- A recipient identifier your push platform can inject in the Reelevant link, usually the same identifier used in e-mail campaigns.
- For the resolve-before-send pattern, a Workflow ending with a JSON Template Output Node.
Pattern 1 — Image swap
This is the default and fastest pattern, and it works on all three surfaces.1
Publish the Workflow
Copy the Channel link from the Integration modal.
2
Register the link in the push platform
Use it as the rich media attachment of the notification, or as the image of the in-app scene or notification centre card. Add the recipient identifier as a URL parameter.
3
Keep the copy generic
The notification title and body come from the campaign, not from Reelevant, so the same wording reaches everyone.
mutable-content flag (Apple documentation), Android reads the image field of the notification payload (Firebase Cloud Messaging documentation). Confirm with your push platform which of the two it supports before planning a lock screen visual.
Some push setups send lock screen notifications as plain text only. In that case the personalised visual appears once the person taps through to the notification centre or an in-app scene, and the lock screen itself stays generic.
Pattern 2 — Resolve before send
Use this pattern when the notification text must change per recipient, not only the visual. Your push platform, or the system that triggers the send, requests the personalised values from Reelevant for each recipient and injects them into the notification it sends.
The response contains the fields declared in the JSON Template Output Node, for example a title, a message, and an image link. Your push platform maps those fields onto the notification title, body, and image.
This request happens at send time, for every recipient, so it adds load to your sending window. Batch it as your push platform recommends, and define a fallback for recipients where the Workflow returns no content.