Campaigns
Write it, pick who gets it, schedule it. The queue survives a restart mid-way through forty thousand recipients and picks up where it stopped.
In private beta · from $19/month
The follow-up you
keep meaning to write.
Beacon is the marketing half of BeaconPulsar. It holds your contacts, decides who should hear what, and sends it — including the messages that go out weeks later because of something a customer did today.
- Journey step types
- 5
Send, wait, branch, exit, and an SMS step that records itself as skipped.
- Recipient states
- 7
Queued, sent, delivered, opened, clicked, bounced, failed — counted, not sampled.
- Sends lost to a restart
- 0
The queue is a table with a lease per row, not a loop inside a request.
- Starts at
- $19/mo
Bought on its own. Pulsar is a separate purchase you do not have to make.
Automation
Journeys that run per person.
Five step types and no more. Each person moves through on their own clock, held by a background worker, so closing the tab changes nothing.
- order.placedPosted to the events endpoint by your shop.
- Thanks — here is what happens nextThrough the same queue a campaign uses.
- 3 days
- Did they open it?Evaluated per person, on that person's own clock.
- Yes — leave the journeyThey heard you. Nothing further is sent.
- No — a second look, different subjectTwo attempts is the whole plan.
Audience
A segment is a rule, not a list.
Evaluated against each contact the moment it is used, so it is never stale and there is nothing to rebuild after an import.
{ "allOf": [ { "field": "emailConsent", "is": true }, { "field": "lifetimeValue", "greaterThan": 50 }, { "field": "daysSinceLastOrder", "greaterThan": 60 } ], "anyOf": [ { "field": "tags", "contains": "wholesale" }, { "field": "opensLast90", "greaterThan": 2 } ]}Sending
Nothing sends inside the click.
Pressing send writes one row per recipient and returns. A worker drains them, taking a short lease on each row, so two workers can never send the same person twice.
| Recipient | State | Updated |
|---|---|---|
| rima@example.com | Opened | 09:41:02 |
| arif@example.com | Delivered | 09:41:02 |
| tanvir@example.com | Sent | 09:41:03 |
| bounced@example.com | Bounced | 09:41:03 |
| sadia@example.com | Queued | — |
Events
Your shop triggers the journey.
Post an event and the people who match enter on their own. No nightly batch, no export, no spreadsheet.
curl -X POST https://api.beaconpulsar.com/v1/events \ -H "Authorization: Bearer $BEACON_KEY" \ -H "Content-Type: application/json" \ -d '{"name":"order.placed", "contact":"rima@example.com", "properties":{"total":4200}}'What is in it
Everything, in one list.
Segments that update themselves
Rules over behaviour, not a static list. Re-read every time they are used, so there is nothing to rebuild after an import.
Journeys
Wait, branch, send, exit. A welcome series, an abandoned cart, a win-back — each running per person in a background worker rather than a browser tab.
Social publishing
Scheduling and publishing to social alongside the email calendar. Being switched on now — the product page marks which parts are live.
Templates and content
Reusable blocks, so a campaign is assembled rather than written from nothing, with a preview of what actually lands.
Analytics and attribution
Opens and clicks per campaign, and where they led. Which message made money, not which had the best open rate.
Consent, kept properly
Subscription state per contact and per channel, recorded with when and how it was given — because the day it matters is the day someone asks.
Pricing
Beacon is priced on its own.
One price list in US dollars, the same in every country. Yearly is the only discount, at 17%.
$19/month
One list, a newsletter, a few campaigns a month.
- 2,500 contacts
- 25,000 sends a month
- Campaigns and segments
- Email support
$49/month
You want journeys running while you do something else.
- 25,000 contacts
- 250,000 sends a month
- Journeys and automation
- A/B testing
$129/month
Volume where deliverability is its own job.
- 150,000 contacts
- 1.5M sends a month
- Dedicated sending IP
- Priority support
Not there yet
What we have not built.
- SMS steps exist in journeys but are not sending yet — the step records that it was skipped rather than failing quietly.
- Send-time optimisation and content scoring are not built.
- No AI-written segments and no predicted-value scoring. Every rule is one you wrote.
Questions
Answers before you ask.
Do I have to buy Pulsar as well?
No. Beacon is priced and cancelled on its own, from $19 a month. Pulsar sits in your dashboard as a preview with its price on it, doing nothing until you want it.
What happens to a campaign if the server restarts mid-send?
It resumes. The queue is a table with a lease on each row, not a loop inside a request, so rows a stopped worker had leased are reclaimed by age and rows already sent are never sent again.
How are opens and clicks counted?
From the per-recipient rows themselves — seven states each: queued, sent, delivered, opened, clicked, bounced, failed. The dashboard figures are counted, not estimated from a sample.
Can I import a list I already have?
Yes. Because segments are rules evaluated at use, an import does not leave you with stale lists to rebuild afterwards.