Merge tags are placeholders that FullHouse replaces with each person’s details when it sends an email. Write them in double curly brackets, such as {{first_name}}.
You can use them in two places:
- Webinar emails, in the Subject and Message of any reminder or follow-up email. A challenge uses the same emails and tags.
- The thank-you redirect address, which supports only two tags.
Nowhere else. Typed into a registration page headline, thank-you message, waiting room note, chat message or offer, a tag shows up as literal text.
Tags for emails
These twelve tags are all there is. The examples use a registrant called Ava Patel, a webinar with the slug spring-launch, and a session at 6pm London time.
| Tag | What it becomes | Example |
|---|---|---|
{{first_name}} |
The first name they entered | Ava |
{{last_name}} |
The last name they entered | Patel |
{{email}} |
Their email address | [email protected] |
{{webinar_title}} |
Your Public title | How to launch your course in 30 days |
{{presenter_name}} |
Your Presenter name | Jamie Rivera |
{{session_date}} |
The session date: weekday, month, day and year | Thursday, November 5, 2026 |
{{session_time}} |
The session start time, in 12-hour format | 6:00 PM |
{{timezone}} |
The timezone used for those two tags | Europe/London |
{{join_link}} |
Their personal link to the room | https://showtell.live/w/spring-launch/join/… |
{{replay_link}} |
Their personal link to the replay | https://showtell.live/w/spring-launch/replay/… |
{{calendar_link}} |
A calendar file (.ics) for their session |
https://showtell.live/w/spring-launch/calendar/….ics |
{{unsubscribe_link}} |
A personal link that unsubscribes them | https://showtell.live/unsubscribe/… |
How each tag behaves
Names
If someone leaves a name blank, or the field is hidden on your form, {{last_name}} comes out blank, and {{first_name}} comes out as “there”. A greeting of “Hi {{first_name}},” then reads “Hi there,”. The same applies in subjects. There’s no way to set another fallback word.
Presenter
{{presenter_name}} comes out blank if you haven’t set a presenter. It’s not used in any of the default emails.
Date, time and timezone
{{session_date}} and {{session_time}} are written out in the timezone shown by {{timezone}}. Which one that is:
- The timezone recorded from the visitor’s browser when they registered. Nearly everyone has this, even if you’ve chosen a Fixed timezone.
- If there isn’t one, your webinar’s timezone when you’re using Fixed timezone.
- Otherwise, UTC.
The format is always English, and always 12-hour. It doesn’t change with the visitor’s language or your settings.
{{timezone}} prints the raw timezone name, with its underscore if it has one, such as America/New_York. Keep that in mind if you want the sentence to read naturally. The default emails put it in brackets after the time.
Links
{{join_link}}, {{replay_link}} and {{calendar_link}} are personal to each person. Don’t copy one from a test or your own registration and paste it into an email, because everyone would get the same link.
For someone registered through a challenge, {{join_link}} and {{replay_link}} both go to their personal challenge hub instead of a single room.
These links keep working if you change the slug.
Any of these links becomes a button if it’s alone on its line, labelled for where it goes. See Format the message.
Unsubscribe
Opening this link shows the person a page asking them to confirm, and pressing Unsubscribe there stops their emails. Every email already has an Unsubscribe link in the footer, so you only need this tag if you want another one in the message itself.
The rules for writing tags
| Rule | Example |
|---|---|
| Use lowercase, exactly as listed. | {{first_name}} works. {{First_Name}} doesn’t. |
| Spaces inside the brackets are fine in emails. | {{ first_name }} works. |
| A tag that isn’t on the list stays as written. | {{city}} appears in the email as {{city}}. |
| There’s no fallback or formatting syntax. | {{first_name or there}} appears as written. |
| Answers to registration questions aren’t available as tags. | Use the registrant’s page or a CSV export instead. |
Check for leftovers in the preview. A mistyped tag stays visible there, as it will in the real email.
Where the sample values come from
The preview and test email fill in tags with sample details, not real ones.
| Tag | In the preview (What they receive) | In a test email |
|---|---|---|
{{first_name}} |
Ava | Your full account name |
{{last_name}} |
Patel | Blank |
{{email}} |
[email protected] |
Your account email |
{{webinar_title}} |
Your public title | Your public title |
{{presenter_name}} |
Your presenter, or a placeholder | Your presenter, or a placeholder |
{{session_date}} |
Two days from today, such as “Saturday 7 November” | Tomorrow, in the real format |
{{session_time}} |
6:00 PM | This time tomorrow, in the webinar’s timezone |
{{timezone}} |
Your browser’s timezone | The webinar’s timezone |
{{join_link}} |
A sample address | Your registration page |
{{replay_link}} |
A sample address | Your registration page |
{{calendar_link}} |
A sample address | Your registration page |
{{unsubscribe_link}} |
A sample address | Not a working link |
To see real values, register from the preview with your own email address and read the real emails.
Tags for the thank-you redirect
The Redirect to external page field on the thank-you step supports two tags, and only these two.
| Tag | What it becomes |
|---|---|
{{email}} |
The registrant’s email address |
{{join_link}} |
Their personal join link |
Both are encoded so they’re safe in a web address. An @ becomes %40, for example, and your page will read it back as normal if it decodes the value.
https://yoursite.com/thanks?email={{email}}&join={{join_link}}Here the tag must be written exactly as shown. Spaces inside the brackets don’t work, and other tags stay as written.