Gmail sending
Send campaigns through your own Gmail / Google Workspace mailboxes instead of the domain sender.
Alongside the verified domain sender, a campaign can send through a pool of your own Gmail / Google Workspace mailboxes over SMTP. Each message goes out from a real mailbox — useful for cold outreach and one-to-one-feeling mail where sending "as a person" matters more than domain-level throughput.
Manage the pool under Gmail sending in the dashboard (only the project owner can add or edit accounts).
Connecting a mailbox
Gmail requires an app-password, not your normal login:
- Turn on 2-Step Verification for the Google account.
- Create an app-password (Google Account → Security → App passwords).
- In Gmail sending → Add account, enter the address, a label, and the 16-character app-password.
The app-password is encrypted at rest and never shown again — the settings list only indicates whether a credential is set. A bad or revoked password surfaces as an error on the account so you can fix it.
Daily caps & rotation
Each account carries a daily send cap (recipients per UTC day) and a weight. A Gmail-backend campaign rotates across the enabled, credentialed accounts using a weighted, cap-aware round-robin: it prefers the account that has sent the least relative to its weight, and skips any account that's reached its cap for the day.
- Free Gmail allows roughly 500 recipients/day; Workspace roughly 2,000. Stay comfortably under these — the default cap is conservative.
- A campaign can restrict itself to a subset of accounts and set per-account quotas ("send 200 from A, 500 from B") on the campaign's Setup step.
- If every eligible account is capped, the campaign auto-pauses and resumes automatically once the UTC day rolls over (or resume it manually).
How it differs from the domain sender
| Domain sender (SES) | Gmail | |
|---|---|---|
| From address | any address on a verified domain | the connected mailbox itself |
| Domain verification | required | not required |
| Throughput | high | per-mailbox daily caps |
| Delivery events | real (delivered/bounce/complaint) | acceptance only (see below) |
| Opens / clicks | provider tracking | self-hosted pixel + link redirect |
Tracking & analytics
Gmail SMTP gives no event feed, so tracking is handled on our side:
- Delivered — recorded when Gmail accepts the message (its
250 OK). This is a handoff signal, not a guaranteed inbox landing. - Opened — a tracking pixel we inject fires when the message is displayed. Gmail pre-fetches and caches images, so open counts run high and should be read as directional, not exact.
- Clicked — tracked links redirect through us and are accurate.
- Bounces and spam complaints are not available for Gmail sends (there's no feedback loop); hard failures at send time are still recorded as failed.
These flow into the metrics dashboard, the message log, and your webhooks the same way domain sends do.
Gmail sends still respect your send quota and the suppression list — suppressed addresses are skipped regardless of backend.