Re: Sending multiple emails to the same person in a campaign, with different content

Anonymous
Not applicable

Sending multiple emails to the same person in a campaign, with different content

Afternoon All,

I have a question pertaining to data in a send.

I have sent an email to (Customers) asking them to fill out a survey.

I am gathering that information, and then uploading it to Marketo for distribution. 

My question is that (Account Executives) have multiple (Customers) that they are responsible for, and if 2 or more customers complete the Survey, then in theory, the (Account Executive) should receive 2 or more emails. 

I know that Marketo de-dupes the list, so I am wondering if this will remove the duplicates, or send multiple times if the content is different.

The (Account Executives) are our customers, so they cannot see our Salesforce database.  so I cannot do the {{SP_Send_Alert_Info}} placeholder which I initially thought would work.  I have resorted to a manual upload of the process, after Salesforce runs, so that I can get the information I needed, using tokens, in the emails I will be distributing to the Account Execs.

Any input or insight is appreciated!

Tags (1)
1 REPLY 1
Andy_Caron3
Level 4 - Champion Alumni

Re: Sending multiple emails to the same person in a campaign, with different content

Hi Anthony,

Couple things here:

An alert will go every time the campaign is triggered (I once had a user learn this the hard way when they set up an Alert off of a Batch campaign, and got over 1k Alerts that the email had been sent, one for each record). The only time you need to worry about dupes in the list is for Send Email flow steps, not for Send Alerts. You really should never be using Marketo to send an email to an inside person, only to send alerts (Unless you're doing an internal marketing campaign). If you're really worried about a lead taking the survey twice and ensuring both Alerts go, you can edit your SC Settings on the Schedule tab so that leads can flow through every time instead of once.

Screen Shot 2017-08-17 at 12.42.19 PM.png

I'm not quite sure I get the full deployment case you're using here, but it sounds like your cadence is something like this:

1) Smart Campaign 1:

     Smart List: Account Name = (### Customer names)

     Flow: Send email w/ survey link

2) Upload survey information

3) Smart Campaign 2:

     Filter: Member of List or Member Program, Status = Responded

     Flow: Send Alert: Send to {{lead.account exec email}}

Does this sound about right?

I've had a similar challenge in the past, if having the data in Marketo is more important than the visualizations you get out of something like a survey monkey (these can always be replicated) here is what I would do to fully automate :

1) Create new fields (one for each survey question)

     Temp_Survey01

     Temp_Survey02

     Temp_Survey03

     etc.

2) Create a LP and form inside the Survey Program

Use your temp fields for your survey questions. Just change the Label and the Field Type to fit your needs. You can always NULL them out later and re-use them.

(Don't forget that you can show a different Display value to the survey taker, than what is in the Store Value in the system)

Screen Shot 2017-08-17 at 12.41.01 PM.png

3) Create a Smart Campaign to update your Account Executive Email Address

4) Send out the link to your new LP

5) Set up a trigger Smart Campaign (you probably won't be able to get a token to work here correctly so skip it and use choices instead)

Trigger: Form is Completed

Flow: Send Alert

               Choice: If email address is: @ (is one of these ###), Send Alert to Account Executive A

               Choice: If email address is: @ (is one of these ###), Send Alert to Account Executive B

               Choice: If email address is: @ (is one of these ###), Send Alert to Account Executive C

               etc

6) if you want, you can also use the {{lead.Temp_Survey01}}, {{lead.Temp_Survey02}} tokens to write into a permanent field to retain all their answers in one place before you NULL them.

Hope this addresses what you were trying to solve for. The question was a little difficult to get into.

Andy Caron