TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What Is a Bot Farm? Definition and the Traffic Signs It Leaves

A bot farm is a coordinated set of automated accounts, scripts or devices that fakes real users at scale. How it differs from a botnet, what it is used for, and eight traffic signatures to look for with a worked example.

Lin Zhou Reviewed by Emma Collins Also called bot farms Last updated Nov 20, 2026 Glossary

Quick answer

A bot farm is a coordinated collection of automated accounts, scripts or devices run by one operator to imitate real users at scale, usually to fake clicks, visits, views, installs or followers. It differs from a botnet because the operator owns or rents the machines.

What is a bot farm?

A bot farm is a coordinated collection of automated accounts, scripts or devices, run by one operator, that imitates real users at scale. The purpose is usually to fake attention: clicks, visits, views, followers, installs or votes. Where one bot is a single program, a bot farm is the operation around many of them, including the servers, proxies, accounts and software that keep them running.

The terms around it are often confused, so it helps to fix them:

TermWhat it isWho or what does the workTypical aim
BotOne automated programSoftwareAny repetitive task, good or bad
Bot farmA coordinated group of bots, accounts or devices under one operatorSoftware, often on rented servers or real devicesFake engagement at scale
BotnetMany infected computers or devices controlled remotelyMalware on other people's machinesAttacks, spam, fraud
Click farmA bot farm or worker group focused on fake clicksScripts or paid peopleAd fraud, inflated clicks
Phone farmRacks of real phones driven by softwareReal devicesFake installs and app engagement

The main difference from a botnet is ownership of the machines. A botnet runs on devices its operator does not own; a bot farm usually runs on infrastructure the operator rents or owns. That matters for detection: a bot farm's traffic often comes from data-centre or proxy networks, while a botnet's comes from ordinary homes.

Owning a bot farm is not automatically illegal. What matters is what it is used for: testing your own site is legitimate, manufacturing fake reviews, fake ad clicks or fake political support is not.

What are bot farms used for?

  • Fake social proof. Followers, likes, reviews and video views bought to make something look popular.
  • Ad fraud. Fake clicks and impressions that drain a campaign budget or inflate a publisher's earnings.
  • Metric inflation. Visits and app installs generated to hit a target or sell a product on the strength of numbers.
  • Influence operations. In July 2024 the US Department of Justice announced the seizure of two domain names and the search of 968 social media accounts on X that it said formed an AI-enhanced bot farm run for a foreign government. The accounts used invented personas, were registered through private email servers, and were created with a software package the advisory named Meliorator.
  • Scraping and probing. Bots that read content in bulk or test pages and forms for weaknesses.

The case above shows the scale and the technique: a few operators, hundreds of accounts, each looking like a person. The same logic applies to website traffic, only with sessions in place of posts.

How much traffic is automated?

Automated traffic is now a large share of the web. The 2025 Imperva Bad Bot Report, which covers 2024, found that automated traffic made up 51% of all web traffic, the first time in a decade it passed human activity, and that bad bots alone were 37% of all internet traffic, up from 32% the year before.

Two cautions. First, this is a vendor report based on the vendor's own network, so treat it as an order of magnitude, not a measurement of your site. Second, most of that traffic never reaches an analytics script, because a lot of it is crawlers and API calls that do not run JavaScript; what you see in your analytics is only the part that does.

Traffic signatures a bot farm leaves in analytics

Bots are cheap to run but hard to make look like a varied human audience. Look for signatures that appear together, not for any one:

SignatureWhat you seeWhy a farm causes itHow it can mislead
One source or campaign dominatesA single UTM source or referrer suddenly contributes a large shareOperators work from one script and one tagA real campaign can also produce a spike
Spike with no causeSessions jump on a day with no launch or mentionJobs are run in batchesPress or social mentions do the same
One page and one secondAlmost all sessions are single page with a duration near zeroBots load and leaveSlow pages produce short sessions too
No interactionPage views but no scrolls, clicks or eventsScripts do not behave like readersContent that answers at a glance
Identical devicesSame browser, screen size and language in thousands of sessionsOne software profile cloned many timesA corporate network can be uniform
Flat clockTraffic at the same level through all 24 hoursMachines do not sleepGlobal audiences can be flat too
Network concentrationMany sessions from a few networks or hosting providersRented servers and proxiesOffices and mobile carriers also concentrate
Zero outcomesThousands of sessions and no conversionsNobody is buyingNew traffic sources start at zero

No single row is proof. Three or more together, on the same segment, is a strong case.

Worked example: how much a bot farm distorts the numbers

Sample data: a site had 10,000 sessions last month and 120 conversions. A segment of 1,200 sessions came from one UTM source called promo-x. In that segment 98% of sessions viewed a single page, the median duration was 1 second, and there were no conversions. The other 8,800 sessions had 45% single-page sessions and carried all 120 conversions.

GroupSessionsSingle-page shareConversionsConversion rate
Whole site10,00051.4%1201.20%
Source promo-x1,20098%00.00%
Everything else8,80045%1201.36%

The raw conversion rate is 120 ÷ 10,000 = 1.20%. Without the suspect segment it is 120 ÷ 8,800 = 1.36%, so the farm understated the conversion rate by 0.16 points: the reported figure is 12% below the real one (1.20 ÷ 1.36 − 1). If you pay for this source, 1,200 sessions bought nothing.

Count the signatures in the table: one source dominating (12% of sessions), single-page and near-zero duration, and zero outcomes. Three are present in the same segment, which is enough to treat it as suspect, and the other five (spike, interaction, device uniformity, clock, network) are worth checking before you block anything. A single spike on its own would not be enough.

Why detection is hard: farms that look like people

Detection works well on simple bots. Imperva's report names the tactics farms use to avoid it: residential proxies (so the traffic comes from ordinary home addresses), faked browser identities, headless browsers, AI-assisted scripting and anti-detection tools. A phone farm goes further by using real devices, so device checks pass.

That has a consequence for how you read your data. Detection of automated visitors can reduce the problem but never prove that the remainder is human. What cannot be faked cheaply is behaviour that costs money or effort: reaching a pricing page and then completing a purchase, signing up and returning on three separate days, a chat that makes sense. Judge segments by outcomes, not by labels alone.

What to do when you suspect a bot farm

  1. Isolate the segment. Find the source, campaign, landing page or network that carries the signatures, and look at it as a group.
  2. Check the outcome, not just the shape. If the segment has conversions or real conversations, it is not a farm, even if it looks unusual.
  3. Keep it out of the decisions. Report numbers with and without the segment so your conversion rate and bounce rate are not distorted.
  4. Stop paying for it. If the source is paid, pause it, and read the platform's policy on invalid traffic before disputing the charge.
  5. Block at the edge if it is hitting something sensitive. Rate limits, challenges and firewall rules belong at your CDN or web application firewall; analytics tools measure, they do not block.
  6. Write it down. Note the dates and signatures, so you recognise the next one faster.

Spotting a bot farm in TapCub

TapCub measures traffic; it does not block it. What it does is keep recognised bots out of your human numbers and let you look at suspicious segments.

  1. Check what is already excluded. New projects use Detect and report separately: recognised bots appear only under Web analytics › Bots and are not counted in human visitors, sessions or pageviews. All bots lists each one with its operator, purpose, requests, pages visited, most common status code, trust level and the detection layers it matched. See how bot detection works and are bots counted in visitors.
  2. Find the segment. Open Web analytics › Sources, scan the UTM source and referrer rows for the one that has jumped, and click it to add it as a filter. Only a hostname filter carries from one page to the next, so re-apply the source filter on Pages, Audience and Sessions (or keep the address that already has it) to check single-page share, duration, devices and entry pages for that segment alone.
  3. Check outcomes. Under Web analytics › Goals, see whether the filtered segment has any conversions, and compare with the whole site, as in the worked example.
  4. Set an alert. In All-platform analytics › Operations › Monitors, create a check on a built-in metric such as sessions, bounce rate or pageviews at an hourly or daily interval. A trial run shows how many times it would have fired over the last 30 days. Monitors only notify.
  5. Know the limits. With the page script alone TapCub sees only bots that run JavaScript, so crawlers that do not need server collection or a log import. Trust is verified, suspected or unknown, and unknown does not by itself mean a bot is spoofed. If a row is wrong, report a false positive.

For blocking, use your CDN or firewall. TapCub reports what happened; it does not stop it.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Lin Zhou

Product Experience Specialist

Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is a bot farm?

A bot farm is a coordinated group of automated accounts, scripts or devices under one operator that imitates real users at scale. It is used to fake clicks, visits, views, installs or followers, and to inflate the numbers someone is paid or judged on.

What is the difference between a bot farm and a botnet?

A botnet is made of other people's infected computers controlled remotely; a bot farm usually runs on servers or devices the operator owns or rents. Bot farm traffic often comes from data centres or proxies, a botnet's from ordinary homes.

How can I tell if bots are inflating my traffic?

Look for several signs in the same segment: one source or campaign suddenly dominating, single-page sessions near zero seconds, no interaction, identical devices and zero conversions. In the sample, 1,200 of 10,000 sessions with those signs made the conversion rate read 1.20% instead of 1.36%.

Is running a bot farm illegal?

Not automatically. Testing your own site is legitimate; using bots for fake reviews, fake ad clicks or fake political support is not. The legal risk depends on the purpose and on the laws where the operator and the targets are located.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics