SolutionsA single title
The newsletter sells, and the list cannot see who bought
Your most engaged readers arrive from the daily newsletter and subscribe at the wall, and the next offer email reaches them anyway because the list is a copy that never heard.
The situation
What is going wrong
The newsletter is your best-converting channel, and the system that sends it is the last to hear that a reader converted.
The offer email after the purchase
The reader who subscribed on Tuesday gets Thursday’s discount email, because the list holds an address and the billing system holds an account, and nobody joins them before each send.
An unsubscribe that did not stick
A reader leaves a list in one system and the next import from the other puts them back. The media group hears about it from the reader.
Who is right about this person
Marketing and subscriptions each export, compare and argue about who a reader is, and whoever exported last wins.
What changes
When the list, the wall, the offer and the invoice read one record
EdgeKit Newsletters
The list on the record that knows who paid
Sign-ups, lists, preferences and consent sit on the reader record beside the subscription, and every list membership shows whether your email platform has been told, because a failed push is a reader still receiving mail they left.
- One record from the first address: sign-up, registration and purchase
- Unsubscribes made in your platform come back to the record
- Changes your platform has not accepted are counted on screen, lists with most first
EdgeKit Profile
Your email platform is told what the record says
Signed-in readers’ events are forwarded to the marketing platform you already run, on the same reader ID the list uses, so the offer campaign reads what the reader did, not a copy exported last week.
- Forwarded to Braze, your warehouse or any OTLP endpoint
- A purchase your pages report arrives as an event on the same reader ID
- The subscription is not sent as a profile field today
- BrazeCustom events · signed-in readers · on the reader IDOn
- OTLP endpointEvery event, the whole rowOn
- Warehouse · Snowflakeedgekit.events · backfilled from the archiveOn
EdgeKit Paywall
The newsletter as the step before the price
A rule can send a registered reader who has bought nothing to the newsletter sign-up, so the newsletter becomes the step between registering and paying, and the reader who arrives from it is already known to the wall.
- Registered and bought nothing is a group a rule addresses
- Live 60 seconds after you publish
- Your commercial team writes and changes it, with no release
EdgeKit Personalization
Each reader’s edition carries their stories
With EdgeKit Publications, the stories in a reader’s edition are ranked from what that reader has read, on the same record the wall reads, so the edition that brings a reader back is built from their own reading. Your editors set what is eligible, and the model ranks.
- Feeds fill at send time, reader by reader
- Pin, boost and hold back: the editors’ rules decide what is eligible
- The per-reader fill runs through Braze today
To: LenaThe Morning Brief · Mon 8 June
For you Election funding: the new cap, explained
To: TomThe Morning Brief · Mon 8 June
For you Paris shows: the five collections that mattered
To: AmaraThe Morning Brief · Mon 8 June
What the tariff ruling changes from today
For youPersonalised feed
Unsubscribe · View in browser
How it goes live
Four steps, and a working sign-up on your own site in a day
White-glove onboarding: we set it up with you, start to finish.
- 01
Map the lists you have to the record
Which lists, in which platform, and which group each mirrors there. We read it with you.
- 02
Create the lists and publish them
Each list names the group it mirrors in your platform and goes live with your next publish. Before that it takes no sign-ups.
- 03
Put the sign-up on your site, and in the wall
Your developers add the form and the preference page in your own design, three calls in EdgeKit’s browser SDK, and we build them with you if nobody is free. With EdgeKit Paywall, your commercial team writes the rule that sends a registered reader who has bought nothing to that form.
- 04
Keep sending, and watch one screen
Your platform keeps every campaign and journey. EdgeKit tells it who is on each list, hears back when someone unsubscribes there, and counts on the Lists screen every change your platform has not accepted.