Send to the whole table, from a domain that's yours.
Pick a table, pick who's opted in, pick a template you designed, and send. Bounces and complaints come back and suppress themselves, unsubscribes are one click, and the whole thing pauses itself if your reputation starts to slip.
- Your own DKIM domain
- Opt-in gate
- Automatic suppression
- One-click unsubscribe
- Auto-pause on bad reputation
The unglamorous parts, done properly.
Anyone can put an email in a queue. The difference is what happens when a mailbox rejects it, when someone hits unsubscribe, and when your bounce rate starts climbing mid-send.
Audience from your own table
Point at a TinyTables table, name the email column, and name the column that records consent. Rows that don't match are never queued.
Consent is fail-closed
Once you set a consent column, a row has to match an allowed value to be included. Not set is not sent.
Your domain, verified
Add a domain, get three DKIM CNAMEs, verify once. Then any from-address on that domain works with no extra step.
A suppression list that wins
Hard bounces, complaints and unsubscribes suppress automatically and are checked twice — at build time and again at the moment of sending.
One-click unsubscribe
RFC 8058 list-unsubscribe, so Gmail and Outlook show the native button. Corporate link scanners can't accidentally unsubscribe people.
It stops itself
If bounces pass 5% or complaints pass 0.1% after fifty sends, the campaign pauses rather than burning your domain.
Honest counts
Every metric is set once per recipient, so a provider retrying a webhook can't inflate your open rate.
See who, not just how many
Click into the actual addresses behind bounced, unsubscribed and complained, with the provider's reason.
Proof it before you send
Send yourself a test, then a confirm gate shows a fresh recipient count and real sample addresses before anything leaves.
From table to inbox.
- 01
Verify your domain once
Add your sending domain, drop in three DKIM records, hit verify. After that every address on that domain is available as a sender.
- 02
Build the send
Choose a TinyEmail template, write a subject with merge variables, pick the table and the consent column, and watch the recipient count update as you go.
- 03
Confirm and watch it drain
The confirm gate shows you a fresh count and real addresses. Then it queues, throttles to your provider rate, retries what's retryable and reports as it goes.
It uses the rest of your TinyCommand.
Same login, same data, same bill. No export step between the thing that finds the answer and the thing that acts on it.
Where you design the template. Campaigns is what sends it to a list.
The audience, the consent column and the merge data all come from here.
Fill in the missing emails before you send, and verify the risky ones.
Capture the opt-in that puts someone on the list in the first place.
What TinyCampaigns is not.
Every tool’s marketing page tells you what it does. This is the part that usually isn’t on one, so you can find out now instead of after you’ve built on it.
- This is broadcast sending. Drip sequences and behaviour-triggered automations are not part of it today.
- The audience is fixed when you confirm the send, not evaluated as it drains. Rows added to the table after that aren't included in that campaign.
- In the send screen a segment is a table plus a consent column. There is no filter builder and no saved-view picker yet.
- A campaign can't be edited after it's created. Duplicate and change the copy instead.
- Reporting is unique-per-recipient: opens, clicks, bounces, complaints, unsubscribes. There is no repeat-open count, no per-link breakdown, no geo or device split, and no CSV export of the report.
- Domain verification is DKIM. We do not check your SPF or DMARC records for you — worth setting up yourself.
- There is no A/B test on subject lines.
- Preview text isn't wired through to the message yet, so don't rely on it in the inbox preview.
Questions people actually ask.
How is this different from TinyEmails?
TinyEmails is where you design the email. TinyCampaigns is the machinery that sends it to a list: audience, queue, throttling, your sending domain, suppression, bounce handling and reporting. Two products, one hand-off.
Can I send from my own domain?
Yes, and you should. Add the domain, add three DKIM CNAME records, verify, and every address on it becomes a valid sender.
What stops me emailing someone who opted out?
The suppression list, and it's checked twice — once when the audience is built and again immediately before each message goes out. It beats whatever your table says.
What if a send starts going badly?
It pauses itself. Past fifty sends, a bounce rate over 5% or a complaint rate over 0.1% stops the campaign automatically rather than letting it run your domain into the ground.
Do campaign sends cost credits?
Campaign sending is not credit-metered today. Test sends are limited to five per workspace per day.
Deliverability is the product. Everything else is a text editor.
Your domain, your table, your opt-ins — and the bounce handling you'd otherwise pay a separate vendor for.