FAQ
Clear answers about traffic quality and Botless.
Understand what the platform is designed to detect, how to roll it out, and what a traffic verdict can and cannot tell you.
Detection and verdicts
Invalid traffic is traffic that does not represent the intended or legitimate activity for a measurement or advertising event. It can include automated requests, accidental activity, manipulated behavior, and other traffic that should not be treated as a valid advertising interaction.
Botless is designed to classify signals associated with automation, known data-center and proxy infrastructure, unusual request velocity, and inconsistent browser behavior. Available signals depend on the integration and request context.
No. A verdict expresses the observed risk and supporting findings. It does not establish who caused the traffic, why it occurred, or whether a legal or contractual definition of fraud is met.
Use a policy that can monitor or challenge uncertain traffic instead of treating every result as a binary allow or block decision. Review patterns across multiple events before acting on a partner or source.
Integration and rollout
Botless is intended for request flows where a browser-side or server-side signal can be evaluated before or alongside an advertising decision. The suitable pattern depends on your latency, identifiers, and enforcement needs.
Usually not. Start in monitoring mode, compare findings with known outcomes, investigate exceptions, and then introduce enforcement gradually.
Use identifiers that help your team act on a result, such as source, campaign, placement, publisher, zone, or sub-identifier. Avoid sending personal data that is not required for the agreed integration.
Yes. Separating the classification from your decision policy allows teams to apply different actions based on source, placement, campaign, or other business context.
Operations and limitations
No system can guarantee complete detection or zero false positives. Browsers, traffic techniques, and network conditions change, and some signals may be unavailable. Results require monitoring and periodic review.
No. Botless can support operational traffic-quality decisions, but it does not replace contractual measurement, audits, accreditation, legal review, or a partner-required verification provider.
Segment the affected period by source, placement, geography, network, device, and verdict findings. Compare the change with deployments, campaign edits, and partner activity before changing policy.
Pricing is scoped around evaluated request volume, integration requirements, and support needs. The proposal defines usage, limits, features, and commercial terms.
Have a question about your traffic flow?
Describe the integration point and the decision you need to make. We will help you evaluate the fit.
Ask Botless