Seatext library / BotRefund evidence
How Experts Label Leads in Ad Traffic Analysis to Avoid Blanket Terms
Experts avoid blanket lead labels by using signal‑based criteria, a layered audit, and continuous refinement. They classify leads into groups such as valid, low‑intent, suspicious, and fraudulent based on contactability, timing, session behavior, campaign...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Experts in ad traffic analysis reject blanket terms like “good” or “bad” leads. Instead, they assign nuanced labels that reflect observable signals and downstream outcomes. This practice prevents mis‑attributing performance issues to the wrong audience and keeps optimization efforts focused.
Labeling starts with a baseline of normal performance for each campaign, then layers of evidence are added to decide whether a lead is worth pursuing, needs nurturing, or should be blocked as invalid.
Why blanket labels hurt campaigns
Broad labels hide variation. A campaign may appear to have a steady cost per lead while the sales team receives unreachable contacts or duplicated messages. Treating all low‑performing leads as fraud can discard real prospects who simply need more time or education. Conversely, labeling every lead as valid lets bots poison pixel data and skew bidding algorithms.
For example, a B2B software campaign might see a high volume of leads from a low‑cost placement. A blanket “bad” label would cut that placement. But after investigation, those leads may be genuine prospects from a different industry – they just need a longer nurture cycle. Without granular labels, the advertiser loses a valuable source.
In another scenario, a lead that fills a form in under two seconds might be flagged as fraud. However, if the user is using autofill and has visited before, the speed could be legitimate. Blanket rules would discard that lead. Experts use multiple signals to avoid these mistakes.
Core principles of expert lead labeling
Experts follow three principles:
- Use observable, measurable signals rather than assumptions. For example, instead of assuming a lead is bad because of a low conversion rate, check if the email domain is valid or if the phone number connects.
- Separate signal strength from final outcome. A signal like “form filled in 1 second” triggers investigation, not a verdict. It might be a red flag, but it could also be a returning customer using autofill. The label is only assigned after combining multiple signals.
- Update labels regularly as new data arrives from clicks, sessions, and CRM. A lead that starts as “suspicious” might become “valid” if the sales team later confirms contact. Labels should be dynamic, not static.
These principles ensure that labeling is evidence‑based and adaptable to changing campaign conditions.
Signal‑based labeling framework
Five signal groups guide labeling:
- Contactability: disconnected numbers, invalid email domains, repeated addresses, or an unusual concentration of one country code. For instance, a lead with a phone number from a region far from the target market is a red flag.
- Timing: several leads arriving in short bursts, forms submitted immediately after landing, or conversions concentrated at unusual hours. A burst of 20 leads in one minute from the same IP requires investigation.
- Session behavior: no scrolling, no field corrections, uniform click paths, and no meaningful time on the offer page. A session with zero scroll depth and a form completion time under 2 seconds is suspicious.
- Campaign patterns: a sharp lead‑quality difference by placement, creative, audience expansion, device, or landing page. For example, leads from Audience Network may have lower contactability than those from feed placements.
- CRM outcome: a high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement. This is the ultimate validation – if the CRM shows zero progress, the lead is likely invalid.
These signals are drawn from real‑world audit guidance (Signals worth investigating). Each signal is scored on a simple scale (0, 1, 2) based on severity. The total score determines the label.
Building a lead label taxonomy
Based on the signals, experts create a taxonomy that fits their business model. A common four‑tier structure looks like this:
- Valid: high contactability, normal timing, engaged session, consistent campaign patterns, and positive CRM outcome. These leads are passed to sales immediately.
- Low‑intent: contactable but shows weak engagement (short session, no corrections) and low CRM qualification. These leads are moved to a nurture sequence.
- Suspicious: mixed signals – e.g., good contactability but odd timing or uniform click paths – requiring manual review. A human checks the session recording or calls the lead to confirm.
- Fraudulent: multiple red flags such as impossible speed, invalid contact info, and zero CRM outcome. These leads are blocked from the CRM and reported to the ad platform.
Some experts add a fifth tier, “Duplicate,” for leads with identical contact details. This prevents double counting and wasted sales effort. The taxonomy must be customized to the business model. For a high‑ticket service, even a low‑intent lead might be worth a phone call. For a low‑cost product, only valid leads are worth pursuing.
Step‑by‑step process to apply labels
- Establish a baseline: calculate landing‑page sessions per click, contactable leads, verified leads, qualified opportunities, and revenue by campaign (Start with a quality baseline, not a theory). This gives a normal range for each campaign.
- Collect raw data: ad platform clicks, website sessions, form submissions, and CRM records. Use a data layer to capture click IDs, timestamps, and user behavior.
- Score each lead on the five signal groups using simple rules or a scoring model. For example, assign 1 point for each signal that exceeds a threshold. A lead with 4+ points is fraudulent.
- Map the score to a label in the taxonomy (valid, low‑intent, suspicious, fraudulent). Adjust thresholds based on historical data. If 10% of leads are fraudulent, the threshold might be set higher.
- Push the label back to the ad platform via click ID or custom parameter so optimization algorithms see the true quality. This prevents the platform from optimizing for invalid traffic.
- Review outcomes weekly: adjust thresholds, add new signals, and retire labels that no longer separate performance. For example, if “low‑intent” leads now convert as often as “valid” leads, merge the labels.
Practical scenario: A lead from a Facebook ad arrives with a form completion time of 1.5 seconds, no scrolling, and an email from a disposable domain. The scoring model gives 3 points (timing, session, contactability). The label is “fraudulent.” The lead is blocked from the CRM and a refund request is prepared using tools like BotRefund, which identifies non‑human traffic with 99% confidence and has an 83% approval rate on refund claims.
Verification and continuous improvement
Labeling is verified by checking whether the predicted label matches downstream results. For example, leads marked “fraudulent” should show near‑zero contact and revenue over a 30‑day window. If mismatches appear, the signal rules are refined. Experts also run a four‑layer audit (Use a four‑layer audit) to ensure platform delivery, landing‑page evidence, lead verification, and sales outcome feedback are all considered.
To measure accuracy, calculate precision and recall. Precision is the percentage of flagged leads that are truly invalid. Recall is the percentage of all invalid leads that were flagged. Experts aim for high precision to avoid false accusations, but also high recall to catch most fraud. If recall is low, add more signals. If precision is low, adjust thresholds.
Continuous improvement involves A/B testing labels. For example, randomly assign a sample of suspicious leads to either “valid” or “fraudulent” and track CRM outcomes. This provides empirical evidence for label refinement. Tools that provide compliance‑grade evidence, such as BotRefund, can automate this process by capturing session recordings and click‑level data.
Limitations and when the approach does not apply
This method relies on having access to session‑level data and CRM disposition fields. It is less effective for:
- Phone‑only campaigns where online session data is missing. In such cases, experts use call‑tracking data and manual verification.
- Markets with strict privacy rules that block client‑side tracking. For example, in the EU, you may need user consent to capture behavioral data. Use server‑side tracking as an alternative.
- Very low‑volume tests where statistical significance cannot be reached. With fewer than 100 leads, baseline calculations are unreliable. Use industry benchmarks instead.
- Multi‑touch attribution models where the same lead interacts with multiple channels. Labeling must consider the entire journey, not just the last click.
In those cases, experts fall back to aggregated metrics and manual spot checks while seeking alternative verification methods. For example, they might use a third‑party verification service that checks phone numbers and email addresses in real time.
Despite these limitations, the signal‑based labeling approach is the gold standard for ad traffic analysis. It turns vague impressions into actionable data, allowing advertisers to optimize campaigns with confidence.
Key facts
| Fact | Source ID |
|---|---|
| Start with a quality baseline, not a theory | S5 |
| Use a four-layer audit | S5 |
| Record whether an email is deliverable, a phone connects, duplicate details recur, and the prospect confirms interest | S5 |
| Signals worth investigating | S1 |
| BotRefund identifies non-human traffic on your site with 99% confidence, builds compliance-grade evidence for every flagged click, and negotiates refunds through the platforms' own invalid-traffic channels — an 83% approval rate across filed claims | S6 |
FAQ
Why not rely on platform‑provided quality scores?
Platform scores often aggregate many signals into a single number, which can hide the specific reasons behind low quality. Experts prefer granular labels that guide concrete actions.
How often should label thresholds be updated?
Review thresholds at least monthly or whenever a major change occurs in targeting, creative, or landing page. Sudden shifts in signal patterns trigger an immediate review.
What tools help automate signal scoring?
Many tag managers and analytics platforms allow custom JavaScript to capture timing, scroll depth, and field changes. These values can be sent to a scoring endpoint or stored as event parameters. Specialized tools like BotRefund can automate detection and provide refund evidence.
Is manual review still needed?
Yes. Suspicious leads that fall between clear thresholds benefit from a quick human check to confirm whether the signal pattern is a false positive or a new fraud tactic.
Does this approach work for offline conversions?
It works best when offline conversions are linked back to the original click ID via CRM or call‑tracking. Without that link, labeling relies on online signals only.
How do you handle leads that are 'suspicious' but later convert?
That is a sign that the labeling model needs adjustment. If a suspicious lead later converts, examine which signals were misleading. For example, a fast form fill might be due to autofill, not a bot. Update the signal rules to account for returning visitors or autofill detection.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.