Deception
Implied functionality
An ad or page pretends to be a tool, button or system message, so people click expecting something to happen that never does.
How it works
Implied functionality means dressing an ad up as something that works: a "Download" or "Play" button, a "Check your eligibility" form, a fake chat window, a countdown, or a warning styled like a message from the phone itself. The visitor clicks to use the feature and lands on a page of search ads instead.
The same trick appears on the lander when keyword links are styled as form steps ("Step 1: choose your age"), implying that answering leads to a result. The click is real, but it was obtained by pretending.
Who pays for it
Users are tricked; advertisers pay for people who wanted a function, not their product. Publishers lose accounts on both sides, since traffic platforms and search feeds each prohibit it.
Who does it, and why
Buyers looking for click rates that honest creative cannot reach, often on push notification traffic and pop traffic where system-style messages are common.
Warning signs
- Creatives containing buttons, progress bars, play icons or system alert styling.
- Landers with quiz or form steps that all lead to the same list of ads.
- Very short visits to advertiser sites after the click.
- User complaints or platform rejections mentioning "non-existent functionality".
Defences
- Ban interface elements in creatives unless the function truly exists on the landing page.
- Present keyword blocks as searches, clearly labelled, not as steps or answers.
- Screen pre-landers bought from templates; many carry these patterns built in.
An example
Illustrative: a push notification styled as a missed-call alert gets a 9% click rate against 1% for a plain ad. Of 1,000 people who tap it, almost all leave within seconds of seeing a page of links. The source looks nine times better on click rate and many times worse on every quality measure that the feed actually pays on.