Hide text in footer of Suggested Messages sent from Participant Center

Erik Domingo
Erik Domingo
Sixth Anniversary Kudos 2 January 2026 Monthly Challenge Name Dropper
in Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions

Hi all,

I'm looking for a method to hide some of the text added to the footer of emails sent from the Participant Center (that use Suggested Messages as templates). There are links to the participant's personal and team fundraising pages which LO inserts automatically - in our scenario, we're trying to hide the personal page links for just one specific TeamRaiser. Per BB Support, these text strings can only be customized on a system-wide basis.

As a workaround, we've added a redirection on the default personal fundraising page that points to the participant's team page. It functions, but we'd prefer to not have the links on the email messages. Any thoughts?

Thanks in advance!
Erik

Tagged:

Comments

  • Jeremy Reynolds
    Jeremy Reynolds
    Tenth Anniversary Kudos 2 Name Dropper Participant

    @Erik Domingo
    Looks like LO injects its code to the bottom of the S63 tag in the email template, so what if you wrapped your suggested content in a parent container and then targeted everything in the email stationary's CSS?

    email template:

    <style>
    #templateContainer p { display: none }
    #suggestedMsg p { display: block }
    </style>
    <div id="templateContainer">[[S63:3]]</div>

    Then in admin, fill out your suggested content and then inspect the WYSIWYG. Edit the html to wrap everything:

    <div id="suggestedMsg">
    <p>blah</p>
    <p>blah</p>
    <p>blah</p>
    </div>

  • Erik Domingo
    Erik Domingo
    Sixth Anniversary Kudos 2 January 2026 Monthly Challenge Name Dropper

    @Jeremy Reynolds
    This looks it should do the trick - thanks so much!

  • Erik Domingo
    Erik Domingo
    Sixth Anniversary Kudos 2 January 2026 Monthly Challenge Name Dropper

    @Jeremy Reynolds Sorry, I do have a follow-up question - where do we access the email stationery for Suggested Messages?

  • Philip Nawrocki
    Philip Nawrocki
    Tenth Anniversary Kudos 2 Name Dropper Participant

    @Erik Domingo there are two spots Stationery can live. One is under the main menu under Email -> Stationery. Now you will need to know which stationery to look for and you can do that by going to your TeamRaiser (TR) and going to Step 12. Customize Suggested Messages. In the Actions column, click Edit on the message you wish to update. Once the page loads, look at Step 3. Message Stationary. This gives you the name.

    Otherwise, while still in your TR, go to Step 10. Manage Stationary. This will list the Stationaries in the TR.

    You should be able to find the one you need in either of those spots.

    Thanks,

    Phil

  • Erik Domingo
    Erik Domingo
    Sixth Anniversary Kudos 2 January 2026 Monthly Challenge Name Dropper

    @Philip Nawrocki Thanks for the reminders Phil - I don't work with Stationery that often.

    @Jeremy Reynolds Unfortunately, I can't see how to get the needed CSS declaration into the body of the email. As far as I can see, email clients only render inline CSS. Since the text in question is inserted by LO outside of the (Suggested Message) body text, I can't see how to get my CSS into the correct location in the markup. Am I missing something obvious?

  • Jeremy Reynolds
    Jeremy Reynolds
    Tenth Anniversary Kudos 2 Name Dropper Participant

    @Erik Domingo
    It's def not obvious :)

    So, two parts here:

    • User-facing UI - no style added, we're just getting clever to add a wrapper around all of the text (and crossing our fingers that whatever they edit doesn't delete said wrapper).
    • Stationary - CSS to target things outside of our sneaky wrapper and hide it.

    As far as where to put the css, you could do that a couple ways. Email > Stationary > Edit > step 2 should load into the start of the stationary so you can put rules there. As it happens most email programs will respect style tags in the body, even though they aren't supposed to. So your template could have this…

    <style>
    #userContent p { display: none }
    #userContent #showThisStuff p { display: block }
    </style>
    <div id="userContent">[[S63:3]]</div>

    …Then you edit the suggested text in TeamRaiser, using inspector to edit the html and wrap the text in the #showThisStuff div. All the additional content added by PC3 will get hidden by the CSS, but everything in the WYSIWYG should remain.

Categories