SolutionsA media group
A known audience before you charge for anything
Search sends fewer readers and the ones who arrive cannot stay anonymous, so the registration wall is back. It pays only if the account it creates is the one the paywall will later read.
Reader groups
- 1Everyone herereason: subscriptionOpen
- 1Free articles under 10 in the last 30 daysOpen· counts 1
- 2Everyone elseoffer: Digital AnnualSubscribe offer
- 1Gift link covers this articlereason: giftOpen
- 2Free articles under 3 this monthOpen· counts 1
- 3Everyone elseRegistration ask
The situation
What is going wrong
Most groups already run the sequence. What they run it on is two systems, and the gap between them is where the registration’s value goes.
Two walls, two systems
The registration wall is a plugin and the paywall is a vendor. The account a reader made in the first is unknown to the second when the price arrives.
Known readers nobody can reach
An account with no newsletter sign-up and no preference beside it is an address. The direct channel the registration was meant to open never opens.
Every title on the same day
A rollout that switches every title at once waits for the slowest title, and a small team never finds a day when all of them are ready.
What changes
When the registration wall and the paywall read one record
EdgeKit Paywall
Registration is a rule, and so is the price
The wall that asks for an account and the wall that asks for money are rules in one console, on one record. Whether a reader is signed in, and what they hold, is the first thing a rule reads, so the paywall arrives later as a new rule rather than a new system. Anonymous reading is counted on the device, so a cleared cookie starts the meter again; once a reader registers, the count can follow the account instead.
- Anonymous, signed in and subscribed are groups a rule addresses by name
- Free reads per device and per signed-in reader, set separately
- On sign-in, the count carries to the account or starts again: your setting
- Counts
- Every readEach article once
- Per
- DeviceSigned-in readerGift link
- On sign-in
- Carry the count to their accountStart again
- Titles
- All titlesChoose titles
Read by
- Everyone else
- Signed in
EdgeKit ID
One account on your own domain
Readers register once, on your domain and under your brand, with a six-digit code or a sign-in link by email, or with Google. The same account is known on every title you later charge for, or kept separate per title if that is what you want.
- A code or a link by email, or Google, with first-party cookies
- One reader across every title, or separate per title, your call
- Ask a question at sign-up, job title or favourite section, and a rule can read whether it was answered
LThe Ledger
Sign in or create an account
Emailj.okafor@example.comCode sentEnter the six-digit code4819From subscriptions@ledger.exampleSign inorContinue with GoogleNo password. Signed in on ledger.example.EdgeKit Newsletters
The channel opens at registration
A newsletter sign-up at registration sits on the same record, so the readers you can reach are the readers who will later meet the price, and the offer email goes to people the record already knows.
- Sign-ups, lists and consent on the reader record
- Your email platform still sends
- Double opt-in per title when you want it
EdgeKit ID
Title by title, not all at once
Each title moves when its team is ready, as a setting per title that goes live with a publish. A reader signed in with your current login keeps the same account through the move, with nothing to re-enter.
- The sign-in mode is set per title, as a publish
- Both logins accepted while a title moves
- No email sent, no password chosen
- Mon 09:12Signed in with your login on Ledger Sport.EdgeKit checks the sign-in on every page.
- Wed 07:40 · Deploy 43Ledger Sport set to Both, while moving.
- Wed 08:05 · Next page viewMoved, in one page load.
- Your sign-in checked
- Email verified by your login
- Matched to account 0192f3…c41e
- Signed in with EdgeKit
- AfterSame account, nothing to re-enter.No email sent. No password chosen.
account 0192f3…c41e · unchanged
How it goes live
Four steps, one title first
White-glove onboarding: we set it up with you, start to finish.
- 01
Name the known audience you have today
Who already registers, through what, and where that record lives. We read it with you, title by title.
- 02
One tag and one CMS integration, done with you
We do the install and your developers review it. The registration form and the panel your rules return are drawn by your developers in your own design, with EdgeKit’s browser SDK. If nobody is free, we build them with you.
- 03
Registration first, on one title
The registration rule goes live on one title. Anonymous readers keep reading under the meter; the ones who register are known from that day, with the newsletter sign-up beside them.
- 04
The price later, as a rule
When the audience is there, the paywall is the next rule on the same record. Nobody registers twice, and the next title moves when its team is ready.