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.
- Program Import
1 of 1 people found this helpful
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!
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.
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.
Yes, exactly. Thanks for clarifying, Dan.
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?