Rheo documentation
User GuideEngage

Set up Engage

Connect your email provider, verify sending, manage consent, and keep deliverability healthy.

Before you send

You need three things before a live marketing send:

  1. A connected email provider with a verified sending identity
  2. A physical mailing address on the provider setup (required for CAN-SPAM)
  3. Customers with email addresses and granted marketing consent

Open App settings → Engage settings.

Email Settings (provider)

Rheo Engage supports one bring-your-own provider per app:

  • Amazon SES
  • Resend
  • Postmark
  • SendGrid

Connect the provider

  1. Open App settings → Engage settings → Email Settings.
  2. Choose a provider and enter the shared from-address fields plus that provider’s credentials.
  3. Set the physical mailing address recipients will see in compliance footers.
  4. Copy the shown webhook URL into your provider (or into SNS for Amazon SES) so bounce, complaint, and delivery events reach Rheo.
  5. Refresh identity until status is verified. Do not send live traffic while identity is unverified.

Amazon SES notes

  1. Verify your domain in AWS SES (DKIM / SPF / DMARC) and your from-address.
  2. Create an IAM user that can send email and read identity status.
  3. Create a SES configuration set that publishes bounce and complaint events to your SNS topic, then subscribe that topic to the Rheo Engage webhook URL shown in Email Settings.

Platform onboarding and billing mail for workspace users uses Rheo-owned SES and is configured separately. Do not mix those webhooks with Engage.

Open App settings → Engage settings → Marketing consent.

  • Marketing topics mode is off by default. When you turn it on, every broadcast and automation must pick a topic, and the preference center shows per-topic toggles.
  • Add topic keys and labels your team will recognize (for example product updates vs promotions).

Preference center

On the same Marketing consent page, the Preference center section lets you brand the hosted page where recipients manage consent. Marketing emails include Unsubscribe and Manage preferences links that open this page.

When topics mode is off, the preference center shows a single marketing opt-in toggle. When topics mode is on, recipients can manage each topic.

When someone shares an email inside your product, your engineering team should send that email and marketing consent through the SDK identify path so they land on the same Customer record. Do not rely on stuffing email into event traits for opt-in. Details live in the Developer Guide and Customer concept page.

CSV import

Customer or segment CSV imports that create email audiences require:

  • email
  • email_marketing_consent (granted or denied)

Optional columns include app_user_id and topic:<key> when topics mode is on. Imports without app_user_id create a Customer that can later merge when the SDK identifies the same email.

Re-grant after unsubscribe

On a Customer profile, granting marketing consent again after an unsubscribe requires an attestation note (how and when permission was obtained). Rheo stores that note with the consent change.

Frequency Cap, quiet hours, and test allowlist

Open App settings → Engage settings → Frequency Cap.

SettingWhat it does
Max emails per contact / Rolling window (days)Caps how many marketing emails one person can receive in the window
App default timezoneUsed when a Customer has no timezone, and for absolute broadcast schedules
Quiet hours (defer delivery)Defers marketing email to the end of the local quiet window instead of dropping it
Test destination allowlistLimits who may receive test-environment broadcasts and automations

Automations can optionally be marked Exempt from app frequency cap in their settings when a transactional-style journey must ignore the cap.

Deliverability health

Email Settings shows deliverability health for your connection. Rheo tracks opens and clicks. Bounce and complaint events from your provider webhook update suppressions on Customers.

If hard bounce or complaint rates cross the hard threshold, Rheo shows Sending paused. Fix the underlying issue, then use Resume sending when you are ready.

From the terminal

Provider connect, settings, health, and resume sending are available in the CLI with rheo engage provider, rheo engage settings, rheo engage health, and rheo engage deliverability resume. Connecting a provider and resuming sends require an owner or admin key.

Rheo Engage

Reach customers by email after they use your app — broadcasts, automations, and consent on your own provider.

Broadcasts

Send one-shot lifecycle emails to consented customers or segments, with local-time scheduling and conversion goals.

On this page

Before you sendEmail Settings (provider)Connect the providerAmazon SES notesMarketing consent and topicsPreference centerCollecting consent from the appCSV importRe-grant after unsubscribeFrequency Cap, quiet hours, and test allowlistDeliverability healthFrom the terminalRelated