Program Smart Lists - best practice? | Community
Skip to main content
James_Glavin
James_Glavin
Level 4
October 20, 2014
Solved

Program Smart Lists - best practice?

  • October 20, 2014
  • 3 replies
  • 1851 views

Hi there,

Marketo newbie here! I'm just starting to build programs, specifically email campaigns. It seems to me that you can create a Smart List in one of two ways, either creating a Smart List as a new local asset and then using the 'Member of Smart List' criteria to add this list to a program. Or I could just build the Smart List directly into the program, so it exists within the program, and not as an asset.

Are there any advantages to doing it in one way over another? What is considered best practice for this.

Thanks in advance,

James

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Josh_Hill13
I do the following:
  • Lead Database: lists everyone will use, building blocks
  • Program Smart Lists - lists I will use here only (usually)
  • Email Send - you can build a list here, but I prefer child lists.
I agree with Rob that you should be careful nesting too many smart lists.

3 replies

A
Anonymous
October 20, 2014
Be careful when you start to "nest" smart lists within each other, if only because it substantially increases the time that it takes to run the programs since Marketo is basically having to look inside multiple different "rooms" for the instructions on how to qualify leads for the program.
    Josh_Hill13
    Josh_Hill13Accepted solution
    Level 10
    October 20, 2014
    I do the following:
    • Lead Database: lists everyone will use, building blocks
    • Program Smart Lists - lists I will use here only (usually)
    • Email Send - you can build a list here, but I prefer child lists.
    I agree with Rob that you should be careful nesting too many smart lists.
      James_Glavin
      James_GlavinAuthor
      Level 4
      October 21, 2014
      Great, thank you Rob and Josh - very helpful!
      Terms & ConditionsAccessibility statement

      Loading footer...