An aggressive cloak that looked safe and tanked my quality score

An aggressive cloak that looked safe and tanked my quality score

The cloak passed review. It also quietly destroyed my unit economics, and the dashboard never said why.

— The setup: grey-hat offer on a search source, cloaking the money page behind a safe page, $120/day.
— The move: I'd set the cloak too aggressive — bots and a big chunk of real users on certain ISPs saw the safe page too. I only caught it auditing my click-to-LP-view ratio.
— The numbers: I was paying for clicks, but 22% of real users were getting served the safe page (no offer) because my cloak's filter was too broad. My quality score dropped, CPCs rose 35%, and a fifth of my paid traffic monetized at zero. Before tuning: $120/day, $108 revenue, -10%. After narrowing the cloak filter: $120/day, $156 revenue, +30%.

— The lesson: a cloak that's too aggressive doesn't just risk bans — it silently eats real, paid traffic that you'll never see convert. The leak hides between 'click' and 'offer view.'

What I'd do differently: Monitor the click-to-money-page-view ratio from hour one. That 22% leak ran for ten days — roughly $260 of paid clicks served a page with nothing to buy. Figures illustrative; the over-cloak leak is a real and underdiagnosed killer.