What a cloaker actually does (and why paid traffic needs one)
Your account gets restricted and nobody explains why. Here is who visits your campaign page besides the buyer — and what changes when you decide who sees what.
It works, and then it stops working
You launch a campaign. It runs. Sales come in. And then, with no warning, the account is restricted — or the ad is rejected, or the page stops being served. The message you get is generic and never says what actually happened.
Most people conclude they did something wrong. Usually they did not. What changed is who was looking at the page.
One page. Very different audiences. Only one of them is there to buy.
The buyer is not your only visitor
A campaign page receives far more traffic than the people you paid to reach. It is worth being specific about who else shows up:
- Automated scanners that sweep pages continuously, with no connection to your ad.
- Spy tools that competitors use to find, copy and republish offers that are working.
- Reviewers opening the page out of context — from another country, on another device, without ever clicking your ad.
- Crawlers and archivers that store a copy of the page, sometimes permanently.
All of them see exactly what your buyer sees. That is the entire problem, and it is a structural one: a single page cannot behave differently for audiences it cannot tell apart.
What a cloaker does, in one sentence
The buyer sees the offer. Bots, spy tools and competitors see the safe page.
That is it. It is not a trick and it is not magic — it is control over who sees what. The web has always worked this way: a logged-in user and an anonymous visitor get different pages from the same address, and nobody finds that strange. A cloaker applies the same principle to paid traffic.
What it protects you from, concretely
Competitors copying your offer
A working offer is the most valuable thing you have, and it is sitting on a public URL. Spy tools exist specifically to find and clone it. The safe page is what they take home instead.
Automated traffic distorting your numbers
Bot traffic does not just waste budget — it poisons your data. Conversion rates look worse than they are, and you end up optimising a campaign against visitors who were never going to buy.
Your offer being judged out of context
A page written for one audience, opened by someone from an entirely different context, gets read in a way you never intended.
What changes when you use Vellar
Knowing what a cloaker does is one thing; having it actually work without becoming a second job is another. This is where Vellar is built differently:
- The decision keeps itself current. An AI updates in real time, so the protection does not go stale while you are busy running campaigns.
- The protected page is still fast. Typical delivery lands around 100 ms — protection that arrives late would cost you the sale anyway.
- You build the page in the same place. The editor lives inside the same account, so there is nothing to export, paste or integrate.
- Protected or open, per page. Not every page needs protection, and switching is one choice — not a migration between tools.
- One account, one invoice, one place to look when something needs attention.
You can see all of it on vellarfunnels.com.
What it works alongside
Protection multiplies what is already working. It sits alongside the other pieces of a campaign and makes each of them count for more:
- A strong offer reaches the people it was written for, instead of being read out of context.
- Good creative gets judged by buyers, and buyers are the audience whose opinion turns into revenue.
- A well-built funnel keeps its numbers clean, because the traffic flowing through it is the traffic you paid for.
- Your ad budget goes further, since more of it lands on people who can actually convert.
That is why protection belongs at the base of the campaign rather than as an afterthought — and why Vellar was built to have it there from the first page you publish.
Why the decision cannot be static
Whatever is scanning your pages does not stand still. What went unnoticed last month is recognised this month. Protection that is configured once and then left alone slowly stops protecting — and the worst part is that it fails quietly. Nothing breaks. The page still loads. You only find out through the results.
That is why, in Vellar, the decision is made by an AI that updates in real time. The protection keeps current on its own, without you having to revisit settings you should not need to think about.
Vellar carries six years in the cloaking market. Everything learned in that time — what changes, what gets recognised, what stops working and when — is what the AI now decides with, in real time, on every visit.
The words you will hear, in plain language
The vocabulary around this subject is heavier than the ideas underneath it. A quick translation:
- Paid traffic — visitors who arrive because you paid for the click, rather than finding you on their own.
- The offer page — what your buyer is meant to see: the product, the price, the button.
- The safe page — a normal, plain page shown to everyone who is not your buyer.
- Anti-bot filtering — separating automated visitors from real people.
- Campaign protection — the whole idea above, applied so the right audience gets the right page.
In Vellar all of this lives behind ordinary screens, with plain names and no jargon — you choose what each page should be and the app takes care of the rest.
Who benefits most from it
Anyone buying traffic at scale
The more you spend, the more every wasted visit costs you. Protection pays for itself fastest exactly where budgets are biggest.
Anyone with an offer worth copying
If your campaign is working, it is worth cloning — and the better it performs, the more attention it attracts. Protecting it is how the advantage stays yours.
Anyone running several campaigns at once
With many pages live, checking each one by hand stops being realistic. Vellar applies the decision across every page from a single account, so the protection scales with you.
Where to start
- Understand who is reaching your page today besides the buyer.
- Decide what each audience should see — the offer, or the safe page.
- Make sure the protected page still arrives fast, because a page that arrives late loses the sale anyway.
- Check the results, not the settings: protection is measured in what converts, not in what is switched on.
If you want to see how this looks in practice, the Vellar landing page shows the full picture, and the Help Center walks through setting up a first campaign step by step.
Six years on the battlefield, now decided by AI
Vellar brings six years in the cloaking market into a single app — cloaker, anti-bot filter and page editor together, with an AI deciding in real time.
See VellarPricing →Keep reading
Speed is part of protection: why delivery time decides the sale
Protecting the page is worthless if it arrives late. The click was already paid for — every instant of waiting is money already spent.
One place instead of three: cloaker, anti-bot and page editor together
Most operations glue three tools together and spend their time on the seams. Vellar put protection, anti-bot filtering and the page editor in a single app — protected or open, your choice, per page.