Engagement Program Question | Community
Skip to main content
Calon_Alpar
Calon_Alpar
Level 2
January 8, 2019
Question

Engagement Program Question

  • January 8, 2019
  • 1 reply
  • 5638 views

Hi Nation,

I have a question regarding setting up an engagement program.

In 2019 we will be launching our first real ongoing nurture programs broken out by general content and then product specific focused. Now my question is around having one engagement program with all the streams or separate engagement programs with one stream. The flow of people will be once they complete the content in the product specific stream, they would move to the general content stream. We definitely want some flexibility between the streams so wondering what's the ideal method?

Thanks in advance for your suggestions.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Victoria_Chu
Victoria_Chu
Level 2
January 8, 2019

What do you mean by wanting flexibility between the streams? Will users be able to move back and fourth between general content and product specific? If so, then I'd recommend using one engagement program with multiple streams. Remember you can only be in one stream in one engagement program but you can be a member of multiple engagement programs.

Calon_Alpar
Calon_AlparAuthor
Level 2
January 8, 2019

Thanks Victoria!

So for the product series streams I believe we would want them to be in one

or shifting from one or the other. But the general content stream we would

want them in both the general stream and a product stream since the content

is complementary.

On Tue, Jan 8, 2019 at 2:48 PM Victoria Chu <marketingnation@marketo.com>

Victoria_Chu
Victoria_Chu
Level 2
January 8, 2019

Got it! In that case I think you should have one engagement program for the product series streams and a separate engagement program for general content stream. Just be careful of your stream transitions and cast times so you don't overwhelm the user.

Terms & ConditionsAccessibility statement

Loading footer...