Expand my Community achievements bar.

Join our product experts for a live Ask Me Anything on November 12th at 8 AM PT about Experiences & Efficiency with AEP Agent Orchestrator & How Agentic AI is Fueling Smarter Testing and Growth!

messageProfileID missing for Push Tracking

Avatar

Level 5

Hi team,


In Dataset "ajo_push_tracking_experience_event_dataset" we don't have any data being populated for the field "_experience.customerJourneyManagement.messageProfile.messageProfileID"


While for Dataset "ajo_email_tracking_experience_event_dataset" and "ajo_message_feedback_event_dataset" we have messageProfileID field being populated.

 

Whan can be happening? Thanks.

If no messageProfileID for Push Tracking, what field can I use to join delivery logs and tracking logs for push?

1 Reply

Avatar

Community Advisor

Hi @Silvio6 ,

 

You should first check what tracking data is being sent back from your mobile app to Adobe Experience Platform (AEP).

Normally, the app should send a tracking event that includes fields such as the messageProfileID.

If this field is missing, it might mean the mobile SDK is not sending the complete tracking payload.
You can manually configure push tracking in your app code using the following method:

Messaging.addPushTrackingDetails(intent, remoteMessage.getMessageId(), remoteMessage.getData());

Adobe provides an official documentation reference for this setup here:
https://developer.adobe.com/client-sdks/edge/adobe-journey-optimizer/push-notification/android/manua...

 

There’s also an Adobe Debugging/Assurance application https://experienceleague.adobe.com/en/docs/experience-platform/assurance/home?utm_source=chatgpt.com

 that you can use to inspect and verify which events are being sent from your mobile app to AEP.
Use it to confirm whether the tracking event includes the messageProfileID or other message identifiers.

This tracking data is used by AJO mainly for reporting and grouping purposes.
If the messageProfileID is still missing even after verifying the SDK events, it could mean either:

  1. The mobile SDK isn’t sending it, or

  2. Adobe Journey Optimizer doesn’t currently support populating that field for push tracking events.

In that case, check your mobile SDK implementation and confirm with Adobe support whether this field is expected for push messages in your specific setup.

 

Hope it will help you.

 

Kr,

Parvesh

 

Parvesh Parmar – Adobe Community Advisor
https://www.linkedin.com/in/parvesh-parmar/