Little things that Marketo documentation doesn't cover. | Community
Skip to main content
Liz_Davalos
Liz_Davalos
New Participant
January 3, 2018
Solved

Little things that Marketo documentation doesn't cover.

  • January 3, 2018
  • 2 replies
  • 5162 views

I've found a few of these so I thought maybe it would be good to have a discussion on holes in documentation. New users have a huge learning curve to tackle and it's easy for us to figure something out the hard way and just keep going. I haven't been writing any of this down, but as I've only been using Marketo for a few months lots of little things keep jumping out at me. For instance I cannot find anything in the documentation that actually says a "success" status for an engagement program means people won't receive any more emails from that program. I'd assume this is the case, but I like to be sure. If anyone can confirm this or knows of any other things like this please share. Tips are also appreciated.

Best answer by JDNelson1

Also, what then is the point of statuses and the success checkbox? Anyone know?


Generally there's a flow step after success that does something else. I have a number of engagement programs that all react with each other. When a person gets flagged as success in my "low intent" campaign, I pause that and move them to another engagement for "high intent"

The system is designed for a variety of different uses. The trick is you need to tell it what success means to you.

2 replies

A
Anonymous
January 4, 2018

Hi, Liz.

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.

Thanks again.

Steve Schaefer

Manager, Documentation

    J
    JDNelson1
    Community Manager
    January 4, 2018

    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!

    J
    JDNelson1
    Community Manager
    January 3, 2018

    I don't believe that is the case - but there are some more details around it that could make it a bit more confusing. For instance, if you're using embedded programs in your engagement, and a person is already associated to that program (success or not) then they will not receive that email.

    Liz_Davalos
    Liz_DavalosAuthor
    New Participant
    January 3, 2018

    Wow, ok, so I have an engagement program that is pushing people to an affiliate site. That means I can't track conversions, but they do send me a list each week of form fill outs. I was planning to have a smart campaign check the list against the EP and set the member status to success if they are in the list. This way I know if someone completed the EP for any reporting I want to do later on. The catch is that they shouldn't get any more emails since they've converted. Any ideas on how I should do this is "success" doesn't stop the emails?

    Liz_Davalos
    Liz_DavalosAuthor
    New Participant
    January 3, 2018

    Also, what then is the point of statuses and the success checkbox? Anyone know?

    Terms & ConditionsAccessibility statement

    Loading footer...