Quick answer
Ad fraud is the deliberate creation of fake ad activity, such as clicks, impressions or installs, to collect money from advertisers. It is the intentional part of invalid traffic. In your analytics it shows as clicks that never arrive, near-zero engagement and no conversions from one source.
Formula: Invalid traffic rate = invalid clicks ÷ total clicks
What is ad fraud?
Ad fraud is the deliberate creation of fake ad activity, such as clicks, impressions, installs or conversions, to collect money from advertisers or to drain a competitor's budget. The wider category is invalid traffic: Google defines it as traffic that does not represent genuine interest in your business, and it includes accidents such as clicks caused by ads placed too close to navigation buttons. Fraud is the deliberate part of that category; the accidental part costs you money too, but nobody planned it.
For a site owner, the practical definition is simple: you paid for a visit, and no person who could ever buy came. Advertisers pay for clicks and impressions, so a click made by a script costs the same as one made by a customer. That is the whole incentive. TapCub does not buy, bid on or place ads, so this page is about what you can see after the click, in your own traffic data. Two related terms are the bot farm (a place that generates fake engagement at scale) and the botnet (a network of compromised devices run by an attacker).
Types of ad fraud and invalid traffic
The Media Rating Council splits invalid traffic into two tiers, and Google's help pages use the same split. General invalid traffic (GIVT) is caught by lists and routine checks; sophisticated invalid traffic (SIVT) needs deeper analysis.
| Type | Tier | What it is | What it tends to look like in your data |
|---|---|---|---|
| Data-center traffic | GIVT | Requests from servers whose IPs are tied to invalid activity | Sessions from hosting providers, no real browsing |
| Known crawlers | GIVT | Programs that declare themselves non-human | Named bots in the user agent; counted separately by good analytics |
| Irregular patterns | GIVT | Auto-refresh, duplicate clicks | Many near-identical hits in seconds |
| Automated browsing | SIVT | Scripts that do not declare themselves, such as botnet traffic | Sessions that look human at first glance; zero conversions at scale |
| False representation | SIVT | Ads shown on a different site, device or country than claimed | Traffic from a country you did not target |
| Manipulated behaviour | SIVT | Programs that trigger clicks or installs without consent | Clicks with no matching visit |
| Incentivised behaviour | SIVT | People paid to click | Real people, no interest, no purchases |
Google's Campaign Manager 360 help page lists these three GIVT and six SIVT categories (the table above merges the last two SIVT categories, misleading interface and undisclosed classification, into the rows that look most like them in your data). Other well-known forms, such as clickjacking (invisible ads that trick users into clicking) and ad stacking (several ads layered so only the top one is visible), appear in Google Ads' list of fraudulent placements.
How traffic data reveals it
Fraud is hard to prove from one number, but it leaves a pattern across several. Sample data: a campaign spent 5,000 on 10,000 clicks at 0.50 each, split over three traffic sources.
| Source | Clicks | Sessions seen in analytics | Arrival rate | Conversions | Spend |
|---|---|---|---|---|---|
| Search brand terms | 3,000 | 2,900 | 96.7% | 90 | 1,500 |
| Social campaign | 4,000 | 3,100 | 77.5% | 30 | 2,000 |
| Partner network X | 3,000 | 800 | 26.7% | 0 | 1,500 |
| Total | 10,000 | 6,800 | 68.0% | 120 | 5,000 |
Four signals stand out for network X:
- Arrival rate: clicks that never become sessions. Some gap is normal (people close the tab, scripts are blocked), but 26.7% against 77–97% elsewhere is not.
- Behaviour: almost no engagement, very short visits and a bounce rate near 100% on the sessions that do arrive.
- Zero conversions at a volume where the other sources convert.
- Odd concentrations: most sessions from one country, device model, hour of the night or hosting network.
Calculate the damage: reported cost per conversion is 5,000 ÷ 120 = 41.67. Without network X it is 3,500 ÷ 120 = 29.17, so the suspicious source inflates the cost per conversion by 41.67 ÷ 29.17 − 1 = 42.9%, and 1,500 of 5,000 (30.0%) of the spend went to a source that produced nothing.
A single signal can be innocent; low arrival can mean a slow page, and zero conversions can mean a bad audience rather than a bot. Treat three or more of the four signals together as a reason to ask the ad platform for an investigation, not as proof.
Formula and the cost of invalid traffic
Invalid traffic rate = invalid clicks ÷ total clicks. If 1,000 of the 10,000 clicks were invalid, the rate is 10.0%, and at 0.50 per click that is 500 of wasted spend. Google says invalid traffic caught before billing is removed from your costs, and invalid activity found after billing is credited in the next billing cycle where possible. Its investigation requests cover activity from the last 60 days, so check campaigns monthly, not yearly.
Common misunderstandings
- "A high bounce rate means fraud." Not by itself: a fast page with a clear answer also has high bounce. Compare with the same source on other days.
- "Bots are always caught by analytics." Declared crawlers are easy to separate. Bots that pretend to be ordinary browsers can still look like visitors, which is why source-level patterns matter.
- "The ad platform's number is the true number." Clicks are counted by the platform and sessions by your analytics; the two will never match exactly, so track the gap rather than demand zero.
- "Fraud only happens on cheap networks." It happens wherever there is money per click or per install.
What to send the ad platform
If the signals add up, send the platform a short evidence pack rather than a complaint: the date range (within the last 60 days), the campaign and source, platform clicks against analytics sessions, the arrival rate, engagement figures and the spend involved. In the sample, that is "network X, 3,000 clicks, 800 sessions (26.7%), no conversions, 1,500 spent". Ask for an invalid-activity review and keep your own table, because the platform's decision may take several business days and the numbers you recorded are the only copy of what you saw.
How to do it in TapCub
Run the network X example in TapCub:
- Tag every ad link with source and campaign parameters, then open Web analytics › Sources to see sessions by source and campaign next to your click counts from the ad platform.
- Compare the arrival rate by dividing sessions by platform clicks for each source.
- Check behaviour. Look at bounce rate, average duration and goals by source in Web analytics › Goals.
- See recognised bots. Web analytics › Bots lists crawlers TapCub identified, their operator, purpose and request count; they are kept out of visitor and conversion numbers. Bots posing as ordinary browsers are not identified this way, so the source-level signals matter.
- Import the spend. In All-platform analytics › Business › Channel ROI import cost by day, channel, source and campaign to see cost per click and cost per acquisition by source.
TapCub does not buy ads, block clicks or request refunds: it shows the pattern so that you can take it to the ad platform.
Sources
- Google Ads Help, About invalid traffic (definition, credits, 60-day investigation window).
- Campaign Manager 360 Help, Filtering invalid traffic to ensure quality (GIVT and SIVT categories).
- Media Rating Council, Invalid Traffic Detection and Filtration Standards Addendum (June 2020 update).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Customer Experience Consultant
Writes about live chat, visitor conversations, and self-service, sharing practical ways to make customer communication clearer and more effective.