--- title: "Campaigns and newsletters - OpenEmail" description: "Write the email once as a template, send it from the composer or your own code, and see what was delivered, opened and clicked" url: "https://openemail.uk/use-cases/campaigns" --- Newsletters and announcements # 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. [Open mail](https://openemail.uk/mail/inbox) [Get Started](https://openemail.uk/signup.md)[All use cases](https://openemail.uk/use-cases.md) Monthly update Monthly update v3 Published Hi {{firstName}} Omar Read the update POST /emails/batch dana@northwind.co Clicked omar@lumen.io Sent mia@pinefield.dev Queued 130 Sent 42 Opened 9 Clicked 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. 1. 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. 2. 02 Publish the version A published version freezes, so later edits to the template cannot change what is already going out. 3. 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. 4. 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. Templates A body written once, versioned, and sent many times: from the composer, from your own code, or by an agent. Intro Invoice Follow-up Hi Sarah, good to meet you at Scheduled send Write it now, land it when they are awake. Tomorrow, 8:00 queued, not sent See when mail you sent was opened 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. Tracking on your own domain Tracked links and the open pixel on a subdomain you choose, such as links.yourdomain.com, instead of the OpenEmail address. Analytics & graphs What your mailbox is actually doing, drawn rather than guessed at. 62 on Monday · 38 still waiting on you Recipient suggestions The people you already write to, offered as you type. SR AK NM JD PL +1,240 sarahreyes@acme.com Verified sender A mark beside the sender when the sending domain’s published records line up. receipts@ stripe.com SPF DKIM DMARC verified sender In practice ## Every piece, walked through. Each page below walks through one job, from writing the first draft to reading what happened after. Send a newsletter Design the email once, send it from your own code, and see what was opened. Hi {{firstName}} Omar Read the update dana@northwind.co Clicked omar@lumen.io Sent 130 Sent 42 Opened 9 Clicked Invite people to meetings Send a real invitation from your own address and watch the replies land on the event. 14:00 14:30 Design review AN BR CM Yes 2 Maybe 1 No 0 Schedule an announcement Write it today, land it on Tuesday morning, and edit or stop it until then. Pricing update, in plain words Scheduled Sends Tue 09:00 Mon Tue Wed Thu Fri See what your mail does Charts for what arrives, what you sent, what was opened and what was clicked. Opened 128 +6 Clicked 41 6 automated fetches Not counted Watch what happens after send See what happened to every send, and keep dead addresses out of the next one. omar@lumen.io Skipped Delivered 129 Bounced 3 Blocked omar@lumen.io Held back 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. The mail your product sends 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. to buyer@northwind.co template order-receipt 202 msg\_9f2c7a14 email.sent msg\_9f2c7a14 email.delivered msg\_9f2c7a14 email.opened msg\_9f2c7a14 Put the whole company Addresses for people and for roles, all on one domain. Each has its own people, keeps the shared sign-off, and stays put when somebody leaves. DNS records Verified MX @ TXT @ ben@ acme.com BW anna@ acme.com AL Keep your domain yours Publish the records that prove your mail is yours. Every message that arrives comes scored, with the sender checks and the reasons on it. yourdomain.com Records found TXT @ CNAME oe1.\_domainkey TXT \_dmarc MX @ [All use cases](https://openemail.uk/use-cases.md)