My understanding is that for emails, the Engagement Program checks to see if a person has ever been sent that email before, if they have then it will not be resent.
I believe that what Cathal said is true, as long as it is literally the same email - and not a local clone.
Let me rephrase. I understand the engagement model will not send the same exact same email twice from within a nurture stream.
My question is whether or not there is way to prevent an engagement email that promotes a piece of content from being sent if the same content has already been delivered through a diferent mechanism such as being downloaded directly or through content syndication.
For example, say I run a content syndication deal for whitepapers A, B and C. When someone downloaded any of those three whitepapers, I would want to add them to a nurture stream that included promoting those same whitepapers, but that would skip any nurture emails that promoted a whitepaper that the person had already downloaded.
Make sense? Anyone know the answer to this?
Yes, this is possible. To achieve this you must use programs and program membership. If you have a program that is added leads to the membership when they download content from your website, then you reference this program in the engagement stream, if the lead is a member, it will skip the program and move to the next piece of content.
I have the exact same question as Courtland, but I am having a hard time understanding your response and how you would set this up in Marketo. Would you mind laying it out a little more for me? Would you need to set up a program for each whitepaper?
@Cheryl--I understand how this would be set up, but I guess I dont understand how the stream knows to skip the individuals who are members of the program when we have never told it to skip individuals who members of that program. Does that make sense?
@Andrew - I would love to hear that answer as well. I believe it is a built-in feature of the engagement nurtures. I have tested it and it works, although an answer by Marketo would provide clarity.
Also @Cherly, does the progression status need to be "member" or can it be any status in a program such as "clicked" or "opened".
The streams knows to skip the individuals who have membership b/c we built the system to look for this. This is inherent behavior of a stream.
The program status can be whatever you want it to be.
I have the same need. Can someone please post a screen shot of the solution as I'm having a hard time visualizing it.
Basically, there are about 10 web forms on the website. If someone fills out a form for any of them, we want them to drop into the Engagement Stream that delivers emails promoting content they haven't filled out a form for. So if John fills out a form for Content #3, he won't receive an email that promotes Content #3.
Do we create a new program that houses a bunch of rules? Or a campaign within the engagement program? Or keep the rules inside the individual landing page programs? Something else?
Any limiations around Standard Markto instance?
Again, a picture would be very helpful.
Hi Jeff -
There are different ways to do it, but I ran into a similar problem you are describing and found creating programs for each piece of content to be the best solution. Not only does that allow you to measure your content better, but it allows you to make sure that people do not receive the content twice by using program statuses. Engagement nurtures recognize if the record is already a member of the program, and if they are, they will bypass that program and move to the next
Image #2:House Assets and Smart Campaigns under the program
Image #3: Create a Smart Campaign similar to "Engagement Nurture Email" w/ the smart list of
Image #4: Create a Smart Campaign similar to "Engagement Nurture Email" w/ the flow of
Image #5: Engagement Nurture. Drag your programs in
Hope this helps.
Thanks Taylor, I had a feel it was something like that. I'll try out.
From a management perspective, I really like the idea of keeping everything under one Program. Just wish it were a lot simplier where you could somehow attach a rule to a piece of content.