Reference
Email and Communications Settings Reference
This reference covers the email and communications settings available at both the account level (Global Options) and the event level (Event Info > Communications). These settings control how Forge sends transactional and marketing emails on behalf of your organization.
From Address and Sender Identity
| Setting | Where it lives | What it controls | Notes |
|---|---|---|---|
| From Name | Global Options > Email | The display name that appears in the email client as the sender | Example: 'Planner Conference Team' — keep it recognizable to avoid spam filters |
| From Email Address | Global Options > Email | The email address used in the From: header of all outgoing emails | Must be a verified domain in your email provider; unverified addresses will cause deliverability issues |
| Reply-To Address | Global Options > Email | Where replies are directed when a recipient clicks Reply in their email client | Can differ from the From address — useful for routing replies to a support inbox |
| Event From Name Override | Event Info > Communications | Overrides the account-level From Name for this specific event | Leave blank to use the account-level default |
| Event From Email Override | Event Info > Communications | Overrides the account-level From Email for this specific event | The override address must also be verified with your email provider |
Transactional Email Settings
| Setting | Where it lives | What it controls |
|---|---|---|
| Send Confirmation Email | Event Info > Communications | Master toggle — when off, no confirmation email is sent on registration |
| Confirmation Email Template | Event Info > Communications | The template used for the post-registration confirmation email for this event |
| Send Waitlist Email | Event Info > Communications | Sends a notification email when a registrant is added to the waitlist |
| Waitlist Email Template | Event Info > Communications | Template used for waitlist placement notifications |
| Send Cancellation Email | Event Info > Communications | Sends a notification when an attendee's registration is cancelled |
| Cancellation Email Template | Event Info > Communications | Template used for cancellation notifications |
| Send Reminder Email | Event Info > Communications | Enables scheduled reminder emails before the event |
| Reminder Days Before | Event Info > Communications | How many days before the event start the reminder is sent (e.g. 7, 3, 1) |
Email testing
Before your event goes live, disable the Send Confirmation Email toggle to prevent test registrations from emailing real contacts. Re-enable it when you are ready to start accepting real registrations.
Email Provider Configuration
Forge sends email through your configured email provider. Provider settings are managed in Global Options > Email Provider. Supported providers include SendGrid and Salesforce Marketing Cloud. The provider configuration covers:
- API key or credential for the email provider
- Domain verification status (SPF, DKIM, DMARC records)
- Bounce and unsubscribe webhook endpoint URLs that must be registered with your provider
- Dedicated sending IP (if your provider supports it)
Domain verification is required for deliverability
Emails sent from an unverified domain are far more likely to land in spam or be rejected by recipient mail servers. Set up SPF, DKIM, and DMARC DNS records for your sending domain before your first event. Your email provider's dashboard provides the exact records to add.
Salesforce Triggered Sends
In addition to Forge-native email sending, you can route transactional emails through Salesforce Marketing Cloud using Triggered Sends. When enabled, registration events fire a SFMC Triggered Send rather than a Forge email. This allows you to use SFMC's full template library, personalization, and reporting.
| Setting | What it controls |
|---|---|
| Enable SFMC Triggered Sends | Routes transactional emails to Salesforce Marketing Cloud instead of Forge's built-in sender |
| Triggered Send Definition (Confirmation) | The SFMC Triggered Send Definition External Key for the confirmation email |
| Triggered Send Definition (Reminder) | The SFMC Triggered Send Definition External Key for reminder emails |
| Data Extension Mapping | Controls which Forge fields are passed to the SFMC data extension for personalization |
SFMC integration prerequisite
Salesforce Marketing Cloud Triggered Sends require the SFMC Connector to be configured in your Salesforce org before they can be enabled in Forge. Contact your Salesforce admin to verify the connector is active.
Unsubscribe and Compliance
Forge automatically appends an unsubscribe link to all marketing emails. Transactional emails (confirmations, reminders) are exempt from unsubscribe requirements under CAN-SPAM and GDPR Article 6 lawful-basis processing, but Forge still provides an opt-out path for best practice.
| Setting | What it controls |
|---|---|
| Unsubscribe Page URL | The URL shown in the footer of every marketing email — defaults to Forge's built-in unsubscribe page |
| Unsubscribe List | The Salesforce list (or Forge audience) that records unsubscribed contacts |
| Footer Content | Optional custom footer text appended to all outgoing emails — include your physical mailing address to comply with CAN-SPAM |