Bot Pageview Filter
Remove caller-classified automated and unknown traffic from pageview totals and quantify inflation.
Description
A bot-pageview filter separates supplied human-labeled counts from all other traffic classes.
A bot-pageview filter separates supplied human-labeled counts from all other traffic classes. Inflation is measured relative to retained human views.1
Remove caller-classified automated and unknown traffic from pageview totals and quantify inflation.
When to use Bot Pageview Filter
Use this tool to remove caller-classified automated and unknown traffic from pageview totals and quantify inflation.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Bot Pageview Filter and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter pageviews, trafficClasses using the field table and calculation rules, then run the tool.
- Read reportedPageviews, filteredPageviews, removedPageviews, inflationPercent. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| pageviews | Pageview counts | list of number | Required |
| trafficClasses | Traffic classes | list of string | Required |
Enter nonempty aligned nonnegative finite counts and labels. Trim/lowercase labels; only exact human is retained, all other labels are removed. Return retained, removed and inflation. With zero humans, positive removed views yield a 100 placeholder; all-zero counts yield zero.
inflation%=100removed/humanRetained Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| reportedPageviews | Reported pageviews | number; minimum: 0 |
| filteredPageviews | Filtered human pageviews | number; minimum: 0 |
| removedPageviews | Removed automated pageviews | number; minimum: 0 |
| inflationPercent | Reported-view inflation (%) | number; minimum: 0 |
{
"input": {
"pageviews": [
800,
150,
50
],
"trafficClasses": [
"human",
"bot",
"unknown"
]
},
"output": {
"reportedPageviews": 1000,
"filteredPageviews": 800,
"removedPageviews": 200,
"inflationPercent": 25
}
}Limitations and assumptions
No traffic is classified or blocked. Counts can be fractional, and the zero-human placeholder is not the undefined mathematical ratio.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Open-Rate Inflation: Adjust reported email opens for estimated machine-generated opens. For a complementary task, use Read Completion Rate: Calculate read completion rate from the supplied measurements.
References
-
Bot Pageview Filter — tool.io
Similar or alternative tools
- Open-Rate Inflation
Adjust reported email opens for estimated machine-generated opens.
- Read Completion Rate
Calculate read completion rate from the supplied measurements.