Glossary

Shared terminology for the Transactional Email knowledge base. Use these terms consistently across articles, and link here on first use of an unfamiliar term.

Term	What it means
Transactional Email	Cambium’s HubSpot app that sends one-to-one transactional emails — receipts, subscription notices, account notifications — from a HubSpot workflow, using an email you design in HubSpot.
Transactional email	An email a recipient needs because of something they did or an account they hold, such as a receipt or a renewal notice. Not marketing: no promotions, discounts, upsells, or newsletters.
App Home	The Transactional Email page in HubSpot (Marketplace apps → Transactional Email) with your setup checklist, usage, sending status, domain health, errors, reporting, send log, and billing summary.
Settings	The Transactional Email settings page in HubSpot, with the tabs Sending domain, Sender profiles, Templates, Billing, Alerts, and Sending. Super Admins can change it; everyone else sees it read-only.
Super Admin	The HubSpot user role that can change Transactional Email settings, manage billing, and resume sending.
Send transactional email	The custom workflow action that sends one email to one recipient and returns a send status. Available in every HubSpot workflow type.
Template	A HubSpot marketing email, built with standard drag-and-drop modules, that the workflow action uses as the email’s content.
Compatible template	A template that only uses supported modules and content. An incompatible template can’t be sent and fails with template_incompatible.
Token	A placeholder such as {{ contact.firstname }} or {{ company.name }} that is replaced with the recipient contact’s (or their primary company’s) property value at send time.
Primary company	The company HubSpot marks as primary on a contact. {{ company.* }} tokens read from it.
Content review	The automatic check that every template version is transactional, not promotional. A template that fails can’t send; there is no override.
Template version	A template’s content at a point in time. Editing the subject, layout, modules, text, or styles creates a new version, which is reviewed again. Renaming the email does not.
Sender profile	A saved From name, an address on your sending domain, and an optional reply-to that a workflow action sends with. You pick it from a dropdown instead of typing addresses.
Sandbox sender	The built-in sender a workflow action can use until you go live: the sandbox address, the From name Cambium Transactional Email (editable), and replies to the person who installed the app.
Default sender profile	The sender profile listed first, marked (default), in the workflow action’s Sender profile dropdown. Exactly one profile is the default.
Sending domain	The domain your emails are sent from once you go live, such as notify.acme.com. You prove you own it by publishing DNS records. Base includes one.
DKIM	DomainKeys Identified Mail: a signature that proves an email really came from your domain. You publish three CNAME records for it.
MAIL FROM domain	The bounce-handling subdomain, bounce.<your domain>, with an MX and an SPF TXT record. It makes SPF pass for your domain.
SPF	Sender Policy Framework: a TXT record listing who may send mail for a domain. Transactional Email’s SPF record lives on the MAIL FROM domain, not your root domain.
DMARC	A TXT record at _dmarc.<your domain> that tells mailbox providers what to do with mail that fails DKIM and SPF. We suggest p=none only when you don’t already have one.
Sandbox	The free mode every account starts in: 20 sends total, to any recipient, from Cambium’s shared sandbox address. Only emails that go out count, and the 20 sends never reset, not even if you reinstall.
Live sending	Sending from your own verified domain. It needs a verified sending domain, the accepted Acceptable Use Policy, and an active subscription.
Acceptable Use Policy (AUP)	The rules for what you may send — transactional email only, to people you have a relationship with. A Super Admin accepts it before checkout.
Isolated sending reputation	Each HubSpot account sends with its own reputation, so another customer’s bounces and complaints can’t affect your deliverability.
Billing period	One month of your subscription, starting on the day you subscribed. Your included emails reset at the start of each period.
Included emails	The emails your plan includes per billing period: 1,000 on Base. Only live sends that go out count.
Top-up	A block of 100 extra emails that auto-buy adds when your included emails run out. It’s billed on your next monthly invoice, and unused top-up emails expire at the end of the billing period.
Auto-buy budget	The most Transactional Email may spend on top-ups for you in one billing period, in whole dollars. Auto-buy only buys whole top-ups, so it never goes over. $0 turns auto-buy off.
Warm-up	The daily sending limit that ramps up over a new sending domain’s first 30 days, so mailbox providers learn to trust it.
Auto-pause	An automatic stop on all sending when volume jumps far above normal or bounce or complaint rates get too high. A Super Admin resumes it in Settings.
Suppression	Skipping an address that hard-bounced, marked an email as spam, or soft-bounced 3 times in a row. Suppressed sends return suppressed.
Hard bounce	A permanent delivery failure, such as an address that doesn’t exist.
Soft bounce	A temporary delivery failure, such as a full mailbox.
Complaint	A recipient marking your email as spam.
Send status	The workflow action’s status output: sent, queued_warmup, or the reason the email didn’t send.
Error code	The workflow action’s error_code output: the same value as the send status when the email didn’t send, empty otherwise.
Message ID	The unique ID of a sent email. It appears in the workflow output, on the contact’s timeline event, and in the send log.
Send log	The searchable history of every send attempt — metadata only, kept for 45 days.