11 — RETRICS VETO

Same orders.
Fewer lies in the
denominator.

Veto refuses the sessions that were never people — before they reach your analytics, your pixels and the rate you make decisions from.

Why the category fails →

BUILDING

ReconciliationAGAINST THE STORE’S OWN ORDERS

SESSIONS RECORDED48,210

REFUSED — NOT PEOPLE−9,140

SESSIONS THAT WERE PEOPLE39,070

ORDERS — UNCHANGED612

REPORTED BEFORE1.27%

WHAT YOUR HUMANS DO1.57%

DEMO STORE · THE ORDER COUNT NEVER MOVES — ONLY THE DENOMINATOR

THE CATEGORY IS SPLIT, AND BOTH HALVES ARE WRONG

A blocked count cannot be checked. An order can.

Most tools here report how much they blocked and stop. Veto is Shopify-native, keeps per-session evidence, and reports every number against the store’s own orders.

THE CHEAP HALF

IP and country blockers

Bypassed by anything with a residential proxy, and confident enough to refuse real customers who happen to be travelling. A blocklist cannot tell you which of the two it just did.

THE EXPENSIVE HALF

Off-Shopify click-fraud tools

They watch the ad click and never see the order, so they can report a saving without knowing whether anything sold. A number that cannot be checked against revenue is a number about nothing.

01 — THE VERDICTBUILDING

Refused before it counts, not deleted after.

A refusal is not a guess with a confidence score attached. It is a set of named signals and the verdict they produced, kept together — so the session never enters analytics, and you can still see exactly why it did not.

Session 8f21c4REFUSED

Datacentre ASNknown cloud range

Headless runtimeautomation flags present

Pointer entropyno human variance

Session depth1 page, 0.4s

Checkout reachednever

DEMO SESSION · FIVE SIGNALS, ONE VERDICT — AND THE VERDICT IS STORED WITH THEM

02 — THE EVIDENCEBUILDING

The only refusals worth trusting are the reversible ones.

Every refusal keeps its reason, which means a false positive is a thing you can look at rather than a thing you argue about. A flagged session that behaves like a person is let through, and that release is recorded too.

Evidence trailPER SESSION

STORED

The reason, not just the outcome

Every refusal keeps the signals that produced it.

REVIEWABLE

A false positive is a thing you can look at

Not a thing you argue about with a support agent.

REVERSIBLE

Released when it is wrong

A flagged session that behaves like a person is let through — and the release is recorded too.

A REFUSAL YOU CANNOT INSPECT IS A BLOCKLIST WEARING A BETTER NAME

03 — WHAT IT PROTECTSBUILDING

Three places a fake session does real damage.

A session that was never a person costs you three times: once in the rate you decide from, once in the signal your ad platforms learn from, and once in the audience you pay to reach. Veto withholds it from all three.

Where the 9,140 never arriveWITHHELD

Your analyticsThe conversion rate you make decisions fromCUT

Your pixelsThe signal ad platforms optimise towardCUT

Your audiencesThe lookalikes you pay to reachCUT

DEMO STORE · REFUSED BEFORE IT COUNTS, NOT DELETED AFTERWARDS

QUESTIONS

The four we get asked.

What happens if it refuses a real customer?

The session is kept with the signals that produced the verdict, so you can look at it. A flagged session that then behaves like a person is released, and the release is recorded as well. A system that cannot be wrong in public is not one you should trust.

Does this slow the storefront down?

Veto is Shopify-native rather than a proxy in front of your store, so there is no extra hop between a shopper and your theme.

Why not just report how much was blocked?

Because a blocked count cannot be checked against anything. The order count can. Every figure Veto reports is stated against your store's own orders, which is the only number in this category that a merchant can independently verify.

Can I use it today?

Not yet — Veto is building and is not on the App Store, so there is no price to quote. If bots are eating your ad budget now, tell us about the store and we will open it to you first.