Email personalization field from 1..N linked resource (Campaign Standard) | Community
Skip to main content
Kornel_Keseru
Kornel_Keseru
Level 3
October 4, 2017
Solved

Email personalization field from 1..N linked resource (Campaign Standard)

  • October 4, 2017
  • 1 reply
  • 1591 views

Hi,

I have a 1 to N relationship between Profile and CustomResource. So each Profile can have one or more matching rows in CustomResource.

I would like to send an email to profiles that have a specific row in CustomResource, and I want to use fields from CustomResource in the email for personalization.

Executing a query inside an Email delivery on CustomResource will give me the matching rows, and each row will identify a unique profile (via the link to Profile). However the CustomResource is not a right schema for the email delivery because we need email, blacklist parameters, etc. that are all part of Profile.

My understanding is that in this case I have to create a new Target mapping based on CustomResource and configure the link to Profile inside the target mapping, so that ACS will know how to find out the email, blacklist parameter, etc. but still I have the already filtered out rows of CustomResource available for email personalization.

I can implement the use case above with workflows (query and email delivery steps) without custom target mapping, but I want to make it simple and use just an email delivery template; no workflow involved.

Can someone please confirm that custom target mapping is the right tool for implementing the use case above?

Thanks,

Kornél

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by florentlb

Hi,

From what I understand, you are still able keep the Profiles dimension as main targeting dimension of your query, and to filter data on the related tables. For example on delivery logs, "Profiles for which delivery logs exist such as delivery = dlv123" is something you can do from a query. If you have other 1-N resources like the log table, even custom, you should be able to do the same.

In my example above, the targeting dimension is Profiles, and I can see in the Explorer the 1-N tables, allowing me to specify some more filters.

Hope this helps,

Florent

1 reply

florentlb
florentlbAccepted solution
Level 10
October 10, 2017

Hi,

From what I understand, you are still able keep the Profiles dimension as main targeting dimension of your query, and to filter data on the related tables. For example on delivery logs, "Profiles for which delivery logs exist such as delivery = dlv123" is something you can do from a query. If you have other 1-N resources like the log table, even custom, you should be able to do the same.

In my example above, the targeting dimension is Profiles, and I can see in the Explorer the 1-N tables, allowing me to specify some more filters.

Hope this helps,

Florent

Terms & ConditionsAccessibility statement

Loading footer...