Extraction vs. List

Hello. I've been in the museum/Tessitura world for 5 weeks now. Recently I did the courses for lists and extractions. 

I'm wondering if you could share how you use lists, versus how you use extractions. What purposes are you using these features for? Thanks in advance.

Parents
  • Lists are faster and easier.  But you get a few of things out of Extractions:

    • There are a large number of tools to help you build customer communication lists with Extractions
    • It is easier to exclude records by using suppressions rows
    • You can segment extractions, which allows you to easily pull different, unrelated groups together, but also to see where they were picked up with the counts
    • Since Extractions run concurrently, you can build really large complicated queries that won't bog down your client for a long time

    One difference between the two to never forget is that Lists automatically screen out Inactive constituent records, while they must be manually suppressed from Extractions.

    You can, of course, use Lists in Extractions (as you can use Lists in other Lists), and you can save Extractions to Lists.

Reply
  • Lists are faster and easier.  But you get a few of things out of Extractions:

    • There are a large number of tools to help you build customer communication lists with Extractions
    • It is easier to exclude records by using suppressions rows
    • You can segment extractions, which allows you to easily pull different, unrelated groups together, but also to see where they were picked up with the counts
    • Since Extractions run concurrently, you can build really large complicated queries that won't bog down your client for a long time

    One difference between the two to never forget is that Lists automatically screen out Inactive constituent records, while they must be manually suppressed from Extractions.

    You can, of course, use Lists in Extractions (as you can use Lists in other Lists), and you can save Extractions to Lists.

Children
No Data