A content locker asks a visitor to complete one offer before your content unlocks. Done well it earns more per visitor than any banner placement. Done badly it destroys trust in a week. Here is the difference, and how to build one that lasts.
Banner advertising pays you for attention. Content locking pays you for intent. That single difference is why a page with 400 visitors a day can out-earn a page with 40,000, and why content locking has stayed profitable through fifteen years of display ad decline.
The mechanic is simple enough to explain in one sentence: a visitor wants something specific from you, and before they get it they complete one short offer. Executing it well is harder, because a locker is the most aggressive thing you can put in front of a visitor and the fastest way to lose one. This guide covers both halves.
A locker is a gate placed between a visitor and a piece of content they have already decided they want. When the visitor arrives, they see a short list of offers filtered to their country and device. They pick one, complete it, and the content unlocks automatically when the advertiser confirms the conversion.
The critical word in that description is already. A locker does not create demand. It converts demand that exists. This is why the same locker earns $0.40 per visitor on a download page and $0.004 on a homepage: on the download page, the visitor came to get something.
Three reasons, in order of size.
The visitor is pre-qualified. Somebody who clicked "Download" has demonstrated more intent than a thousand people who scrolled past a leaderboard ad. You are monetising the bottom of your funnel instead of the top.
The payout is per action, not per impression. A CPM placement pays you a few dollars per thousand views. A single locker conversion often pays more than a thousand impressions, and a good page produces conversions at double-digit percentages.
There is nothing to ignore. Banner blindness is a measured phenomenon. A locker is the page. It cannot be scrolled past, and it does not compete with your own content for attention because it appears at the moment your content is being requested.
The trade has to be honest. A locker works when the visitor's side of the bargain is worth what you are asking. If the content behind the gate is thin, the visitor learns that lesson exactly once, and you lose the traffic source that took you months to build.
ToroAds gives you four delivery methods, and choosing correctly matters more than most publishers realise.
Iframe embed. The locker renders inside your page in a sandboxed frame. Fastest to install, works on any CMS, and keeps your page layout intact. This is the default and the right answer for most publishers.
JavaScript runtime. A script tag that lets you trigger the locker from your own code: on a button click, after a countdown, at the end of a video. Use this when the unlock needs to happen at a specific moment rather than on page load.
Inline fragment. The locker is injected directly into your page markup with no iframe at all. Slightly more work to integrate, noticeably better on mobile, and the best choice if you care about layout continuity.
Direct link. A standalone hosted page. No integration at all: you just send traffic to a URL. This is what you use from social bios, Telegram channels, QR codes and anywhere you do not control the HTML.
There is also a downloadable server-side integration if you want the unlock verified by your own backend before releasing a file, which is the correct approach when the locked asset genuinely costs you money to serve.
The platform ships six locker templates: Modern Pro, Noche AZ, Brisco, Minimal Light, Captcha and FreeSamples. They differ in layout density, colour weight and how the offer list is presented.
The temptation is to pick the one that looks best to you. Resist it. Pick the one that looks most consistent with the page it sits on. A dark, heavy locker on a light, minimal blog reads as an ad injection and gets closed. The same locker on a gaming site reads as native and converts.
If you can only test one variable this month, test the template. It is the highest-leverage change available and it takes thirty seconds.
You can serve your lockers from your own domain rather than a shared platform hostname. Publishers routinely skip this, and it is a mistake, for two reasons.
The first is conversion rate. A URL a visitor recognises converts better than one they do not. This is not a small effect on cautious audiences.
The second is durability. A shared hostname accumulates the reputation of everyone using it. Your own domain accumulates only yours. If you plan to build anything long term, own the surface it runs on.
Publisher content also executes on a separate content origin from the main platform, which is a deliberate security boundary: your custom HTML, CSS and JavaScript can never run on the same origin as the dashboard that holds your balance. It costs you nothing and it removes an entire class of risk from the network you are earning on.
Lock the reward, never the road to it. The visitor should be able to read your article, see your screenshots, and understand what they are getting before the gate appears. Gating the description as well as the download is the single most common reason lockers get abandoned.
Tell them what is behind the gate, specifically. "Unlock the file" performs worse than "Unlock the 42-page PDF". Specificity is free conversion rate.
Show fewer offers, not more. A wall of twenty offers is a decision problem. Four well-matched offers is a choice. Every additional option past about six costs you completions.
Match the offer weight to the content weight. Asking for a multi-step registration to unlock a wallpaper is a bad trade and visitors know it. Short offers for small content, higher-payout offers for genuinely valuable content.
Never promise something you do not have. This is the one that ends publisher accounts. If the unlock delivers nothing, the visitor complains to the advertiser, the advertiser charges the conversion back, and the offer disappears for everybody.
Good candidates share one property: the visitor arrived specifically to get them.
Bad candidates are equally consistent: your homepage, your article body, your category pages, anything a search engine needs to index, and anything a visitor did not ask for by name.
Worth understanding, because it explains the delay publishers sometimes see between a visitor completing an offer and the content opening.
Your locker never decides on its own that an offer was completed. The visitor completes the action on the advertiser's property, the advertiser fires a server-to-server postback confirming it, and only then does the unlock state flip. The check runs against the platform, not against anything in the browser, which is why an unlock cannot be faked by editing the page.
That design has one consequence you should plan for: unlock timing depends on how fast the advertiser reports. Most report in seconds. A few take longer, and a locker that says "verifying, this can take a moment" loses far fewer visitors than one that appears frozen.
It also means a rejected conversion mirrors back onto the unlock record, so your reporting and your visitor's experience never disagree about what happened.
The number that matters is not conversion rate and it is not payout. It is earnings per visitor to the locked page: total locker revenue divided by everyone who reached the gate, including the people who left.
That number is honest in a way conversion rate is not. A locker showing high-payout offers can post a 6% completion rate and beat a locker at 30% on cheap offers, or lose to it badly. You cannot know which without dividing by total visitors.
Break it down by country and device in your statistics page. Nearly every publisher discovers the same thing: one geo and one device combination is carrying the page, and a second one is dragging it down badly enough to be worth excluding.
Locking indexed content. A search engine that cannot read your page stops sending you traffic, and the locker slowly starves the very source it depends on.
Running one template forever. The first template you picked is almost certainly not your best one. Test.
Ignoring mobile. For most publishers, mobile is the majority of locker traffic and the minority of locker revenue. The inline fragment method exists largely to close that gap.
Treating held conversions as lost. Conversions flagged for review are not deleted. They carry a hold period and approve automatically if nothing goes wrong. Read the review state before assuming a network shaved you.
Pick your single best download page. Not your busiest page, your most wanted one. Put a locker on it, choose the template that matches your site, point it at your own domain, and give it seven days of traffic before you change anything.
Create your ToroAds account to build your first locker, or read the SmartLink guide if you would rather start with something that needs no integration at all.
Continue reading from the ToroAds blog.
