SOLVED

Deciding whether to import list into database vs local program

Go to solution
Highlighted
Anonymous
Not applicable

Deciding whether to import list into database vs local program

I have  not seen any information on when, where and why to import lists, i.e. List Import folder of Active Marketing Programs, specific Active Marketing Program, like webinar, or the Database.  Logically, I am assuming it's almost hierarchical, like if a list makes sense to be put in a local program, it goes there, otherwise put it in the List Import folder, but then when would one import a list into the database?  Are those lists sort of like global lists , limited to those requiring multiple programs to access and work on them within a campaign? 

Anyway, just checking on my understanding.  Thanks for any insight on this.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Champion Alumni

Re: Deciding whether to import list into database vs local program

Something like that

  • Program Import
    • you almost always want to add a static list to a Program and import to that List.
    • helps with attribution if you care about that
    • keeps lists associated with that activity
  • Lead Database Import
    • rarely useful anymore
    • may be ok if it's a first implementation with a large list
    • may be ok if it's a one col email address for a large list.

View solution in original post

6 REPLIES 6
Highlighted
Level 10 - Champion Alumni

Re: Deciding whether to import list into database vs local program

Something like that

  • Program Import
    • you almost always want to add a static list to a Program and import to that List.
    • helps with attribution if you care about that
    • keeps lists associated with that activity
  • Lead Database Import
    • rarely useful anymore
    • may be ok if it's a first implementation with a large list
    • may be ok if it's a one col email address for a large list.

View solution in original post

Highlighted
Level 6 - Champion Alumni

Re: Deciding whether to import list into database vs local program

Hey Nancy,

Importing into a list in a  program is better because it keeps all things related to the program together. Importing into the database doesn't keep things together. But you can do whatever you want!

Sincerely,

Keith Nyberg

Highlighted
Anonymous
Not applicable

Re: Deciding whether to import list into database vs local program

Hi Nancy,

I agree with both Josh and Keith that importing a list into a program is better. However, it's important to point out that sometimes importing lists can result in the creation of duplicate lead records if the leads that you are importing on the list already exist in your Marketo database. Just something to be cautious of. If it is a list of net new leads though, this shouldn't be an issue.

Highlighted
Level 10 - Champion Alumni

Re: Deciding whether to import list into database vs local program

Courtney - this is true, however the out-of-the-box functionality in Marketo automatically dedupes on email address.  So if you're importing a new list of leads and some of those are already in Marketo (with the same email address), Marketo will update those records with any new/changed data (of course, honoring whatever "block field update" rules you have in place) - and not create a duplicate.

Highlighted
Anonymous
Not applicable

Re: Deciding whether to import list into database vs local program

Yes, exactly. Thanks for clarifying, Dan.

Highlighted
Champion Moderator

Re: Deciding whether to import list into database vs local program

If Marketo automatically de-dupes email addresses (except when dupes are created by the CRM), in what scenario would a dupe be created upon list import?