Skip to content
Reportkey
KillBot
Website anti-bot protection

KillBot bot traffic report: requests, bots, share

KillBot sits in front of a website and separates bots from people. Reportkey takes its daily totals for each protected site and shows requests, bots, real users, and bot share in the report next to advertising and web analytics.

14 days free · no card required · all integrations
Sign up, connect your KillBot account on the integrations page, and pick a site in a project. Your first report in 5 minutes.
  • Requests, bots, and real users for each protected site.
  • Bot share by day, week, and month with change against the previous period.
  • Daily totals only, with no IP addresses or visit lists.
Sample Reportkey report with website traffic and goals
Sample Reportkey report with website traffic and goals
KillBotRequests, bots, and real users by day
30+
integrations
5 min
setup
14 days
trial
TL;DR

KillBot integration: connect your KillBot account once on the Reportkey integrations page and choose a protected site in a project. Requests, bots, users, and bot share by day, week, and month reach the client on schedule in one report with ads and Yandex Metrica.

Bot traffic report from KillBot

KillBot is an anti-bot service: it runs in front of a website, checks incoming traffic, filters automated visitors, and helps defend against application-layer DDoS attacks. Its account shows how many bots were stopped, but that figure lacks context. The client cares less about protection itself than about where the ad money goes and why analytics visits do not match leads. Reportkey adds KillBot daily statistics to a recurring report next to advertising and web analytics, so traffic quality is discussed on a single page.

Connecting KillBot to your report

Connect access to your KillBot account once on the Reportkey integrations page. Then pick the protected site in project settings: KillBot treats each site as a separate counter, and one account can hold several. Finally, select blocks, the period, and the delivery schedule.

If account access changes, the connection asks for updated details, while the chosen site and report settings stay intact.

Website traffic quality by day

The main block shows for every day:

  • requests, the traffic KillBot saw at the site entrance;
  • bots, the part the service classified as automated;
  • users, real visitors according to KillBot;
  • bot share, the ratio of bots to requests calculated by Reportkey.

These are separate counters of the service, so the report places them side by side without deriving one from another. Daily detail matters because spikes matter: a single scraping wave over a weekend can noticeably lift the monthly share.

Website bot share over time

The second block groups days into weeks or months and compares bot share with the previous period. You can see whether pressure on the site is rising, whether a change in protection rules helped, and whether peaks coincide with new ad campaign launches. With several sites, the same block is repeated for each one.

Click fraud report with Yandex Metrica and Direct

KillBot tags visits in Yandex Metrica as bot or not bot. In a Reportkey report it helps to place a Yandex Metrica block with visits and goals, a Yandex Direct block with clicks and spend, and the KillBot bot share together. When clicks and visits grow without leads and the bot share is above normal on the same days, the specialist gets a concrete reason to review placements and campaign settings.

Keep the boundary in mind: KillBot counts traffic at the entrance, while Yandex Metrica counts visits that reached the site. Absolute figures from the two systems will differ, so compare how they change.

What the report leaves out

Only daily totals enter the report. IP addresses, individual visit lists, and technical check details are never shown to the client. The report also does not translate filtered bots into saved money, because such estimates depend on the buying model and belong in a separate analysis.

KillBot alongside web analytics

Besides Yandex Metrica, Google Analytics and Top.Mail.Ru fit well next to bot data when the client checks traffic across several counters. Other web analytics sources are collected in the analytics group.

AI insights on traffic trends and report branding are not on every plan. A finished document example is the context agency demo report, and terms are on the pricing page.

Metrics

What goes into the KillBot report

These are the metrics that the KillBot integration already brings into Reportkey reports.

Checked requests
Bots
Users
Bot share
What this integration adds to the report
Requests, bots, and real users by day
Pricing

KillBot reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect KillBot to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from KillBot in client reports.

Pain points
  • The client sees a spike of visits without leads in web analytics and asks the agency whether the budget is going to bots.
  • Bot protection is in place, yet to show its effect to the owner a specialist takes screenshots from a separate account every month.
  • Bounce rate and time on site jump from week to week, and nobody can tell whether the audience changed or a wave of automated traffic arrived.
KillBot
A paid search agency

In a competitive niche the client needs to know how much site traffic is automated. A monthly report places ad spend, Yandex Metrica visits, and the daily bot share from KillBot side by side, so the click fraud discussion rests on numbers.

KillBot
An online store owner

Price scrapers and page-crawling bots hit the store regularly. A weekly report shows how many daily requests come from bots and how their share changes after protection rules are adjusted.

KillBot
A technical lead reporting on protection

The company pays for anti-bot protection and wants to see results. A monthly document shows bot and real-user trends for each protected site without access to the KillBot account.

Report preview

How KillBot appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey report with website traffic and goals
Sample Reportkey report with website traffic and goals
KillBot traffic quality block

Stacked daily bars of bots and users, a bot share line over them, tiles with monthly totals and the change from last month, and a per-site table below.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the KillBot connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Select the resource that should feed the KillBot report inside the project setup. Requests, bots, and real users by day
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need to connect KillBot?
Access to the KillBot account where your sites are set up. Enter it once on the Reportkey integrations page, then choose the protected site in a project. With several sites, each report project can show its own.
How are requests, bots, and users related in the report?
They are three separate KillBot counters. Reportkey shows each exactly as the service returns it, does not derive one metric from the others, and adds only the bot share of requests.
Why does the data differ from Yandex Metrica?
Yandex Metrica counts visits that reached the site and loaded its tag, while KillBot sees traffic at the entrance, before the site. The numbers do not and should not match. Compare trends instead: a rising bot share combined with visits that grow without leads is a reason to check the campaigns.
How often are statistics updated?
KillBot provides daily totals, and Reportkey loads them on every report build, on schedule or manually. Weekly and monthly values are summed from days. History depth is set by KillBot, so connect the site early if you want comparisons with past periods.
Will the report show how much money protection saved?
No. The report presents KillBot's classification as is and does not convert filtered bots into currency or saved budget. Such estimates depend on how the advertising is bought and are made separately.

KillBot bot traffic report: requests, bots, share

Sign up, connect your KillBot account on the integrations page, and pick a site in a project. Your first report in 5 minutes.

Start free