In This Article:

    Deduplication: Standard Mail and Email

    In This Article:

      Deduplication Information for Standard Mail

      When sending standard mail, some of the deduplication options are listed below.  For example Joe and Sally are married. Joe’s Constituent ID is 1 and Sally’s Constituent ID is 2:

      Constituent ID

      First Name

      Address Line 1

      Address Line 2

      Postal Code

      Spouse ID

      Spouse Address Line 1

      Spouse Address Line 2

      Spouse Postal Code

      1

      Joe

      123 Main St.

       

      15108

      2

      123 Main St.

      Apt 1

      15108

      2

      Sally

      123 Main St.

      Apt 1

      15108

      1

      123 Main St.

       

      15108


      1. If you select the option, "One per Constituent ID" AND “or Spouse ID” then the query results are checked to make sure only one letter is sent to the couple and ALL mailing history checked to make sure only one letter is sent to each couple.  Mail Merge History created for Joe and he is listed as the ‘Master’ recipient in the mailing history Mail Merge History created for Sally, she is not listed as the ‘Master’ recipient
      2. If you select the ONLY the option, "One per Constituent ID" then the query results are checked to make sure only one letter is sent to each  Only mailing history marked Primary (Master) is checked to make sure only one letter is sent to each Constituent ID.    
      3. Mail Merge History created for each constituent with a unique Constituent ID. Mail Merge History created for Joe 
            • If neither “One per Constituent ID” or “or Spouse ID” is selected, then no deduplication checking is done in the query results or on the server and all constituents will receive this mailing.
            • Mail Merge History created for Sally
      1. If only “Address based on Line 1 and Postal Code” is selected, then the query results are checked to make sure only one letter is sent to identical Address Line 1 entries. Only one letter is sent to Joe and Sally.
      2. If “Address based on Line 1 and Postal Code” is selected AND “include Line 2”, then the query results are checked to make sure only one letter is sent to identical Address Line 1 AND Line 2 entries.  Joe and Sally would each receive a letter as Sally’s address is entered with an Address Line 2 and Joe’s is not.      

      Deduplication Information for Email

      1. If you decide to check the "or Spouse ID" checkbox in the Email Merge Options pop-up window, it will only impact another row in the file that has the corresponding Spouse ID.  For example Joe and Sally are married. Joe’s Constituent ID is 1 and Sally’s Constituent ID is 2:      

      Constituent ID

      Email Address

      Spouse ID

      Spouse Email

      1

      joe@hotmail.com

      2

      sally@hotmail.com

      2

      sally@hotmail.com

      1

      joe@hotmail.com

      1. If you ONLY select the option "One per Constituent ID", then an email will be sent to joe@hotmail.com AND sally@hotmail.com.
      2. If you select "One per Constituent ID" AND "or Spouse ID", then only 1 email is sent, and that is to joe@hotmail.com.
      3. This is because when Salsa CRM gets to the second row, it sees Constituent ID = 2, and then checks all previous rows for values in both Constituent ID and Spouse ID columns to look for a match. Salsa CRM sees a match of joe@hotmail.com in the first row.    
      4. If you select only "One per Email Address", then two emails will be sent, one each to joe@hotmail.com AND one to sally@hotmail.com.  
      5. If you select "One per Constituent ID" and "One per Email", two emails will be sent, 1 each to joe@hotmail.com AND sally@hotmail.com.
      6. If you select "One per Constituent ID", "or Spouse ID" and "One per Email", only one email is sent, and that is sent to the first email address, among related spouses, that Salsa CRM encounters, in this example, joe@hotmail.com
      Was this article helpful?
      0 out of 0 found this helpful
      Have more questions? Submit a request

      Comments

      0 comments

      Please sign in to leave a comment.