Profile with multiple push tokens in Adobe Journey Optimizer
When implementing push notifications using Adobe Journey Optimizer (AJO), a common question arises regarding how profiles are managed across multiple devices. Specifically, whether a single profile can have multiple push tokens and if all these tokens can be targeted during a push notification campaign. This article outlines the issue and provides guidance on how AJO handles such scenarios.
Description description
Environment
- Product: Adobe Journey Optimizer (AJO)
- Applicable Features: Push Notification Channel
- Constraints: Requires integration with Adobe Experience Platform (AEP) and Real-time Customer Profile.
Issue/Symptoms
The issue pertains to the ability of AJO to manage push notifications for THOSE who use a mobile app across multiple devices. Key questions include:
- Can a single profile have multiple push tokens associated with it?
- Can all these tokens be targeted simultaneously during a push notification campaign?
- What is the process for synchronizing mobile app data, including push tokens, with AEP?
Resolution resolution
Adobe Journey Optimizer supports targeting profiles with multiple push tokens across various devices. Below are the steps and considerations for implementing this capability:
-
Registration of Branded Mobile App
Begin by registering your branded mobile app (Android or iOS) with Apple’s Push Notification service (APNs) or Google Firebase Cloud Messaging (FCM) messaging services. These services generate unique push tokens that identify specific devices.
-
Synchronization with Real-time Customer Profile
Push tokens generated are passed to Adobe Experience Platform (AEP) and synchronized with the Real-time Customer Profile using an out-of-the-box client SDK integration. -
Personalized Push Payloads
During journey publication, customer profiles that meet journey conditions are qualified to receive personalized push notifications tailored to their preferences and behaviors. -
Internal Push Messaging Delivery Service
Personalized payloads are sent to an internal delivery service within AJO, which validates app credentials before forwarding messages to Apple or Google messaging services for final delivery. -
End-user Push Notification Interactions
End-user interactions with received notifications are captured as Experience Events via SDK integration, enabling tracking and analysis of engagement metrics.
Additional Notes
For scenarios involving external CRM systems:
- It is possible for an external CRM system to send token-related information (e.g., token, timestamp, customer ID) directly to AEP.
- AJO can utilize these externally provided tokens for sending notifications; however, this requires proper synchronization between the external CRM and AEP.