Unique ID to be picked up from the system schemas for sending SMS via AJO journey messages using contextual attributes

[vikramcl]

Dear Community,

Greetings!

I am trying to send an uniqueID to the 3rd party system for sending the metadata. 

I need one attribute that is to be uniquely generated for each SMS sent via AJO journeys. 
Kindly suggest one attribute from the system schemas / datasets that would help me stitch this ID back to the message feedback event dataset to have a single view of the journey via queries or data distiller jobs. 

Sequence of events: 
1. SMS received from 3rd party system to AJO (This contains the SMS information) (Dataset 1) 
2. SMS delivered to the user and metadata (this contains the uniqueID) sent to 3rd party via AJO. (Message Feedback Dataset / Step Event Dataset stores the journey details) 
3. 3rd party sends the metadata back to AJO (Dataset 3) 

I would need one unique ID to be used in the metadata within the SMS content to stitch back the information to the profile. 
Constraints:
The only identity I am using is loyaltyID and can't use any other identity. 

Need your help. Thanks!  
Vikram C L 

[Mayank_Gandhi]

@vikramcl 

Use messageProfileID from the AJO Message Feedback Event Dataset

• messageProfileID is a unique GUID generated for each message sent to a recipient via a journey (including SMS).
• It exists in the AJO Message Feedback Event dataset and is specifically designed to identify each delivery to a profile.
• You can embed this messageProfileID in your SMS metadata sent to the third-party system.
• When the third-party system returns data to AJO, ensure it includes this messageProfileID, enabling you to stitch together the original send, delivery event, and feedback data even if only the loyaltyID identity is available in the identityMap.