Standard Suppression

Could anyone who has a standard suppression set up for Extractions share what is on it?  We are planning to set one up and want to make sure we don't miss something important.  Obviously some of it is organization specific depending on our usage of attributes, mail purposes, etc... but just a general idea would be great.  Thanks!

  • Hi Kjersten,

    Here are some of ours that are not totally specific to us.

    Constituency Board
    Constituency Board Former
    Constituency Staff
    Constituency Artist
    Type Non Individuals
    Do Not Solicit Phone
    Do Not Solicit Mail
    Do Not Solicit Email
    Do Not Market Phone
    Do Not Market Mail
    Do Not Market Email
    Do Not Trade Phone
    Do Not Trade Mail
    Inactive Account
    No Phone Number

    Then some various ones to find bad address.

  • Former Member
    Former Member $organization

    I also supress Merged constituents, along with Inactive Account as my #1 supression.  The rest then vary depending on the purpose of the extraction, but those two are my 'essentials'.

  • Hi Emma,

    Thanks for that idea - we hadn't thought of that!  I seem to vaguely remember hearing about this at some point, but can I just make sure I understand correctly?  If I recall, once two records are merged, the original ID (which no longer exists as far as the user interface is concerned) will sometimes pull into lists, so you basically end up with people on your list twice: once with the old ID, and once with the current, active one.  Is that accurate?  We just started doing dupe merging here recently, so I figure I should understand what I'm saying before I tell all my colleagues!

    Thanks!

    Beth



    * * * * *
    All aboard to experience a legendary journey on the world’s most famous ship.  Titanic: The Artifact Exhibition is now open at the Science Museum of Minnesota.   Log on to www.smm.org/titanic today to reserve your boarding pass.

    Be social!  Find the Science Museum on Facebook, Twitter, MySpace and more.  Log on to www.smm.org/social for more information.

    Elizabeth A Varro
    Membership Manager
    Science Museum of Minnesota
    (651) 265-9829

    ----- "Emma Carter" <bounce-emmacarter7724@tessituranetwork.com> wrote:
    | From: "Emma Carter" <bounce-emmacarter7724@tessituranetwork.com>
    | To: bvarro@smm.org
    | Sent: Sunday, October 11, 2009 9:41:50 PM GMT -06:00 US/Canada Central
    | Subject: Re: [Tessitura Marketing Forum] Standard Suppression
    |
    |

    I also supress Merged constituents, along with Inactive Account as my #1 supression.  The rest then vary depending on the purpose of the extraction, but those two are my 'essentials'.

    |
    |

    From: Kjersten Schladetzky <bounce-kjerstenschladetzky7557@tessituranetwork.com>
    | Sent: 9/23/2009 3:08:31 PM
    |

    Could anyone who has a standard suppression set up for Extractions share what is on it?  We are planning to set one up and want to make sure we don't miss something important.  Obviously some of it is organization specific depending on our usage of attributes, mail purposes, etc... but just a general idea would be great.  Thanks!

    |

    |
    | --
    | View this message online at: http://www.tessituranetwork.com/COMMUNITY/forums/p/1227/4385.aspx#4385
    | --
    | This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
  • List Manager is set up not to pull merged constituents, but in extractions, you need to suppress inactives and merged accounts (unless, of course, you want to get them).

    Lucie

    ================================
    Lucie Spieler
    IT Development and Training Manager
    Editor, Season Program
    Florida Grand Opera
    ---------------------------
    8390 NW 25th Street
    Miami, FL 33122-1504

    305-854-1643 x.1521 phone
    305-856-1042 fax
    800-741-1010 ticket office
    lspieler@fgo.org
    www.fgo.org

    P please don't print this e-mail unless you really need to.

    ________________________________

    From: Tessitura Marketing Forum on behalf of Beth Varro
    Sent: Mon 10/12/2009 1:06 PM
    To: Lucie Spieler
    Subject: Re: [Tessitura Marketing Forum] Standard Suppression


    Hi Emma,

    Thanks for that idea - we hadn't thought of that! I seem to vaguely remember hearing about this at some point, but can I just make sure I understand correctly? If I recall, once two records are merged, the original ID (which no longer exists as far as the user interface is concerned) will sometimes pull into lists, so you basically end up with people on your list twice: once with the old ID, and once with the current, active one. Is that accurate? We just started doing dupe merging here recently, so I figure I should understand what I'm saying before I tell all my colleagues!

    Thanks!

    Beth



    * * * * *
    All aboard to experience a legendary journey on the world's most famous ship. Titanic: The Artifact Exhibition is now open at the Science Museum of Minnesota. Log on to www.smm.org/titanic today to reserve your boarding pass.

    Be social! Find the Science Museum on Facebook, Twitter, MySpace and more. Log on to www.smm.org/social for more information.

    Elizabeth A Varro
    Membership Manager
    Science Museum of Minnesota
    (651) 265-9829

    ----- "Emma Carter" wrote:
    | From: "Emma Carter"
    | To: bvarro@smm.org
    | Sent: Sunday, October 11, 2009 9:41:50 PM GMT -06:00 US/Canada Central
    | Subject: Re: [Tessitura Marketing Forum] Standard Suppression
    |
    |

    I also supress Merged constituents, along with Inactive Account as my #1 supression. The rest then vary depending on the purpose of the extraction, but those two are my 'essentials'.

    |
    |

    From: Kjersten Schladetzky
    | Sent: 9/23/2009 3:08:31 PM
    |

    Could anyone who has a standard suppression set up for Extractions share what is on it? We are planning to set one up and want to make sure we don't miss something important. Obviously some of it is organization specific depending on our usage of attributes, mail purposes, etc... but just a general idea would be great. Thanks!

    |

    |
    | --
    | View this message online at: http://www.tessituranetwork.com/COMMUNITY/forums/p/1227/4385.aspx#4385
    | --
    | This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
    ________________________________


    | Spam
    | Not spam
    | Forget previous vote
    |



    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
  • To give a little more background, when two records are merged the delete record is not really deleted but rather the status is changed to Merged. This is the record that exists in the T_CUSTOMER table, which pretty much just holds the N1, N2, and a few audit fields like last update. All the other data in a constituent record is stored in other tables and the ID on that data is changed from the delete record to the keep record. Because of that, it's pretty unlikely a merged ID would end up in an extraction (it wouldn't have any data that would meet your criteria unless you were looking at something like name status) but it never hurts to be safe by suppressing merged records.

    Kevin Sheehan
    Documentation & Learning Resources Specialist
    Tessitura Network
    1 888 643 5778 ext 329 Office
    ksheehan@tessituranetwork.com
  • Hi

    Our standard postal suppressions are:

    Staff members

    Inactive accounts

    Merged accounts

    Customers with 'deceased' flag (in case these have not been inactivated for any reason)

    People with 'Do Not Mail' marked in data protection

    People with our organisations postcode - sometimes this is used for press accounts where we only have an email address

     

    Hope that's helpful

    Siobhan

     

     

  • Thanks Kevin.  That helps alot.  Sounds like something we should throw in just to be safe.

    Unknown said:
    To give a little more background, when two records are merged the delete record is not really deleted but rather the status is changed to Merged. This is the record that exists in the T_CUSTOMER table, which pretty much just holds the N1, N2, and a few audit fields like last update. All the other data in a constituent record is stored in other tables and the ID on that data is changed from the delete record to the keep record. Because of that, it's pretty unlikely a merged ID would end up in an extraction (it wouldn't have any data that would meet your criteria unless you were looking at something like name status) but it never hurts to be safe by suppressing merged records.

    Kevin Sheehan
    Documentation & Learning Resources Specialist
    Tessitura Network
    1 888 643 5778 ext 329 Office
    ksheehan@tessituranetwork.com

  • Sorry, I checked the criteria for our "Inactive Account" suppression and it also checks for merged accounts.

  • Former Member
    Former Member $organization

    We tend to think of our Standard Suppression Extraction as the things we want everyone to think about when they are extracting a list. Our Standard Suppression's are extrememly similar to the ones Ryan listed for ACT as well as a segment for Subscribers and Minors.

    Not that we always suppress Subs but that we want people to stop and think about whether they are mailing to Subs or not, as a lot of our mailing and email messaging is based on whether we are sending to Subs or STBS.