S48 Tag in TeamRaiser Stationery

Hi Hillary,


Don't think it will work at Stationary level, but you can always put it inside of the message body itself. The S48 works there and we have been using it that way so far (creating user's dashboard at the bottom of the coaching email message)


Also, the monetary amount (i.e. goal, raised etc) will work only on Live email not preview.


regards,

Daniel


 

Yup, we are at moment using it for Coaching Emails, as well as AutoResponder of a Teamraiser  -- for example here are some of the following stats:


Emails Sent: [[E48:[[S42:XXXX:fr-id]]:emails-sent]]

I've Raised: [[E48:[[S42:XXXX:fr-id]]:dollars]]

My Goal: [[E48:[[S42:XXXX:fr-id]]:goal]]


The "XXXX" placeholder on our case is the FRID of the Blueprint Teamraisers that gets automatically converted into FRID of those children. I noticed that you are using "0" instead (which should be ok to achieve the same dynamically retrieve the associated FRID -- could that be it's no longer working?  How about try the format above, if you are not on a blueprint, you can change that XXXX with actual FRIDs of your teamraiser.


EDIT - ADD ON NOTE:

the E48 is actually the same as S48 -- in CLO you use E for the outer S-tag when you are nesting multiple S-tags

<td><p>[[S48:0pct-of-goal]]</p></td>


Typo.


Have you tried actually sending the email? I think these probably won't work doing a preview or test send. Also try hard coding the FR_ID.


You can also put [[S48:help]] in the email. That should render the valid settings for the module that is hosting the tag.

Brian Mucha:

<td><p>[[S48:0pct-of-goal]]</p></td>


Typo.


Have you tried actually sending the email? I think these probably won't work doing a preview or test send. Also try hard coding the FR_ID.


You can also put [[S48:help]] in the email. That should render the valid settings for the module that is hosting the tag.

Brian Mucha:

including the very existence of S42 tag with that fr-id parameter just to get fr-id parameter that we are actually already been passing.. logically just doesn't make sense

I always guessed that you would sometimes use [[S42:0:fr-id]] to get the id actual value, which you might need to call APIs and such.

 

"The same stationary always returns null if we use it for email campaigns or coaching emails."


The 0 wildcard will always fail outside of the Teamraiser itself. It just means "just use the FR_ID of whichever Teamraiser I'm in". But in broadcast email, that tag isn't in any TR. Should work for coaching, I think.


One thing we do is stick the FR_ID into a session variable using [[U0:myid=1234]].


You can then consume it like this:  [[E42:[[S80:myid]]:TITLE]]


We do definitely use [[S42:0:TITLE]] in Teamraiser AR messages all the time, and I haven't heard of a problem.

"I've had a ticket in with support for over a month on this issue..."


Call your account manager and get them to start pushing support on your behalf. I've had to do that repeatedly. Their job is to advocate for you.

Yep, you can set session variables in email. We use that a lot.


One thing we do is set up standard Teamraiser Autoresponders as reusables. At key spots in the copy we have a session variable S-Tag. That way you can set an optional custom closing paragraph in each teamraiser's AR email config right in the message body.


The s-tag just needs to be set before it is consumed in the DOM. (You can't set the s-tag in the message body and expect it to work in the stationary masthead.)

Dan, is that the bug you're referring to? Or is it just me fighting this?

 

Brian Mucha:

One thing we do is set up standard Teamraiser Autoresponders as reusables. At key spots in the copy we have a session variable S-Tag. That way you can set an optional custom closing paragraph in each teamraiser's AR email config right in the message body.


The s-tag just needs to be set before it is consumed in the DOM. (You can't set the s-tag in the message body and expect it to work in the stationary masthead.)

A couple of followups, if you don't mind:

• Are you just avoiding session variables in the email stationary before the HTML body?
• Are you hand-coding the session var in each autoresponder?
  
  I've had mixed results with something like...
       [[?xx::x[[S80:myid]]x::[[U0:myid=[[S42:blueprintID:fr-id]]::]]
  
  ...because S80 sometimes returns null (or somehow creates an infinite recursion or race conditon).
• If email campaigns are a no-go, how are you handling email blasts to your full event schedule (e.g. a registration coupon for the holiday)?

Kate Gollogly:

Hi Daniel,


How would you recommend testing coaching emails?


What I have been trying to do is add myself as an event manager (using the email that I registered with as a participant). Then sending my test coaching email to event managers only.


I have tried a variety of ways to display the S48 content, but nothing seems to be working. It looks like S42 (campaign information) works just fine. But S48 (participant information) is not working.


Just to confirm, it was definitely S48 tags that you used and had working in your coaching emails? I chatted with BB support and they said that S48 do not work in coaching emails, so I'm a bit confused.


Here is what I have tried so far:


<h2>S42 embedded in S48 tag - with frID = 0</h2>


<p>My Goal: [[E48:[[S42:0:fr-id]]:goal]]</p>

<p>I've Raised: [[E48:[[S42:0:fr-id]]:dollars]]</p>

<p>Percent of my goal: [[E48:[[S42:0:fr-id]]:pct-of-goal]]</p>

<p>Days to event: [[E48:[[S42:0:fr-id]]:days-to-event]]</p>



<h2>S42 embedded in S48 tag - with frID = Blueprint ID</h2>

<p>My Goal: [[E48:[[S42:1130:fr-id]]:goal]]</p>
<p>I've Raised: [[E48:[[S42:1130:fr-id]]:dollars]]</p>
<p>Percent of my goal: [[E48:[[S42:1130:fr-id]]:pct-of-goal]]</p>
<p>Days to event: [[E48:[[S42:1130:fr-id]]:days-to-event]]</p>



<h2>Only S48 NO S42 - with frID = 0</h2>


<p>My Goal: [[S48:0:goal]]</p>

<p>I've Raised: [[S48:0:dollars]]</p>

<p>Percent of my goal: [[S48:0:pct-of-goal]]</p>

<p>Days to event: [[S48:0:days-to-event]]</p>



<h2>Only S48 NO S42 - with frID = Blueprint ID</h2>


<p>My Goal: [[S48:1130:goal]]</p>

<p>I've Raised: [[S48:1130:dollars]]</p>

<p>Percent of my goal: [[S48:1130:pct-of-goal]]</p>

<p>Days to event: [[S48:1130:days-to-event]]</p>

<h2>Only S48 NO S42 - with frID = registered child event ID</h2>

<p>My Goal: [[S48:1133:goal]]</p>
<p>I've Raised: [[S48:1133:dollars]]</p>
<p>Percent of my goal: [[S48:1133:pct-of-goal]]</p>
<p>Days to event: [[S48:1133:days-to-event]]</p>


Any tips and tricks you can offer would be greatly appreciated! Thanks!

Hi Kate,


You have to put the S48 tags inside of the coaching email body message and not the stationary. It will definitely work because that's the thing we currently been doing (no report so far from our end-users telling otherwise so far thus I assume that it's just an oversight of the BB support you chatted with)


Use the one I re-highlighted from your post (with blueprint ID). 


Now to test coaching email, you are in the right direction there as you mentioned. We usually create a dummy account that we use for testing purpose of all kind, and you could actually put an "unconfirmed" donation amount for the sake of testing purpose on those accounts, also set a goal for each dummies (which all could be done from your Convio admin backend). Create an email group consisting of those dummy account as recipients, and copy the coaching email draft and schedule an actual delivery.


For different type of dummy accounts -- we have one for regular participant non team, a team captain, a team member, and then a participant based on our custom group (i.e. participants with diabetes that in our walk they are known as Red Strider, and Red Rider on our cycling), all of those (retrievable through S48 tags)  are parts of our "participant dashboard" displaying their stats within the coaching email.


Let us know.


ADD ON EDIT NOTE:


You could also probably try to put those S48 components inside of a "reusable" Pagebuilders and have that embedded within the coaching email body message (again, not stationary) through the S51 tag. This would probably make the maintenance going onward manageable since it's centralized so you just edit it on one page for all.  I haven't personally try this but it should work.


regards,

Daniel