Different Message IDs in case of Dynamic Content

[HardikJa3]

Currently, In our journey 1 we are sending separate emails to different variants (A,B,C) of customers using different paths of the basis of their variant (A,B,C). And later in the next journey 2 we sending out new emails on the basis of their interaction with previous email (We are tracking interaction for each customer in CJA using message id & action id, as each email action is unique and has a separate path in Journey 1).

Now if we were to, merge all emails into a single email action and enable separate content (fragment) for each variant using dynamic content. Now the message ID (action ID and node ID) will be same for each variants so how can we track the interaction to be utilized for Journey 2.

[SatheeskannaK · Accepted solution]

@HardikJa3

The Execution Metadata helper function allows you to record extra details about the content delivered to a customer. For instance, when setting up dynamic content logic, you can define a key/value pair to track information such as the audience type or the specific content variant (e.g., content variant1, content variant2) the customer received within Journey1. This metadata is recorded in the message feedback event dataset (example screenshot below) and can then be utilized as an audience attribute within Journey2.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalizatio...

[HardikJa3]

Hey @SatheeskannaK A few follow up questions, what will be the placement of the metadata node in the journey, whether it will be before the email node or after the email node?

2) Metadata is an event.. So we need to use in which audience ? Or can we use it in personalisation on email template ?

3) And can an attribute be our key and product as value ?

[HardikJa3]

Hi @SatheeskannaK  Can you please answer these questions if possible ?

[SatheeskannaK]

@HardikJa3 

1) Execution Metadata helper is part of the personalization helper function. It's used at the message (i.e. email) level.

2) Metadata is an event.. So we need to use in which audience ? Or can we use it in personalisation on email template ? -

The helper function must be used in the email template. When its used in the audience is contingent on whether the 'journey2' criteria necessitates this additional metadata.

3) And can an attribute be our key and product as value ?

• key refers to the metadata name - it's just a string you can give as a name
• value is the metadata to persist - you can have contextual product data product (ex. Wristwatch, Smartwatch etc,.) as value.