had to put proper age verification on one of my sites this week and conversion basically halved overnight. the checkout to verified step is where everyone drops, they hit the id or face scan and just leave. same offer, same traffic, same funnel otherwise. feels like the vendor i picked is too heavy for this audience. anyone running age verif right now that doesnt murder signups, or is this just the cost of being compliant in 2026?
first thing, log exactly which verification step loses them, the upload, the scan, the processing wait, or the retry. its almost never the whole flow, its usually one ugly step. a lot of vendors force a full id upload when a simple age estimate would clear most users, and that heavy step is what kills your rate. find the step, then you know what youre actually fixing.
are you offering more than one verification path? if not, add one today. a lot of people pass way better with a card check or a reusable digital id than a live face scan, and if you only offer the scan youre forcing your worst converting option on everyone. give two or three methods and let them pick, your clear rate usually jumps on its own.
a halved conversion the day you switch verification on is the vendor and the flow, not your traffic, so dont go re testing your funnel. the ones built for high volume consumer sites clear most people in seconds, the cheaper compliance focused ones add manual review and friction that makes real users bail. you probably bought a compliance tool when what you needed was a conversion focused one.
watch how it behaves on mobile specifically, thats where most of this traffic is and where id upload and face scan flows fall apart, camera permissions, bad lighting, slow uploads. if your drop is almost all mobile thats your answer, the vendor just isnt mobile first. a flow thats fine on desktop can be unusable on a phone and no funnel survives that.
every vendor oversells the invisible seamless pitch, then in production the pass rate is nowhere near the demo. the ones who get decent rates arent on some magic vendor, theyre the ones who pushed back and got the vendor to tune the threshold for their audience instead of shipping the default strict settings. ask for the config, dont accept the out of the box setup, thats where your conversion went.
dug into the step logs and ada was right, its the face scan on mobile doing almost all the damage, desktop is fine. adding a card check as a second path like sasha said and asking the vendor to loosen the threshold. rtbraj probably right too, i grabbed the compliance heavy one when i should have looked at the consumer grade ones. going to test both before i judge it.
good catch. set up an alert on verify completion rate per method so next time a vendor update or a threshold change pages you instead of you noticing a week of lost signups later. the lost conversion while you dont notice is the expensive part here, not the verification itself. the vendor you cant fully control, the detection lag you can.
saw a few others say the same about that style of vendor this month, seems the strict default is biting a lot of people. your multiple path fix is the durable one though, the vendor settings youll always be at their mercy on, but giving users a choice of method you can carry across whatever vendor youre on.
worth separating two things you are optimizing at once, the vendor pass rate and your legal exposure. the cheapest to pass flows are not always the ones that actually satisfy the law in the states that now require this, and a card check alone does not count as age verification in several of them. not legal advice, but check what your specific jurisdictions accept as a method before you optimize purely for conversion, or you can pass everyone and still be non compliant.
thats the part i half knew and was hoping to ignore. so the card check as a second path only helps me where its an accepted method, otherwise im just improving conversion on a flow that doesnt satisfy the rule. ok, that changes the plan, i need to split by visitor jurisdiction not just offer a universal second path.
and from the EU side the vendor choice is itself a data risk, you are routing a face scan or an ID document to a third party. not legal advice, but pick a vendor that verifies and discards rather than one that stores, because a breach of a pile of customer IDs is a far worse day than a dip in signups. the processor and privacy rules often bite before any regulator does.
yes, and that is exactly the right conclusion. geo detect, serve the accepted method per jurisdiction, and keep a record of which method verified each user. not legal advice as always, but the record keeping is the part people skip and it is the part that saves you if anyone ever asks how you verified a given signup.
from the buying side, before you blame the vendor pull completion rate by geo and device, not just overall. i bet the drop is concentrated, one or two geos on mobile doing most of the damage while desktop and your tier1 are basically fine. if so you dont need a new vendor, you need a better fallback method on the exact segment thats failing. dont rip out the whole stack over an averaged number.
source on anyone actually hitting the pass rates these vendors quote in the sales deck? because i have never seen production match the demo once. ask the vendor for a pass rate on real adult mobile traffic in your geos, in writing, and watch them get vague.
one thing nobody has flagged, whatever vendor you pick, make sure a failed verification doesnt also trip your fraud or chargeback tooling in a way that burns the customer. i had a flow once where a legit user failing the age scan got flagged as suspicious downstream and then couldnt retry cleanly. verification failure and fraud are different events, keep them separate.
from the design side, half the drop at the upload or scan step is pure UX, people dont know what a good photo looks like, the error messages are useless, and theres no progress indication so they assume it froze. before swapping vendors id fix the screen copy and add a sample image, ive seen that alone recover a chunk of the drop that everyone blamed on the vendor.
coming from nutra and sweeps this was the biggest adjustment, in mainstream you never had a mandatory friction step you couldnt optimize away. here you cant, its law, so the game is making the required step as painless as possible, not removing it. mentally reframing it from conversion leak to fixed cost of doing business helped me stop fighting it and start minimizing it properly.
lol every few weeks someone discovers age verification halves their signups and posts it like breaking news. not dunking on you nate, its genuinely brutal. the real answer in this thread is the boring one, multiple accepted methods plus a mobile flow that isnt a face scan. everyone wants a magic vendor, nobody wants to log which step fails.
fair hit, i was one of them, i almost swapped vendors blind before ada told me to pull the step logs. logging it took an afternoon and told me exactly where to spend, the face scan on mobile. doing the boring thing first would have saved me a week of panic.