Every figureshows its working.
No scary industry numbers, no black box. Three steps, each one checkable, and a report that names what cannot be verified as plainly as what can.
Connect ad accounts.
Connect at manager level, once, in minutes. Every client account under it comes with it. Kliksight reads reporting and billing-level credit data from the platform; it changes nothing and blocks nothing, ever.
The tag observes arrivals.
One tag on each client’s landing pages observes what actually arrives from paid clicks. It is consent-gated and fails closed: no consent, no measurement. It sets no cookies and reads none, and detection runs nightly over the observations, computed carefully rather than in real time. Kliksight classifies events, never people, and never uses the word fraud about a visitor it cannot identify.
Every period, the reconciliation.
Every finding is checked against the platform’s own invalid-activity credits before it reaches a report. What was already filtered and never billed is excluded by construction. What is left is recoverable: detected minus credited, per client, in that client’s own report.
= recoverable
What we measure, and what we read.
Arrivals on your client’s landing pages, observed by the Kliksight tag, and Kliksight’s own detection over those observations. Nothing here comes from the platform.
Billing-level invalid-activity credits: the platform’s own ledger of what it charged and what it gave back. Credits, not refunds, and the report names them as the platform’s own figures.
“If you're using third-party tracking tools, take note that they may flag duplicate IP addresses or bot traffic that our systems have already processed and excluded from your billing.”
Google Ads Help, About invalid traffic (11182074)
The mechanic, plainly: the platform already filters invalid activity and credits it before billing. Any figure not netted against those credits double-counts what was never charged.
That warning is the reason the reconciliation exists. Kliksight is not click fraud detection. It is ad spend verification: every figure is stated net of the platform’s own credits, and where a platform publishes no billing-level credit figure, the report says the recoverable term cannot be computed. It never renders a guess. Reconciliation depth varies by platform, and each report states it per platform rather than averaging it away.
Why unnetted numbers are too big.
The common way to value invalid traffic. That figure counts clicks the platform filtered before billing and clicks it has already credited back. It is arithmetic on money that was never charged.
What Kliksight reports: what remains after both. The remainder is what can still be claimed, and it is usually small.
A small honest number is the one an agency can put in front of a client. The figure survives the client checking it against their own invoice, which is exactly what the big one cannot do.
Google reports what it credited. Not what it should have.
Google now publishes an account-level record of the invalid-activity credits it issued. That is one side of the reconciliation. Kliksight measures the arrivals independently, so the two figures can be compared, and packages what remains as a filing-ready claim inside the sixty-day window.
Kliksight never sits in the click path.
The tag observes arrivals on the advertiser’s own page, after the click has already landed. Nothing Kliksight runs can delay, redirect or break an ad.
Tools that intercept the click to block it must place their own domain between the ad and the landing page, and Google certifies those domains for exactly that reason. That certification governs redirect trackers; a landing-page tag is expressly out of scope in Google’s own guidelines. Kliksight is deliberately not one of them.
A tool in the click path is a dependency in your ad serving: when it goes down, the landing page goes with it. Not being in the path is a property of the design, not an absence.
We ran the whole method on our own money first.
Before asking for anyone’s subscription, we ran a deliberately small live campaign against our own account and put every stage through it: the tag, the detection, the reconciliation against the platform’s billing.
A click identifier is not a click, and an arrival is not a rate: the two counts above are different measures, and no rate is computed between them here, the same floor rule every report follows. The result was a clean report: detection found nothing the platform had not already handled, and the report said so. This is a methodology demonstration from our own verification record. It is not a market claim, and it predicts nothing about your accounts. A method that can say “nothing found” about its own money is the method you want checking your clients’.
kliksight.com currently sets no cookies of its own, so this notice asks for nothing. How the measurement tag behaves on customer sites is in the Cookie Policy.