Who it’s for
For lead gen

Fake leads from paid ads, traced to their source

A fake form fill costs you twice: the ad spend to capture it, and the sales time to chase a lead that was never a person.

How ValidVisit works →
What you get, exactly
Valid / Invalid
An auditable verdict on every visit, with its evidence.
48 networks
Attribution across the native, push and pop channels where invalid traffic concentrates.
No cookies
No device IDs, raw IP never stored — nothing heavy for a blocker to trip.
01 / THE PROBLEM

You already know this.

  • Bot and incentivized form fills inflate lead volume and crater close rates.
  • You pay per lead for traffic you can’t verify at the source.
  • Sales chases junk while the CRM fills with noise.
02 / WHAT YOU GET

Every visit judged, and the source behind it.

Detect, judge and attribute — with the evidence to act. The verdict never touches your traffic and we never claim recovered dollars; you see what’s real and decide what to cut.

  • Judge the visit behind every lead Valid or Invalid and attribute it to the source, campaign and publisher that sent it.
  • Separate valid from invalid before the noise reaches the data your funnels optimize on.
  • Renegotiate with lead sources on evidence — a per-visit quality record, not a gut feeling.
03 / HOW IT FITS

How ValidVisit fits the way lead-gen advertisers work.

Why paid ads attract fake leads

  • Bots that fill forms. Scripts submit any form they find, sometimes with real people’s details. Google’s own help says its invalid-traffic filters “don’t prevent invalid leads on their own” and calls lead quality “a shared responsibility” (Google Ads).
  • Paid humans. Click and form farms send real people to fill forms with no intent to buy.
  • Per-lead incentives. Publishers, affiliates and traffic vendors paid per lead have a reason to send volume over quality, including recycled or resold contact details.
  • Low-friction forms. Both platforms say their shortest forms trade quality for volume: Google’s “More volume” lead forms may include people who are less interested, and Meta’s “Higher intent” forms add a review step before submitting.

What Google and Meta offer against fake leads

Both platforms have form settings that trade volume for quality:

  • Google Ads lead forms: choose “More qualified” over “More volume” for an extra step and fewer, more interested leads (lead form types). Google also recommends reCAPTCHA, double opt-in, server-side validation and bidding toward qualified or converted leads.
  • Meta instant forms: the “Higher intent” type adds a review-and-confirm step, and Meta offers phone verification by one-time code and conditional questions.
  • Forms on your own site: reCAPTCHA, double opt-in and server-side checks on emails and phone numbers.

These make a fake lead harder to submit. None of them tells you which campaign, publisher or placement keeps sending them, and that is what decides where the next dollar goes.

The cost of a fake lead

  • High CPCs. Legal, insurance, home services and finance carry some of the most expensive keywords in search, and patterns consistent with competitor clicking concentrate on exactly those terms.
  • Double cost. You pay for the click, and if an automated session completes the form you pay again in sales time chasing a lead that was never a person.
  • Form bots and incentivized fills. Scripts that fill any form they find, and publishers paid per lead with a reason to send volume over quality.
  • CRM pollution. Fake leads distort conversion data and lead scoring, so the whole funnel optimizes on bad inputs.

The visit behind every lead

A lead in your CRM tells you what someone typed. It doesn’t tell you whether a person typed it. ValidVisit judges the visit that produced the form fill Valid or Invalid, with its evidence, and attributes it to the keyword, campaign, publisher and sub-source behind it.

Send each lead to ValidVisit by server-side postback and the conversions report shows which leads came from Invalid visits. That’s the list to check before sales picks up the phone, and the list to keep out of the conversion signal your bidding learns from.

Lead-quality disputes, on evidence

Whether you buy leads from publishers and affiliates or sell them to a buyer, quality disputes usually come down to one side’s word against the other’s. A per-visit record changes that conversation: this source, these leads, the verdict on the visit behind each one, with evidence in your dashboard.

Use it to renegotiate a source’s terms, cap it or drop it. On ad networks that credit invalid traffic, the same record supports the request: what each network’s terms say about refunds.

A weekly routine

  1. Tag every source: UTMs for search and social, the network’s own tokens for native, push and pop (tracking-token directory).
  2. Add the script to every landing page that hosts a form.
  3. Post leads back to ValidVisit server-side, so each lead is tied to its visit.
  4. Review sources worst-first by the share of leads from Invalid visits, not by lead volume.
  5. Act where you buy: exclude placements, tighten targeting, or take the record to the lead source.
For lead-gen advertisers

Trace every fake lead to the campaign and source that sent it.

  • Judge the visit behind every lead Valid or Invalid and attribute it to the source, campaign and publisher that sent it.
  • Separate valid from invalid before the noise reaches the data your funnels optimize on.
  • Renegotiate with lead sources on evidence — a per-visit quality record, not a gut feeling.

Just your email · no card · unsubscribe anytime · privacy policy

How it works →
deal-alerts.example71% invalid
zone 447123% invalid
premium-news.example2% invalid

Questions, answered.

What are fake leads?+
Form submissions from paid traffic that will never become customers: bots filling forms, paid humans with no intent, recycled or resold contact details, and accidental submits from low-friction forms. Each one costs the ad spend that produced it and the sales time spent chasing it.
Why am I getting fake leads from Google or Facebook ads?+
Usually one of four reasons: bots that fill any form, paid click or form farms, sources paid per lead that favour volume, and forms short enough to invite low-intent submits. Google says its invalid-traffic filters don’t stop invalid leads on their own, so form settings and your own checks matter, and so does knowing which source sends them.
Can it tell a real lead from a bot form fill?+
It judges the visit that produced the lead Valid or Invalid, with evidence in your dashboard. An Invalid verdict flags a lead worth scrutinising before sales spends time on it.
Does it integrate with my CRM?+
The verdict and attribution run on the visit; conversions and lead events flow through the same postback the rest of the product uses. There are no CRM connectors; leads reach ValidVisit through that postback.
Should I reject leads from Invalid visits automatically?+
That’s your call, and review before rejection is the safer start. An Invalid verdict is strong evidence a lead needs checking, not an instruction to delete it; routing those leads to a review queue keeps a rare real prospect from being thrown away.
Does it stop competitors from clicking my ads?+
No. It doesn’t block clicks or exclude anything in the platform. It shows which keywords and campaigns send Invalid visits, so you can adjust targeting or file an invalid-click report with the network. More on competitor clicking.
Why is lead gen hit harder than other models?+
Lead-gen keywords are among the most expensive in search, so each invalid click costs more, and the harm doesn’t stop at the click: a fake form fill becomes a junk lead that wastes sales time and skews your CRM data.
deal-alerts.example71% invalid
zone 447123% invalid
premium-news.example2% invalid

Judge your paid traffic for lead-gen advertisers.

Every visit judged Valid or Invalid across 100+ data points, attributed to the source that sent it.

Just your email · no card · unsubscribe anytime · privacy policy

Join the waitlist with just your email · 7-day trial at launch

One script · no cookies · no device IDs · raw IP never stored