TeamRaiser Children Registrants

Options
Myla Burns
Myla Burns ✭
Ninth Anniversary
in Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
Hi, 


We are wondering how other organizations (we use BB CRM and Luminate Online with BB's sync utility) handle child registrations in TeamRaiser.  If the parent uses their email address, it causes issues with the sync and duplicates.  However, you need an email address to register.  Dummy addresses cause similar issues.  I'd love to hear if anyone has found a good solution or just general ideas.  Thank you!
Tagged:

Comments

  • Jeremy Reynolds
    Jeremy Reynolds ✭
    Ancient Membership Facilitator 2 Name Dropper Photogenic

    Myla Burns:

    Hi, 


    We are wondering how other organizations (we use BB CRM and Luminate Online with BB's sync utility) handle child registrations in TeamRaiser.  If the parent uses their email address, it causes issues with the sync and duplicates.  However, you need an email address to register.  Dummy addresses cause similar issues.  I'd love to hear if anyone has found a good solution or just general ideas.  Thank you!



    The issue is that you'll occasionally get new parents who want to register as a child, but still receive email and fundraise on his/her behalf. So, we've got a couple-pronged approach:


    CRM-side (Raiser's Edge), anyone under age 16 is automatically added to a "never-solicit" group out of an abundance of caution. Once they become of age, they'll be put back into normal population.


    On the TR side of things, I'm trying something new this year to see if I can't give folks a way to opt out of email directly on children's registrations. Basically, I've added some jQuery that:
    • Watches the year drop-down under date of birth
    • Does the math to figure out if the registrant is underage
    • Makes a "Register without email" checkbox appear next to the email address if you choose something within the last 14 years
    • The checkbox hides the email address field, replacing it randomly generated text string @example.com
    Now, this is experimental, and it remains to be seen if things will need tweaking once we hit race season. Example.com is reserved for testing emails, so it won't hurt our delivery rates or spam reputation if we send messages to those addresses. Here's the code:

      

    Y.use('jquery-noconflict', function() { jQuery(function($){<br/><br/>   var ageLimit = 14;<br/><br/>   // instantiate the checkbox<br/>   $('#cons_email').before(<br/>      '<div style="display: none;" id="hideEmailWrap">'<br/>      + '<label><input type="checkbox"> Register without email</label>' +<br/>      '</div>'<br/>   );<br/><br/>   // compare birth years<br/>   var youthCheck = function(years){<br/>      var selYear = $('#cons_birth_date_YEAR').val();<br/>      var targYear = new Date().getFullYear() - years;<br/>      return selYear >= targYear;  // younger will return "true"<br/>   }<br/><br/>   // email input obfuscator<br/>   var emailHider = function(years){<br/>      if( $('#hideEmailWrap input').prop('checked') && youthCheck(years) ){<br/>         $('#cons_email').val('removeme[[T10:[[S9]]]]@example.com').hide();<br/>      } else {<br/>         if( $('#cons_email').val().substring(0,8) == 'removeme' ){<br/>            $('#cons_email').val('')  // only clear auto-gen'd addresses<br/>         }<br/>         $('#cons_email').show();     // show the field regardless<br/>      }<br/>   };<br/><br/>   // trigger on year change or checkbox click<br/>   $('#cons_birth_date_YEAR, #hideEmailWrap input').on('keyup change', function(){<br/>      emailHider(ageLimit);<br/>      if(youthCheck(ageLimit)){<br/>         $('#hideEmailWrap').show() <br/>         } else { $('#hideEmailWrap').hide() }<br/>   });<br/><br/>});});

    You can also see it in action in the individual registrations at our 2018 Run/Walk site.

Categories