Sooner or later, everyone who runs a metered magazine site gets asked the same question: who sees the wall on this story, and why? It sounds like a question with a short answer. At a lot of publishers it isn’t, because the honest answer is “give me a minute to log into the vendor’s dashboard.” The rules that decide who pays, who reads free and what a reader in Toronto is offered live in a tool the circulation team rents. The only complete copy of them sits outside the building.
If you’re the publisher or circulation lead at a trade or consumer magazine with print and digital subscriptions, a metered site and a paywall vendor bolted on, I think those rules belong on your own site, where your own staff can read them.
Your paywall rules are your circulation strategy
A paywall is a set of business rules with a wall on top. Which stories are free. How many a reader gets before the meter runs out. What a reader in Canada is offered next to one in the US. Whether a paying subscriber ever sees a wall again. Put together, that is your circulation strategy, written down. When it lives in a vendor’s console, it is written down somewhere you rent.
Rented rules also tend to pile up. Campaigns outlive the URLs they were aimed at, and nobody on staff can easily list what is still live. Meanwhile the wall itself often runs in the reader’s browser, which means the full article goes out to every visitor and a script hides it from the ones who haven’t paid.
Joshua Benton made the underlying point at Nieman Lab in 2011, writing about the New York Times paywall and its deliberately leaky meter: “That kind of nuance makes for a much more precise instrument than a blunt-force paywall. But it also puts the onus on you to get all that nuance right.” In the same piece he noted that once a reader hit the limit, “The full text of the article is still visible in the page source.” (Nieman Lab, March 21, 2011)
The fair objection is that a leaky wall can be the right call. Benton made that argument himself, and he was right. A vendor also gets you a working wall quickly. A vendor-run wall is a reasonable place to start. The trouble comes later, once the nuance has grown and somebody has to own it.
What changes when the wall lives on your own site
Take Ski Area Management (SAM). For years SAM ran its subscription walls, its article meter and its regional offers through Admiral’s third-party script, and Admiral did the job. By this fall the setup had accumulated 73 journeys, most of them aimed at old Joomla URLs that stopped existing when SAM moved to WordPress. Staff couldn’t easily say which walls were live, which were dead, or what a Canadian reader would see next to an American one.
On November 9, saminfo.com started running those walls from its own WordPress site, through a module we built called SAM Journeys. Three things changed for the people who run circulation.
The rules are readable. Staff open a Journeys menu in WordPress and see every rule in plain terms. They can preview any URL and get a straight answer to “what would an anonymous US reader see here?” Before anything went public, SAM’s team saw the walls on the real site in a staff-only mode.
The hard wall withholds the article. Walls are decided on the server. A reader who has used up the meter sees the opening paragraphs, then an inline subscribe wall, and nothing after it, whether they’re in the USA, Canada or anywhere else. A reader who isn’t entitled to the story isn’t sent the story, so the text isn’t sitting in the page source for anyone who clicks View Source. The meter allows three magazine articles per year, the free views get a prompt the reader can dismiss, and subscribers exit every journey.
Offers follow the reader’s country. The USA, Canada and International each point at their own SimpleCirc subscribe link, so a reader in Canada gets the Canadian offer.
SAM still uses lighter prompts where a nudge is enough. The difference is that SAM now picks where the leaks are, and can read the list.
A faithful import can still be wrong
We brought all 73 Admiral journeys across with their original IDs, and every one landed as a draft. Nothing could go public by accident, and every rule could be traced to the journey it came from.
We thought the import would be the hard part. It wasn’t. The journeys came across faithfully, and they were still wrong.
The Canada journey had lost its targeting, so it would have fired on every page, the homepage included. The International journey had no rules at all, which meant it would have caught any reader whose location lookup failed. Two old adblock walls had dropped their only condition and would have hit everyone.
Importing the old setup is not the same as migrating it. A person had to read every rule again. We copied the US rules to the Canada and International journeys and retired the dead journeys instead of carrying them forward. Because everything had arrived as a draft, the broken rules were caught before a single reader met them.
That is the part I’d warn any publisher about. An importer copies every mistake exactly, including the ones aimed at pages that no longer exist. I’d budget more attention for rereading the rules than for moving them.
What it costs to own the rules instead of renting them
Ownership has a price on both sides, so here are the numbers we can stand behind.
Renting. Admiral’s public pricing page lists Paid Subscriptions, Paywalls & Donations at a 15% revenue share of subscriptions sold, or an All-In-One plan starting at $250 per month. A given publisher’s actual bill isn’t public, and I won’t guess at anyone’s.
Building it the traditional way (Zao estimate). For a typical US agency or in-house team, from the journey audit through the cutover, we estimate 232 to 352 hours. At Clutch’s US WordPress agency average of $100 to $149 an hour, from its WordPress Development Pricing Guide, that is an estimated range of $23,200 to $52,400. It is not a quote, and it is not our price.
What we did for SAM. We added SAM Journeys inside SAM’s existing scope of work, with no additional fees, because of our AI-enabled workflows.
If your wall lives in a vendor’s script tag, here’s where I’d start:
- Write down every rule you have in plain language: who sees each wall, on which URLs, in which countries.
- Find the dead ones. Rules aimed at URLs that no longer exist mean nobody has read the list in a while.
- Log out, open a walled article and view the page source. If the full text is there, your hard wall is a curtain.
- Check your RSS feed for the same thing. SAM’s had been carrying the full text of metered magazine stories; when we checked the public feed on November 10, it carried short descriptions and a link back to the site.
- If you move, import everything as drafts and have a person read every rule before anything goes public.
If you can’t say who sees the wall on a given story without someone else’s login, how much of your circulation strategy is actually yours?
Send us an article URL, and we’ll tell you what we’d look at first.