내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

Extract Email content for all the users

Avatar

Level 3

Hi All,

I have an issue

I am using dynamic parameters in my email to fill up the content. The content is coming from querying the database. I am using <%=targetData.information %> to fill the email and sending it to 5 users.

 

Is it anyway possible to get the exact content that was mailed to each user including the content that came from DB ?

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Employee Advisor

Hi @bhaskarc1289447 ,

If you want to get the content of targetData.information after the email has been sent, you can store contexutal data from targetData into the delivery logs by extending the nms:broadlogRcp entity and adding the filed in the nms:recipient Target Mapping (Storage section). You must ensure that the field in targetData will ALWAYS be the one mentioned in the Target Mapping.

For instance let assume you extended nms:broadlogRcp to add a field named "information" of type string of 255. in target Mapping targetData.information will be stored to that field.

In the workflow field targetData.information will be stored however targetData.Information won't, it'scase sensitive...

Denis_Bozonnet_0-1653033447797.png

We got customer that uses such capability to store common element across all their campaigns that they then export to their data warehouse for in-depth insights...

That would also be an alternative

Thanks

Denis

 

 

원본 게시물의 솔루션 보기

4 답변 개

Avatar

Level 4

Hi @bhaskarc1289447 ,

I feel you can try to render this content by capturing the data from "HtmlContent" field attribute in the email delivery schema.

 

Thanks

Avatar

정확한 답변 작성자:
Employee Advisor

Hi @bhaskarc1289447 ,

If you want to get the content of targetData.information after the email has been sent, you can store contexutal data from targetData into the delivery logs by extending the nms:broadlogRcp entity and adding the filed in the nms:recipient Target Mapping (Storage section). You must ensure that the field in targetData will ALWAYS be the one mentioned in the Target Mapping.

For instance let assume you extended nms:broadlogRcp to add a field named "information" of type string of 255. in target Mapping targetData.information will be stored to that field.

In the workflow field targetData.information will be stored however targetData.Information won't, it'scase sensitive...

Denis_Bozonnet_0-1653033447797.png

We got customer that uses such capability to store common element across all their campaigns that they then export to their data warehouse for in-depth insights...

That would also be an alternative

Thanks

Denis

 

 

Avatar

Level 3

@Denis_Bozonnet

@_Manoj_Kumar_ 

 

Thank you for your reply and I think we will adopt that approach.

A small query:

we are using a schema 'vendor' to create the Target Mapping, so 'abc:broadLogVendor' is created. Now if we have to create a field just as you mentioned, can we include the field directly in the schema since it is not a factory - schema or we need to extend the custom 'abc:broadLogVendor' schema. Please suggest

Avatar

Community Advisor

Hello @bhaskarc1289447 

You can directly add the fields in the custom schema.


     Manoj
     Find me on LinkedIn