Skip to main content

Send transactional messages

Transactional messages are one-to-one Editions triggered by something a subscriber does — a purchase, a signup, a password reset, an appointment booking. Unlike a Broadcast that goes to a whole audience on a schedule, a transactional message fires for a single subscriber the moment an event occurs, and its personalization is filled in from data passed with that event.

Before you begin​

  • An approved transactional Edition saved in a Folder, with personalization tokens for the values that change per subscriber (name, order number, amount, links).
  • A trigger source: your application calling the transactional send API, or an automation/journey step configured to send this Edition. (Confirm which is enabled for your account.)
  • API credentials or an API key if you send from your own application. (Generate and store these in your account settings — confirm the exact location in your account.)
  • Agreement that this content is genuinely transactional (tied to an action), not promotional. Transactional streams should not be used for marketing.

Steps​

  1. Build and approve the Edition, adding personalization tokens for every value supplied at send time.
  2. Note the Edition's identifier so the trigger can reference it. (Confirm where the identifier appears in your account.)
  3. Connect the trigger: point your application at the transactional send endpoint, or add a send step in your automation that selects this Edition.
  4. Pass the recipient address plus the token values for that specific subscriber with each request.
  5. Send a test event to yourself and confirm every token resolves and links work.
  6. Enable the trigger for live traffic.

Result​

Each qualifying event delivers a single, personalized message to one subscriber within moments, and each send is logged individually in your reports.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.