Seatext library / BotRefund evidence
Switching from Blanket Lead Labels to Specific Dispositions: Workflow Changes for Meta Ad Campaigns
Moving from a single "lead" label to specific dispositions like verified, contacted, qualified, and disqualified changes how you collect data, train teams, build reports, and feed signals back to Meta. You'll need structured CRM...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Switching from a blanket 'lead' label to specific dispositions changes your ad campaign workflow in five places: data collection, sales follow-up, reporting, attribution, and the signal you send back to Meta. The change is not cosmetic. It turns a vague lead count into a measurement system the platform can optimize against.
What changes in your workflow
- Form and CRM schema update. Add a required disposition field with the exact picklist values your sales team will use. Lock the field so a lead cannot move to the next stage without a value.
- Sales process enforcement. Make disposition entry mandatory before any follow-up task is created. Managers should audit a sample weekly to confirm the picklist is used consistently.
- Reporting rebuild. Replace 'leads' with stacked bars: reported leads, verified leads, qualified opportunities, and revenue. Add placement, audience, creative, and device breakdowns so quality gaps appear in clusters, not averages.
- Attribution preservation. Keep the click ID (fbclid or gclid), campaign, ad set, creative, placement, timestamp, and URL parameters attached to every CRM record. Do not strip them when the disposition changes.
- Algorithm feedback. Use Meta's Conversions API or offline conversions to send only verified or qualified events back to the platform. Stop sending raw form submissions as conversion signals.
- Verification step. After two weeks, compare the new disposition distribution against the old single-label count. If verified leads drop but qualified opportunities hold, the system is working.
Why a blanket label hides the problem
A single 'lead' label treats a reachable prospect, a disconnected phone number, and a bot submission as equal. Meta's machine learning sees only the conversion event and optimizes for more of whatever triggered it. When invalid traffic poisons the pixel, the algorithm learns to buy more bot clicks. A high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement is a classic symptom of this feedback loop.
Specific dispositions break that loop. They let you tell the platform: count this, ignore that. The result is a cleaner optimization signal and a sales team that stops wasting time on contacts that will never convert.
This matters because Meta's default optimization can hide quality problems for weeks. The dashboard may show a steady cost per lead while the sales team receives unreachable contacts, copied messages, or enquiries that never progress. Dispositions expose the gap between raw volume and real opportunity.
Prerequisites before you flip the switch
- CRM supports custom picklist fields and required-field validation.
- Sales leadership agrees on the exact disposition definitions and will enforce them.
- You have a way to pass click IDs from landing page to CRM (hidden form field, URL parameter capture, or tag manager).
- You can send server-side events to Meta via Conversions API or offline uploads.
- Reporting tool (Looker, Tableau, Sheets, or Meta's own breakdowns) can join CRM dispositions to campaign metadata.
- You have enough form volume per campaign to see a consistent quality pattern instead of random noise.
Step-by-step implementation
1. Define the disposition picklist
Use a small set of values: verified, contacted, qualified, disqualified, duplicate, invalid details, no response. This set comes from a CRM lead-quality audit. Keep it small. Every extra value reduces compliance.
2. Add the field to the lead object
Make it required. Set the default to 'unassigned' so the system flags missing entries. Add a validation rule that prevents stage progression until a real value is chosen.
3. Capture click identifiers on every form submit
Store fbclid, gclid, campaign ID, ad set ID, creative ID, placement, and timestamp in hidden fields. Write them to the lead record at creation. Preserve the click identifier, campaign context, timestamp, URL parameters, CRM record, and any verification result before you change campaign settings.
4. Train sales on the new workflow
Run a 30-minute session. Show the picklist, explain each value, demonstrate the required-field block. Give managers a dashboard that shows disposition completion rate by rep.
5. Build the quality dashboard
Create a report that joins campaign metadata to dispositions. Columns: campaign, ad set, placement, spend, clicks, landing page views, form submits, verified, contacted, qualified, disqualified, duplicate, invalid details, no response. Add a calculated field: qualified rate = qualified / form submits.
6. Configure server-side feedback
In Meta Events Manager, create a custom conversion for 'qualified lead' (or 'verified lead' if volume is low). Send only those events via Conversions API. Turn off the pixel's standard lead event for this campaign or set it to optimize for the new custom event.
7. Run the verification check
After 14 days, pull the dashboard. Look for placement-level quality gaps. Quality normally changes by placement, audience, creative, device, geography, landing page, and time. A sudden gap in one cluster is more useful than a site-wide average.
Common mistakes and how to avoid them
Changing targeting before measuring is the most common error. Teams see a low qualified rate and immediately exclude a placement or audience. Avoid eliminating an entire audience from a small sample; use enough volume to see a consistent quality pattern. Wait until each cluster has enough data before making targeting changes.
- Sending raw form submits as conversions. Bots reach thank-you pages. Server-side events let you filter before sending.
- Dropping click IDs. Without fbclid or gclid, you cannot connect a disposition to the ad that produced it.
- Using too many disposition values. Sparse buckets make reports noisy.
- Letting sales skip the field. A mandatory field with manager review is non-negotiable.
How the four-layer audit fits the new labels
A four-layer audit maps directly to your new dispositions. Use it to decide where a lead falls and which layer should trigger an investigation.
| Audit layer | What it measures | Dispositions it validates |
|---|---|---|
| Platform delivery | Reach, link clicks, landing page views, placements, spend | Baseline volume for all dispositions |
| Landing page evidence | Page loads, redirects, consent, form start, completion time, engagement | Separates invalid details and no response from real submissions |
| Lead verification | Email deliverable, phone connects, duplicate check, interest confirmation | Verified, invalid details, duplicate |
| Sales outcome feedback | Dispositions: verified, contacted, qualified, disqualified, duplicate, invalid details, no response | All seven values — this is the source of truth |
Start with a quality baseline, not a theory. Calculate the normal rate for your account: landing-page sessions per click, contactable leads, verified leads, qualified opportunities, and revenue by campaign. A low-quality lead can be genuine but wrong for the offer. A suspicious session is a signal for investigation, not proof on its own.
Imperva reported that automated traffic represented more than half of web traffic in 2025. That does not mean half of a Meta advertiser's clicks are fraudulent. Treat broad industry statistics as context, then measure the quality of your own sessions and leads.
Key facts
| Fact | Detail |
|---|---|
| Disposition set | verified, contacted, qualified, disqualified, duplicate, invalid details, no response |
| Attribution fields to preserve | click identifier, campaign context, timestamp, URL parameters, CRM record, verification result |
| Quality clusters | placement, audience, creative, device, geography, landing page, time |
| Bot traffic signals | fast form completion, identical field structures, placement-level spikes, no page engagement |
| Pixel poisoning risk | Bots trigger conversion events, teaching Meta to optimize for non-human traffic |
| Refund success rate | 83% of one vendor's customers successfully get a refund from Google or Meta |
Limitations and when this advice does not apply
- Low volume accounts. If you get only a handful of form submits per month per campaign, the qualified rate will be noisy. Keep the blanket label until volume grows.
- No CRM or no click ID capture. Without a place to store dispositions and the original click data, you cannot close the feedback loop.
- Sales team refuses mandatory fields. If leadership will not enforce the picklist, the data stays dirty and the algorithm keeps optimizing for junk.
- Pure e-commerce with instant purchase. For direct sale funnels, the purchase event is already a strong quality signal. Lead dispositions add little.
- Accounts that only need refunds. If the goal is to recover wasted spend, you still need behavioral evidence. Dispositions alone do not prove bot clicks.
Hypothetical scenario: B2B software company
Acme SaaS runs Meta lead gen campaigns. They get 1,200 form submits a month. Sales calls 1,200 numbers; 900 are disconnected or wrong. The algorithm sees 1,200 conversions and buys more of the same cheap placement.
Acme implements the seven dispositions. Sales logs each call. After two weeks: 300 verified, 150 contacted, 80 qualified, 200 disqualified, 50 duplicate, 120 invalid details, 300 no response. They send only 'qualified' events to Meta via Conversions API. The algorithm shifts spend from the cheap mobile placement (80% invalid details) to desktop news feed (40% qualified rate). Cost per qualified lead drops 35% in month two.
This is the expected pattern when the feedback loop is clean. The exact percentages will vary by account.
FAQ
How many dispositions are too many?
Seven is the practical ceiling. More values reduce compliance and create sparse buckets. Start with the seven in the audit; merge only if a value stays under 2% for three months.
Do I need Conversions API, or can I use the pixel?
Use Conversions API. The pixel fires on the thank-you page, which bots also reach. Server-side events let you filter before sending. Client-side tracking alone cannot verify human consciousness.
What if sales won't log dispositions?
Make it a required field before the next task can be created. Tie a small bonus to completion rate. If leadership will not enforce, the project fails — accept the blanket label and its waste.
How long until the algorithm adjusts?
Meta needs enough conversion events to exit the learning phase. With only qualified events feeding back, expect the algorithm to stabilize over several weeks after you switch.
Can I use this for Google Ads too?
Yes. The same dispositions work with Google's offline conversion import. Send qualified leads with gclid and conversion time. Google's invalid activity credit system also benefits from clean disposition data when filing refund claims.
What about leads that go cold then revive?
Add a 're-engaged' disposition if it happens often. Otherwise, treat the original disposition as final and create a new lead record for the return visit with a fresh click ID.
Does this replace bot detection tools?
No. Dispositions measure outcome; bot detection measures behavior at the click. Use both. Detection layers such as ghost click, trap behavior, pointer behavior, motion behavior, speed behavior, path behavior, engagement behavior, and session behavior catch invalid traffic before it becomes a lead.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
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.