Email Marketing

Reach your project's users with broadcast campaigns. Pick a behavioral audience segment, write your message, preview the exact recipients, then send — with per-recipient delivery tracking.

Email Marketing lets you send a one-off broadcast to a slice of your project's end users — a product announcement, a win-back campaign, a changelog digest. You choose an audience segment, OrbitNest resolves the real recipients server-side, and sends through your project's SMTP.

Who this targets

Broadcasts go to your project's users — the people who signed up to your app via project auth — not to OrbitNest admins. It uses the same SMTP and templates as the rest of your email.

Audience segments

Rather than uploading lists, you target built-in segments derived from user behavior. OrbitNest computes the membership at send time, so a segment is always current. Available segments:

all — every account in the project.
verified — users who confirmed their email.
unverified — signed up but never confirmed.
recent_signups_7d — accounts created in the last 7 days.
recent_signins_7d — users active in the last 7 days.
inactive_30d / inactive_60d / inactive_90d — no sign-in for 30 / 60 / 90+ days.
never_signed_in — created an account but never logged in.

Segments are enforced server-side

Recipients are resolved on the server from the segment you pick — an admin can't paste an arbitrary list or bypass the segment. This keeps broadcasts honest and prevents accidental sends to people who aren't your users.

Preview the audience (dry run)

Before sending, resolve a segment to see how many people it matches and a sample of who they are. This is a safe, read-only call — nothing is sent.

bash

curl "https://studio.orbitnest.io/api/admin/projects/{projectId}/email/audience\
?segment=inactive_30d" \
  -H "Authorization: Bearer $TOKEN"

The response includes the total recipient count and a sample list (up to 50 addresses) so you can sanity-check the targeting before committing.

Send a broadcast

Once the audience looks right, send. Provide the segment, a subject, and the HTML body (with an optional plain-text fallback). You can compose inline or reuse one of your email templates.

bash

curl -X POST \
  https://studio.orbitnest.io/api/admin/projects/{projectId}/email/broadcast \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "segment": "inactive_30d",
    "subject": "We miss you — here is what is new",
    "html": "<h1>Long time no see</h1><p>We shipped a lot. Come take a look.</p>",
    "text": "Long time no see. We shipped a lot — come take a look."
  }'

Delivery & tracking

The response reports the outcome of the send:

Sent — number of messages successfully handed to SMTP.
Failed — number that errored, with a sample of the reasons.
Success rate — sent ÷ total, shown in the Studio.

Limits & throughput

Sends are dispatched with bounded concurrency (a few at a time) to stay within SMTP provider rate limits and protect deliverability.
A single broadcast is capped at 10,000 recipients. For larger lists, split by segment or run multiple broadcasts.
There is no undo once a broadcast starts — always dry-run the audience first.

Respect unsubscribes & consent

You are responsible for sending only to users who expect email from you and for honoring opt-outs under CAN-SPAM / GDPR. Use the verified segment and your own consent flags to avoid emailing people who never opted in.

In the Studio

The Marketing Email view in the Studio wraps all of this in a visual flow: pick a segment, preview the recipients, compose or select a template, then confirm and send — with the delivery report shown inline when it completes.