BOTREFUND Prepared for Dossier leadership · October 2026

What we do

We detect the bots in your paid traffic — and recover what they cost you. 15–25% of paid clicks are bots. One tag proves it, click by click.

One JavaScript tag. Seven days to your number. Credits from Google and Meta in 45–90 days. $0 upfront — if nothing comes back, you pay nothing.

Detect

One tag.

A JavaScript snippet through GTM or Cloudflare. Every paid click is scored on your site. No backend work, no checkout changes.

Prove

A file per click.

GCLID or fbclid, timestamp, device and TLS fingerprint, on-site behaviour — the evidence a platform reviewer accepts.

Recover

Claim and escalate.

We file with Google or Meta and stay on it. Credits post to your ad account in 45–90 days.

2,500+ad accounts audited on the same detection stack
$1.2Mrecovered for a global payments network
83%of claims approved by Google and Meta
Dossier × BotRefund · Confidential01 / 06

01 — The problem

A bot clicks. You pay. Nobody refunds you.

01

A bot clicks your ad.

Automated traffic — data centres, click farms, fake apps — clicks the same search and social ads you buy for customers.

02

Google or Meta charges you.

The click is billed like any other. At $250K a month, 15–25% invalid traffic is $37,500–$62,500 gone.

03

There is no sale. The charge stays.

No order, no lead, no customer. The platform keeps the fee, and the fake conversion teaches the algorithm to find more traffic like it.

Why the platforms don't just fix it.

Google and Meta filter some invalid traffic automatically. What they filter, what they credit, and what they can prove per click are three different things. Without a per-click evidence file, there is nothing to claim.

Dossier × BotRefund · Confidential02 / 06

02 — How it works

From one tag to money back.

What happens, and when.

Timeline from tag installation to recovered credits
When What happens What you see
Day 0 The tag goes live — one JavaScript snippet through GTM or Cloudflare. No server changes. No checkout work.
Day 1 Every paid click is scored on your site. Bot traffic appears in the dashboard.
Days 1–7 Each suspect click becomes an evidence file. GCLID or fbclid, timestamp, device, behaviour.
Week 2 The claim is filed with Google or Meta and escalated. A submitted claim with a named reviewer.
45–90 days The platform issues credits. Money back in your ad account.

You pay only when credits land.

Dossier × BotRefund · Confidential03 / 06

03 — The economics

What actually comes back.

Google and Meta spend only. At 19% invalid traffic and 83% claim approval.

Annual spend lost to bots and annual recovery, by monthly Google and Meta spend
Monthly Google + Meta spend Lost to bots / year Recovered from platforms / year
$100,000 $228,000 $189,240
$250,000 $570,000 $473,100
$500,000 $1,140,000 $946,200
$1,000,000 $2,280,000 $1,892,400

At $250K a month: $473,100 recovered in year one — about $39,425 a month.

Recovered spend is contribution margin, not revenue. At a 40% margin, $473,100 is the equivalent of about $1.18M in extra sales.

Then the compounding half. Once bots stop training the algorithm, the same budget typically buys 10–15% more new customers — or the same customers for 10–15% less. That part continues after the refund.

At 19% invalid traffic and 83% claim approval. Credits apply to spend you are already committed to. Your first week replaces both assumptions with measured numbers.

Dossier × BotRefund · Confidential04 / 06
Visa Global payments network

04 — The case

One script. Then the traffic they couldn't see.

A global payments network, already running an edge console, agreed to a single tag.

Install 1 tag · no server changes

One JavaScript tag through GTM or Cloudflare. No backend work, no checkout changes. Live the same day.

Detection 15% of traffic was bots

Their existing console had been seeing 5–6%. The tag found roughly double — traffic they could now act on.

Result $1.2M cash and credits returned

Conversion rate rose 35% once fake conversions stopped feeding the pixel and the bidding model.

“Our edge console showed only 5–6% bot traffic. After adding this system, we doubled the amount detected.”

VP Performance Marketing, global payments network
Dossier × BotRefund · Confidential05 / 06

05 — Second product

The second product: Google overcharged advertisers from 2017.

A different harm from invalid traffic — and a different payout: cash, not ad credits.

The claim

Auctions were rigged.

A federal court found Google illegally maintained its ad-tech monopoly, including Project Bernanke and Jedi Blue. Advertisers paid inflated prices as a result.

The process

Run by a partner law firm.

Google's terms bar class actions, so our partner files coordinated mass arbitration claims. BotRefund reconstructs the historical spend and overcharge as forensic expert of record.

The terms

2017 to today. Cash.

Google spend from 2017 onward. The partner works on contingency: no upfront cost, no out-of-pocket legal fees. About 18 months.

Separate from the invalid-traffic programme. Different harm, different claim — no double counting. You can run either, both, or neither, and we will say so if the spend does not support a claim.

Sergei Glukhov, Founder & CEO · [email protected] · +1 (856) 499-3049

Dossier × BotRefund · Confidential06 / 06