Angus_McCann1

Well that's a bummer. Is there maybe any way to game this? This just doesn't seem scalable and seems like a standard thing particularly email marketers would want - if we have a Program that sent out 8 emails, I don't want to pull 8 individual reports (or 1 report per segments, we happen to have ove...

Thanks, Dave! I figured it could be related, but was not necessarily the case. Our emails are a little larger than we would like, but I just wanted some back-up before I ask other users to start changing their processes.

For number 3, we keep subscription information in a custom data object, so I think it wouldn't be too hard, it would just be a matter of running through the cadence to make sure, but even then, that campaign actually extends out a few weeks AFTER expiry, so I wouldn't be too worried.But thank you fo...

Thanks, Kathryn! The reason we use nesting is honestly due to the variety of marketing campaigns we just around single offerings. Without going too in-depth with it, but we might have 3 different departments all promoting different reports with the same name. It sounds silly, but it helps with keepi...

I think the biggest issue we're facing is just conceptualizing the benefit of using an engagement program over, say, a Default program. Which, I'm sorry isn't specific, but I guess what I'm asking is what can an engagement program do than another program cannot?

So the engagement programs we are setting up are:For new Newsletter RegistrantsGoal 1: Get them engaged with our content & marketing emailsnote: NL registrants are not necessarily new to our databaseGoal 2: Get them possibly converted to paid subscribersFor new Paid SubscribersGoal: Get them engaged...

Actually that is exactly my concern, that we are viewing it from a "Eloqua" perspective rather than a "Marketo" one. Your 30 day trial program seems apt for our use case, actually, as we are using it for new subscribers, new newsletter registrants, and similar scenarios - to nurture as a sort.I was ...