Robert_Villanue

Yep, that's fair. You could replicate that logic in your BI tool but it would be duplication of effort. ... View more

It is extremely dangerous to work with an average of the (indeed already rounded) percentages. In your example each of the three emails has a similar amount of emails delivered, so the two results only differ slightly as expected. But imagine one or two of those emails are sent to roughly 500 instead of 5.000 people? Averaging the three open rate percentages would then give those smaller emails an equal weight in the final result, which is entirely unjustified by the volume sent. For that reason alone I would ALWAYS recommend to use the mathematical approach and take the average based on total delivered and total opens, as the bottom line in your table shows. ... View more

Was it a recent quarter, or a quarter in the past?  " Activities in the activity log are only retained for 25 months"   See this thread: https://nation.marketo.com/t5/Knowledgebase/Storing-Activity-Data-Beyond-Retention-Policy/ta-p/300803 ... View more

Hi Robert   I'm guessing they are email casts, not nested programs that contain the emails? If so then that makes it a little more problematic. With a nested program you can "make people members" of the relevant program to get Marketo to skip that cast. I don't think you can do that with standalone emails. So. Here is what you will need to do. There may be a simpler way but I don't know it....   1. Create a Default type program for each new email you have in the engagement program, nested in the engagement program.  2. Drag your new emails into that program (or if you can't do that, clone the email in).  3. Create a smart campaign in each Default program. Trigger should be "member of engagement program is (your engagement program)". Flow is Send Email, the email in that Default program. 4. Do this for all emails that should be in the engagement program. 5. In the engagement content stream, click "add content", then "Program", and then select the first program you have built. Select the only smart campaign in that program. Do this for all Programs you created, and put them in the order you need.    Now. You will have more flexibility since if you make a person a member of any of those nested programs, when it's time to cast, Marketo will think they have already received it, and skip them and immediately go to the next program.    6. Run a smart list to show everyone who has received the duplicates for Program 1. Eg. If your email is called "welcome email", you probably now have "welcome email" (the original one in the engagement program), "welcome email copy" (the clone you made) and maybe now even "welcome email 3" (to clone it into the default program!). So set up your smart list criteria as "was sent email" and put those three emails in. With the people that are returned, click "select all" in the smart list, then "change program status", select the Default program that corresponds with the email, and change status to "member".  7. Do this for all Default programs. 8. Activate the Default programs.   So. Now you will have everyone who has EVER received the Welcome Email (regardless of ID) with the Program Status of "Member", for that Default program that is in the engagement program. So when Marketo goes to cast, it will skip it. The same logic applies for all other programs if you follow the same steps.   You can read more about this concept here, it's quite powerful: https://nation.marketo.com/t5/Product-Blogs/Building-an-advanced-email-queue-with-Marketo-Engagement/ba-p/242706. Long story short - use Default Programs not Emails in Engagement Programs, you'll be glad you did later!   ... View more

Hi Robert, For this type of scenario, I would recommend using a smart campaign that is triggered when the person is added to the static list. The Flow would have 1 month wait steps in between each email send.  Hope this helps! ... View more

This post will help you ... View more