Merge registrant fields into emails and messages

Personalize notifications by dropping mail-merge fields like {{first_name}}, {{webinar_title}}, and any custom registration field you've collected.

Every message eWebinar sends, email notifications, SMS/WhatsApp, in-session automated chat messages, can pull fields from the registrant so it reads "Hi Sarah," instead of "Hi there,". eWebinar calls these merge fields.

How to insert a merge field

In any message editor (email body, SMS template variables panel, automated chat message, interaction text) click the {{ }} or Insert field button. A menu lists every field available for the current webinar. Pick one and eWebinar inserts the placeholder at your cursor.

What fields are available

The merge-field picker is context-aware. It shows:

  • Built-in registrant fields: first_name, last_name, full_name, email, phone_number, moderatorEmail.
  • Webinar/session fields: webinar_title, start_date, session_time, duration, registration_link, watch_link, unsubscribe_link.
  • Custom registration fields: anything you added to the registration form on this webinar (company, role, industry, etc.).
  • Interaction response fields: for interactions that capture data (Question, Poll, Quiz, Contact Request). Only available in notifications that fire after the interaction.

What happens when a field is missing

If a merge field has no value for a given registrant, e.g. you merged {{company}} but the attendee left that field blank, eWebinar renders it as an empty string, not {{company}}. To guard against that, write the sentence so it still reads well without the value, or use a conditional fallback like Hi {{first_name|there}}, (pipe = fallback).

SMS/WhatsApp is different

Twilio requires pre-approved templates for WhatsApp, so SMS/WhatsApp merging uses template tokens mapped to properties separately. See SMS template variables.