Turing off required unique email for an event to cut down on duplicate emails in system

Options
Hi, 


Does anyone have any thoughts/experience with turning off required unique email in TeamRaiser to cut down on duplicate emails? I debating if I should suggest it to my team for this year's race. 


Thanks. 
Tagged:

Comments

  • Hi Alicia,

    We just had a conference call this morning about the same issue. We currently follow standard protocol with Luminate and have the duplicate email constraint turned on, but this caused many issues last year with our TeamRaiser for our front-end users. We are considering turning it off -- which will allow registrants (specifically spouses who share the same email) to register for a TeamRaiser with the same email. If we do, we would like to know what impact this will have on the database. We also use RELO, and a decision to allow duplicate emails will surely have an impact on our data in RE as well.

    If you can share any insights, it would be most helpful.

    Thanks!

     
  • We allow duplicate emails when registering for Teamraiser. We use Omatic now, and the ancient Connector for DataSync before that, and didn't have any problems. RE doesn't care about duplicate email addresses. Email is not used as a unique key anywhere. This helped us eliminate those deliberately fake email addresses for kid registrations, which allows us to send notices, etc. to the secondary registrants 'in care of' the parent registration.


    However this will not cut down on duplicate emailings, if that was your goal. Some systems will allows you to automatically NOT send to the same email address twice. But Luminate will send an email to every constituent you target regardless of whether that email address already appears in the same list. (I get about 20 copies of each coaching email from all of my test registrations.)


    So our Participant gets a coaching email directed to her, AND another two addressed to her kids who she registered using her email address.


    There is no way to stop that, aside from the constituent unsubscribing on some of them. (I suppose you could create a do-not-send group with everyone under XX age, but that will suppress ALL those minor constituents - not just the ones with shared email addresses.)


    Blackbaud's position on this is that your cons asked to make two records using the same email, so they send to those two records as requested.


    Another thing to be aware of is the setting choices. You can forbid duplicate email addresses everywhere, ALLOW them everywhere (which you probably don't want) or allow them during TR registrations only. However, the latter allows them only during a primary-with-secondaries registration process. You can register yourself and your kids in one transaction using the same email, but you can't come back later and register a third kid using that now in-use email address.


    Additionally, the primary registrant will still need to log-in before registering if their email address has been used in the past, even though you allow duplicates in teamraiser.


    BPM

Categories