welcome email

Forum|Forum|2 years ago
August 11, 2023
1 reply
952 views

Hello

I have set up into the message center a welcome email when user subscribe from the frst time on our website, a call is sent into campaign and triggered a welcoe email message, but I would lke to know what is the best approach to send a reminder after 3 days once the percon open the first email

Regards

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 SatheeskannaK

@rbiri, Reason you're getting this error due to deliveries are by default setup with nms:recipient as target mapping. Update the delivery target mapping in the 'To' section of a delivery with rtevent instead nms:recipient. So whenever you want to send delivery to a different target than the recipient, use a delivery activity with the appropriate target mapping. Usually, message center records won't be on the recipient table.

SatheeskannaK

Community Advisor

@rbiri I would suggest having a separate workflow that uses the query activity and starts with rtevent (Real time event tracking logs) schema to leverage some of the criteria to get the records needed. Example,

Thanks, Sathees

R

rbiriAuthor

Level 3

when I tried that suggested option and query on Real time event tracking logs, as soon as I configure the list to get the event type the display is 0.

On my current config, once you get your regstration confrimation from message center, I have build a wf checking on event history

and I using a filter by status or type

to retrieve the last recipient who get the message

first is it the right way to do it?

and second I should apply a change dimension just after, right?

bcause I keep receiveing an error at the delivery stating that the schema for recipients specified in the transition ('nms:eventHisto') is not compatible with the schema defined in the delivery template ('nms:recipient'), but I have applied the change dimension, thats what I dont understand

SatheeskannaK

Accepted solution

Community Advisor

@rbiri, Reason you're getting this error due to deliveries are by default setup with nms:recipient as target mapping. Update the delivery target mapping in the 'To' section of a delivery with rtevent instead nms:recipient. So whenever you want to send delivery to a different target than the recipient, use a delivery activity with the appropriate target mapping. Usually, message center records won't be on the recipient table.

Thanks, Sathees

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded