For engagement programs, I typically use a "01 - Add to Stream" smart campaign that is triggered by whatever activity constitutes inclusion, and a "02 - Pause Stream" smart campaign when I want the cadence paused. This is useful for nurture programs with a set cadence where you do not need to track success on a program-level basis.
You can also choose to use smart campaigns in default programs that are embedded into engagement programs. This allows for a bit more sophisticated reporting - reviewing success at each program level. This is only needed if you want to differentiate each email at the program level and track success at different stages of the engagement program.
Liz - using child programs within EPs is how all of our EPs are structured. In addition to some of the benefits mentioned here already (more granular control, able to track program engagement/success at the program level, etc.), it also allows us to prevent content being sent to someone who has already engaged with it. For example, we have individual "website content" programs for every piece of gated content available on our website. If one of our EP emails is promoting content that someone already engaged with (using a filter "member of [website content program]; program status "filled out form" or "engaged/downloaded content"), we can have each cast skip those that meet that filter criteria. The only downside is Marketo doesn't automatically move them to the next cast that they qualify for - instead, they receive nothing and are evaluated once again during the next cast (1 week, 2 weeks, etc.).
Thank you for making the effort to find things that are missing in the Marketo Product Documentation. We realize that not everything is included there, because we are documenting the standard usage, and can't provide guidance on every possible situation. Often, unique customer situations have special requirements.
That being said, we are always eager to improve the docs, which is why we include a "How can we improve this article?" button in every one of our more than 1,300 help articles. Click that and you can send the Docs Team an email with your suggestion. We normally can reply quickly, and this often leads to clarified or additional content.
That handy button is meant for documentation feedback only, not for any kind of Support issue. The Support folks are much better equipped to handle any issues you are having with your instance. However, if we can add something useful to the docs themselves, it may prevent that Support call for you--and others.
That button is quite effective, too. A year or two ago might be a different story, but I've submitted requests to add content and it was live a day or two later -- quite impressive. And all the code style updates have been a big improvement as well. Great points, Steve Schaefer! Keep up the good work!
Thank you Steve, I know its impossible to anticipate every possible question. I wasn't trying to knock Marketo documentation, which is extensive, just noting that for someone new to the product I've run into a several instances where it tells me how to use the product in a step-by-step manner, but not the idea behind it or how it functions.
For instance in this case the documentation clearly explains how to setup success tags/statuses and how to make the various campaigns, but it doesn't really tell you what impact each thing has (such as "success" not actually have a defined result). That is understandable, there is a variable library of documentation as it is, but maybe more click-through to more reading that explain the point and function of different items... Regardless it is on me that I haven't supplied feedback and I will certainly try to do so next time.
Yes, I didn't see your comments as knocking the docs, as much as a chance for us to find a way to get more feedback. I hope you'll supply it as you go. New users are a valuable resource.