Email templates are the reusable designs that power every email Forge sends — from registration confirmations to event reminders and marketing blasts. Templates are managed in the global Communications > Templates library and can be assigned to individual events.
🖼️ In the Forge app: The template editor showing a confirmation email template with merge field tokens highlighted.
Template Types
| Template type | When it is sent | Editable content areas |
|---|---|---|
| Confirmation | Immediately after a successful registration | Subject, header, body, ticket summary block (auto-generated), footer |
| Waitlist | When a registrant is placed on the waitlist | Subject, header, body, footer |
| Reminder | On a schedule before the event (e.g. 7 days, 1 day) | Subject, header, body, event details block, footer |
| Cancellation | When a registration is cancelled | Subject, header, body, footer |
| Marketing / Blast | Sent manually or on schedule to an audience segment | Full template — subject, header, hero, body sections, CTA, footer |
| Custom | Triggered manually or via orchestration rules | Full template — all sections editable |
Template Editor
The template editor is a block-based drag-and-drop builder. Each template is composed of sections — header, body blocks, and footer — each with its own styling controls. The editor renders a live preview of the email as you build it.
Merge Fields (Personalization Tokens)
Use merge fields to insert dynamic content from the event and attendee record into email copy. Merge fields are written as double-curly-brace tokens and are resolved at send time.
| Token | Inserts | Source |
|---|---|---|
| {{attendee.firstName}} | The registrant's first name | conference360__Attendee__c / linked Contact |
| {{attendee.lastName}} | The registrant's last name | conference360__Attendee__c / linked Contact |
| {{attendee.email}} | The registrant's email address | conference360__Attendee__c |
| {{event.name}} | The event name | conference360__Event__c.Name |
| {{event.startDate}} | Formatted event start date in the event timezone | conference360__Event_Start_Date__c |
| {{event.endDate}} | Formatted event end date | conference360__Event_End_Date__c |
| {{event.location}} | Venue name and address or virtual/hybrid label | conference360__Venue_Name__c / Venue_Street__c / Venue_City__c |
| {{event.streamingUrl}} | The streaming/virtual attendance URL | conference360__Streaming_Service_URL__c |
| {{registration.ticketSummary}} | A formatted list of purchased items and amounts | Derived from bt_stripe__Sales_Document__c |
| {{registration.totalAmount}} | Total amount paid at checkout | bt_stripe__Sales_Document__c.Total |
| {{registration.confirmationNumber}} | Unique confirmation / order number | bt_stripe__Sales_Document__c |
| {{registration.calendarLink}} | An Add to Calendar link (Google, Outlook, iCal) | Generated by Forge — uses event date/time fields |
| {{organization.name}} | Your organization name (from Global Options) | Forge account settings |
| {{organization.logo}} | Your organization logo as an inline image tag | Forge account settings |
Merge fields that contain personal data (attendee name, email) are resolved just-in-time at send time from Salesforce. They are never cached in Forge's database. Do not include sensitive financial or health data in email copy.
Creating a Template
- Navigate to Communications > Templates in the left sidebar.
- Click New Template and choose a template type.
- Enter a name for the template — this is an internal label used in the template picker on event settings.
- Set the Subject line — this is what recipients see in their inbox. Use merge fields to personalize it (e.g. 'Your ticket to {{event.name}} is confirmed!').
- Build the template body using the drag-and-drop block editor.
- Click Preview to see a rendered preview with sample data.
- Click Save. The template is now available to assign to any event.
Assigning Templates to Events
Templates are assigned per email type on each event's Communications settings tab. For example, you can assign a custom branded confirmation template to your conference while a simpler template is used for webinars. Events that do not have a specific template assigned fall back to the account-level default template for that email type.
Template Cloning
Use the Duplicate option (three-dot menu next to a template) to create a copy of any existing template. This is the fastest way to create event-specific variations without starting from scratch.
:::(Note) (Template storage)
Email templates are stored in Forge's Postgres database, not in Salesforce. They reference Salesforce data only at send time through merge field resolution. Salesforce Triggered Sends also use these same Forge-native templates — there is no separate Salesforce Marketing Cloud template library involved.
:::