AJO - Push Notification Issue

[SherinJo1]

I am working on a POC for push notifications in AJO for an app that is still under development.

For the test, profiles are ingested from a CSV file containing first name, last name, email, appID, platform, device token (captured from the app).

An Individual Profile schema (profile enabled) is used, with email as the primary identifier.
The device token from the CSV is mapped to the schema path pushNotificationDetails.token using the standard Push Notification Details field group.

An audience is created based on email, and a journey is built to:

• Read the audience
• Send a push notification

Issue observed:

Push notification is not sent, even though deviceToken is mapped and visible under identityMap along with email, the journey fails with “No token found in profile”.
Note: Push credentials are configured correctly (we can successfully send push via Postman using the same device tokens).
Kindly suggest how to resolve this and why AJO is unable to recognise the token.

[Mayank_Gandhi]

@SherinJo1 

AJO expects the device token to be specifically mapped according to its standard field group(https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/push/push-config/push-co...)

The field group also expects other attributes (like platform, appId, etc.) be present as part of pushNotificationDetails.

If the token is shown only in identityMap, AJO will not extract it automatically for push delivery.

1. Go to your profile schema in Experience Platform.
2. Check mapping of CSV ingestion.
   • Confirm all push notification fields are landed under pushNotificationDetails.
3. Open a profile record in AJO UI.
   • View raw JSON.
   • Confirm pushNotificationDetails section with token, platform, appId.
4. Review audience conditions and modify so that only profiles with populated push notification fields are included.
5. Test journey again.