Savings Methodology

How Bot traffic ad-cost equivalent is calculated

Distinguishing internal classifications, current-CPC estimates, and verified outcomes.

Last updated: 2026-09-14

Estimated ad spend prevented

Reference estimate: assumes one click prevented per eligible Bot browser

An estimate assuming one prevented ad click per eligible Bot browser linked to an ad platform. Active exclusion settings in the platform are required.

Calculated as eligible Bot browsers × one click × CPC at calculation time. Repeat links from the same site/browser and the same platform click ID are deduplicated within 24 hours, including links to multiple platforms. Visits need a recorded source click ID and platform connection. Sites are counted separately, then added in the all-sites view.

Uses the configured platform or site CPC, ¥100 when unset, and ¥0 when explicitly set to zero. The first CPC recorded for each hourly calculation is retained, so later CPC changes do not revalue history.

Updated hourly, including delayed records through the next day. The estimate covers matched records and shows their date range. It uses click IDs as a reference, not a measurement of actual ad clicks.

1. Why we show a reference value

Bot-classified visits are valued at current CPC as a reference under consistent assumptions.

Visits are not platform-billed clicks and include visits not confirmed as paid ad traffic.

This is a reference conversion of Bot visits at current CPC, not actual spend, savings, refunds or a guaranteed upper or lower bound.

2. Formulas

Bot traffic ad-cost equivalent = Σ(site Bot visits × current site CPC)
  • Each visit is counted once using its latest verdict. Normal + suspicious + Bot visits = total visits. Official crawlers are excluded from totals and Bot-rate calculations.
  • Site CPC is the stored setting: manual or the last retained Google Ads automatic value. A missing sync timestamp does not prove retrieval. Unset CPC defaults to JPY 100; explicit zero remains zero.
  • Per-site estimates are summed. Source reports use current platform CPC, then site CPC, then ¥100; their amounts may differ from the overview. CPC changes revalue history.
  • Bot detection, connection to an ad platform, platform acceptance and ad exclusion are separate stages. This reference amount does not show successful delivery or actual savings.

3. What these figures assume

Current-CPC estimates are not historical ad spend. Historical CPC is not retained.

Bot visits are not pixel sends or Google Ads IP exclusions. Legacy IP-register reference values are excluded from primary outcome metrics.

No CPC error bound has been established. Campaign prices and traffic mix affect differences from actual costs.

Unknown and non-ad sources are included; all Bot verdicts cannot be treated as paid invalid clicks or losses.

Platform invalid-click counts and AdFraud verdicts are different measurements. Unreconciled figures are not added as outcomes.

4. Evidence stages and further verification

See how to check detection, ad-platform connections and advertising results.

Level 1 — read the dashboard number

Reconcile stored verdicts with displayed counts, periods and formulas.

Level 2 — Check platform receipt and exclusions

Check event receipt, audience membership and ad-set exclusions separately. Platform invalid clicks are not automatically our product's outcome.

Level 3 — compare CPA before vs. after sync

Before/after CPA is descriptive. Budget, bidding and seasonality can change; improvement alone does not establish product impact.

Level 4 — Compare campaign groups

Assess cost or delivery differences using a comparison study with predefined population, period and method. Platform changes are decided by advertising operators.

5. Update cadence

  • Read today and yesterday from latest visit verdicts and older dates from daily aggregates at one snapshot. Follow-up replaces the verdict for the same visit.
  • Primary counts and values share one reporting snapshot. Media delivery and synchronization use separate evidence records.
  • A CPC change recalculates historical values after the shared cache refreshes, within five minutes. Methodology details show the setting source and retrieval timestamp.
  • Google invalid clicks: updated hourly
  • Main counts may be up to 5 minutes old; detection details may be up to 15 minutes old. Check the displayed retrieval time. An open page is not continuously updated.
Read the Technical BriefContact sales