Admin
Email Settings, Brand and Journeys
Email settings (Admin > Email) is where an admin turns on outbound email for the org. It opens with a readiness card that tells you the next step, such as Set your sender, Finish domain setup or Send a test email. Once everything is done it says "You're ready to send". Forge sends its own email through a dedicated sending account for your org; it does not send through Salesforce org-wide email addresses. Before your sending account is created, the Data region card above Sender identity lets you choose Global or European Union. It is preselected from your Salesforce organization country (EU, EEA, UK and Switzerland default to European Union). If the country cannot be read, Global is shown and you must confirm it. The region is fixed once the sending account exists and cannot be changed. Existing accounts stay on Global. EU accounts do not have delivery diagnostics or geographic stats. Delivery updates are turned on for your sending account automatically, in both regions: within minutes of a send, History shows each recipient as delivered, bounced or failed and Reports > Email counts it. Existing orgs are repaired automatically.
If you only read one section: set your Sending Domain, add the DNS records, verify, send a test. Leave everything under Advanced settings at its default unless a Salesforce admin has asked you to change it.
Setup steps
- Domain & DNS (start here, it can take up to 48 hours): set the sending domain, choose Register, add the DNS records it shows at your DNS provider, then choose Verify DNS. Records are listed in a table with Type, Host and Value, a status per record (Verified, Pending or Failed, each with an icon) and a copy button that announces Copied; a Failed record offers Check again. DNS changes can take 15 to 80 minutes, sometimes longer. Send to IT creates ready-to-copy instructions for whoever manages DNS. Until it verifies, emails go out from noreply@blackthorn.io and a notice with a Finish domain setup link shows on Admin > Email, Compose, Notifications and test sends. When the domain verifies, the admin who entered it gets an email; if it is still unverified 24 hours after entry, one reminder is sent.
- Additional sending domains (optional): under Sending domains, enter another domain and choose Add (up to 10 in total, including the primary). Publish the DNS records it shows, then choose the refresh icon to re-check; any verified domain can be used for From addresses. Removing a domain also removes it from the email provider and marks addresses that relied on it as Pending.
- Sender identity: enter From name, From address and an optional Reply-to address, then Save. Reply-to is used on emails that do not set their own Reply-to; clear the field to remove it.
- Verify a single sender (while your domain is pending): under Sender identity, choose Verify an address, fill in the From address, From name and mailing address, then choose Send verification email. Open the email sent to that address, click the link, then choose Refresh status; use Resend email or Remove if needed. Emails go out from that address until your domain verifies.
- Add additional senders (optional): add a From name, From address and optional Reply-to, the same fields as the default sender. Each sender shows Verified, Pending or Revoked. The count beside this step covers additional senders only.
- Send a test email: enter a recipient and choose a From address. Skip test email is available.
Defaults and sender settings: what each field does
| Field | What it does | Recommendation |
|---|---|---|
| From Email | The address recipients see as the sender on every email unless a template or sender overrides it. | Use a real, monitored address on your own domain, such as events@yourdomain.com. Addresses on a domain you have not verified are delivered less reliably and will not auto-verify. |
| From Name | The name shown in the recipient's inbox next to the From address. | Use a name people recognize: your organization or the events team, such as Acme Events Team. Avoid a person's name unless that person really sends the mail. |
| Sending Domain | The subdomain Forge sends from. Adding its DNS records proves you own it, which is what lets inbox providers trust the mail. | Use a dedicated subdomain such as mail.yourdomain.com rather than your root domain. That keeps marketing and event mail from affecting your staff's day-to-day email reputation. |
| Tracking Domain | The subdomain used to wrap links so Forge can count opens and clicks, for example click.yourdomain.com. It needs a CNAME record. | Use a sibling subdomain of your sending domain, such as click.yourdomain.com, so links in your emails show your brand instead of a third-party address. |
| Reply-to | Where replies go when a recipient answers. Marked Coming soon. | Until it is available, make sure the From address is a monitored inbox. |
| Bounce address | The address that receives delivery-failure notices. | Leave the default unless your IT team routes bounce handling elsewhere. |
| Unsubscribe redirect | Where a recipient lands after unsubscribing. | Point it to a page on your own site if you want a branded confirmation; otherwise leave it empty. |
Provisioning runs automatically after Salesforce OAuth and whenever you choose Provision / Refresh. It creates your org's email sending account, requests the domain and link branding, and records DNS health. After the records are added, check again with Provision / Refresh; each record flips from pending to verified once the email provider sees it, usually within 5 to 15 minutes and occasionally up to an hour (up to 48 hours with some DNS hosts).
| DNS record column | Meaning |
|---|---|
| Type | CNAME or TXT. Create the record with this type. |
| Host | The record name, sometimes called Name or Host at your DNS provider. |
| Value | What the record points to, sometimes called Target, Points to or Content. |
| Status | pending until the provider sees the record, then verified. |
| Existing records | Forge hostnames use frg1/frg2._domainkey and frgem, so they do not replace SendGrid records you already have. If a host already points elsewhere, Forge shows a warning: keep the existing record and ask your DNS admin. Domains set up earlier with s1/s2._domainkey can switch to unique records with Use unique records; sending stops until the new records verify. |
Sender addresses
Sender addresses are the From addresses people on your team can pick when sending. Add one per person or team that sends email, for example a separate address for sponsors and for attendee support.
| Field or status | What it does | Recommendation |
|---|---|---|
| Email address | The From address. | Use an address ending in your verified domain; it then verifies automatically once the domain is connected. |
| Display name | The name shown in inboxes for this sender. | Use the team or role, such as Events Team. |
| Label | A friendly name shown only inside Forge to help your team choose. | Describe the purpose, such as Sponsor outreach. |
| Reply-to | Where replies to this sender go. | Set it when replies should reach a shared inbox instead of the From address. |
| Verified | Ready to send. | Nothing to do. |
| Pending | Waiting for domain or single-sender verification. | Finish DNS verification, or use Verify to recheck. |
| Revoked | Taken out of use. Restore brings it back. | Revoke instead of Remove when you may need the address again. |
| Allowed by admin / Allow anyway | An admin override for an address that is not on the verified domain. | Use only when you know the address can receive and send correctly; mail from it may be filtered more often. |
| Default | The sender used when nothing else is chosen. | Make this your main events address. |
Send a test email
Enter a recipient and choose which From address to send from, then choose Send test email. The test is sent from the address you picked and shows who it came from, so you can confirm the From name, branding and delivery before anything goes to attendees. Last test send shows when you last tested.
Addresses, preferences and suppression
- Suppression list: addresses on it never receive email, regardless of campaign settings. Recipients who opt out of email are suppressed automatically from future sends with no setup.
- Preference categories: let recipients choose which types of email they receive. When someone selects Manage Preferences in an email, they see your categories as toggles. Each category has a Label, an Email group, a Default Opt-In (subscribers start opted in, or opted out) and an optional planner-only description. Only empty categories can be deleted. Recommendation: use few, plainly named categories such as Event Updates and Promotions, and keep transactional mail like confirmations out of optional categories.
- Suppression Activity: lists recent email jobs and how many recipients were filtered before sending, by category and unsubscribe group, with hashed samples. Download CSV exports it for audits.
Advanced settings
Advanced settings holds the Salesforce logging and emergency controls. They are usually configured by your Salesforce admin. The defaults are fine for most teams, and nothing under Advanced settings changes how an email looks or who receives it.
Salesforce activity logging
When Forge sends an email, it can also write a record of that email into Salesforce so your sales and customer-success teams can see in Salesforce what an attendee, contact or lead was sent, without opening Forge. There are two kinds of record, and you can use either, both or neither.
| Setting | What it does | Recommendation |
|---|---|---|
| Log as Salesforce Tasks | Writes a lightweight Task for each email. It appears in Activity History on the Contact, Lead and Attendee. A Task holds the email subject and date, marked Completed, not the message itself. | Leave on. It is cheap, easy to scan and answers the question "did we email this person?". |
| Log as Salesforce Email Messages | Writes a full-fidelity EmailMessage record with subject, body, to and from. It appears in the email history of the record. It uses more Salesforce storage and API calls. | Turn on when your team needs to see exactly what was sent, for example for support or compliance. Turn off if storage or API limits are tight; Tasks alone still show that the email went out. |
| Where to log attendee emails | Which records get the log entry: Attendee plus linked Contact, Attendee only, or Contact only. | Use Attendee plus linked Contact so the history shows both on the event registration and on the person's own record. Use Contact only if your sales team never opens Attendee records. Use Attendee only to keep the Contact timeline free of event mail. |
| Include HTML body on Email Messages | Stores the full HTML of the email on each Email Message. Adds about 8 KB per record. | Turn off to cut Salesforce storage; the subject, recipients and sender are still kept, but neither the HTML nor the plain-text body is stored. |
| Switch to Bulk API above this many recipients | The send size above which Forge writes the log records through Salesforce Bulk API v2 instead of normal calls, so a large send does not use up your daily API quota. The default is 500. | Keep the default. Lower it if large sends have hit your Salesforce API limits. |
| Warn when a blast will use more than this % of daily API quota | Forge saves this percentage as your threshold. In this version no send screen shows a confirmation prompt when a send would cross it, so watch your Salesforce API usage on the Salesforce connection health pages before large sends. | Keep the default. Lower it to be warned earlier. |
| Retry queue / Open bulk jobs / Retry now | Retry queue counts log records that could not be written to Salesforce yet and are waiting to be tried again. Open bulk jobs counts bulk writes still running. Retry now tries the waiting records immediately. | If the queue stays above zero, check Salesforce connection health before using Retry now. |
Logging in Salesforce never delays or blocks the email itself. If Salesforce is unavailable, the email still sends and the log entries wait in the retry queue.
Pause all sending
This is an emergency control. Pause all sending stops all outbound email at once. Emails Forge tries to send while it is on are skipped, not held, and they are not sent automatically when you turn it off. Use it when something is wrong, such as a wrong template going out, then turn it off when fixed and resend anything that was skipped.
Pause all sending stops all outbound email at once. Emails attempted while paused are skipped, not queued, and are not sent when you resume. Attendees receive no confirmations, reminders or campaigns while paused.
CC additional emails
CC Email Settings (Admin > CC Email Settings) controls which Salesforce email fields are copied on attendee emails. Turn on Enable CC additional emails, then pick the extra email fields on Attendee, Contact and Lead, for example an assistant's or guardian's email. Each event must also turn on CC in its own Communications settings. While Enable CC additional emails is off, the field pickers are greyed out and cannot be edited, but your saved selections stay visible. Use it when a second person, such as an executive assistant, must receive the same confirmations and reminders. You must choose at least one email field before you can enable the setting, and fields that share a label are numbered, for example Email (2), so you can tell them apart.
Brand Settings
Brand Settings, linked from the top of Email settings, sets your organization's logo, colors and font as a brand kit. It applies to all email template previews and new templates. A live preview updates as you edit, and you can pick one of your organization's own templates and sample data to see your brand in context (links in the preview never open Forge). Unsaved changes are flagged, and saving shows "Brand kit saved". If you have Page Designer pages, a Theme picker links the kit to a page's theme: colors and font follow that page, and any field you edit stays your own override.
Lifecycle Journeys
Lifecycle Journeys automates email sequences triggered by an event changing status. There is a section for each trigger, matched to the Salesforce Event Status: Event Activated (Draft to Active), Event Completed (Active to Completed) and Event Canceled (Any to Canceled). A journey applies to all events unless you set Applies to a single event, and new journeys start disabled.
- Choose Add under a trigger to create a journey with a template and an audience: All Attendees (registered) or a Custom Segment. A journey cannot be activated without a template, and each journey shows whether it applies to all events or one event.
- A journey can have steps. Each step has a template (or inherits the journey's), a delay in minutes after the previous step and an optional subject override.
- Journeys can be enabled or disabled and show Active or Paused. Preview shows a preview of the journey, and Execution history lists past runs.
- A journey flagged Missing (template) or Missing segment will not send.
- Recommendation: use Event Completed with a thank-you step and a survey step a day later; use Event Cancelled to send one clear cancellation notice.
Email delivery metrics
Delivery results (Processed, Delivered, Opens, Clicks, bounces, Dropped, Spam Reports and Unsubscribes) are reported per event under Manage > Reports > Email; see the Communications metrics and deliverability page for what each metric means and what to do about it.