Everything you send
to more than one person
Write it once as a template. Send it from the composer, from your own code or on a day you pick, then read what happened after.
Opens are a guide. Some mail apps block images, so the real number is higher.
Where it starts
What this looks like today.
Last month's email, copied forward
The newsletter starts as a copy of the previous one, and small mistakes travel with it.
Sending lives in a separate tool
Campaign mail leaves from one platform, while the replies to it land in your ordinary inbox.
After send it goes quiet
You know how many went out, but not how many arrived or which addresses bounced.
How it works
Running in four steps.
- 01
Build the email from a template
Start from a template in the gallery and edit every block until the email reads the way you want.
- 02
Publish the version
A published version freezes, so later edits to the template cannot change what is already going out.
- 03
Send it, or put it on the calendar
Send from the composer, post up to a hundred messages a call from your code, or pick the day it lands.
- 04
Read the outcome
Analytics draws the opens and clicks, and every send shows as delivered, bounced, complained or failed.
What it runs on
The parts doing the work.
A campaign runs on ordinary parts of OpenEmail, and each one is useful on its own.
A body written once, versioned, and sent many times: from the composer, from your own code, or by an agent.
Whether a message you sent has been opened, when, how many times and which of its links were followed. On unless you turn it off, and plain about the readings it cannot get.
Tracked links and the open pixel on a subdomain you choose, such as links.yourdomain.com, instead of the OpenEmail address.
What your mailbox is actually doing, drawn rather than guessed at.
In practice
Every piece, walked through.
Each page below walks through one job, from writing the first draft to reading what happened after.
Design the email once, send it from your own code, and see what was opened.
Send a real invitation from your own address and watch the replies land on the event.
Write it today, land it on Tuesday morning, and edit or stop it until then.
Charts for what arrives, what you sent, what was opened and what was clicked.
Questions
Asked before signing up.
Can I send the same email from my own code?
Yes. Post up to a hundred messages a call, naming the published template and the values that fill it. The same template sends from the composer, so the two do not drift apart.
Do open figures tell me how many people read it?
No. Opens are a guide, not a count. Some mail apps block the image, so the real number is higher, and automated fetches by scanners and privacy proxies are left out rather than counted as readers.
Can I change a send after I have scheduled it?
Yes, until it goes. Queued mail sits on the same grid as your meetings, so you can rewrite it, move it to another time or cancel it. Bad addresses are held back on the next send until you allow them again.
Nearby
Other jobs for the same mailbox.
Your app posts a message and OpenEmail sends it from your own domain. Every call sits against the key that made it, and every send has an outcome to read.
