Meta Ads conversion tracking for workers' compensation attorneys
Workers' compensation shares personal injury's economics — expensive clicks, valuable cases — with a tighter set of disqualifiers. What Meta Ads adds on top of that is a mechanical requirement: fbclid and _fbc have to reach the record that holds the money, because Meta can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in workers' compensation attorneys, and what Meta specifically needs to accept it.
Free30 minutesNo obligation
Specific to Meta × Workers' comp
Meta for workers' comp: screened leads, nothing about the injury
On Meta, send screened workers' comp leads and signed cases from intake and the case management system through the Conversions API, matched on fbc, fbp and hashed phone and email, with an expected case value. Optimize on the screened lead, not the raw form, and never send injury, employer, claim number or medical details.
Meta reaches injured workers who are not searching for a lawyer because they do not know they need one: someone on light duty whose benefits were cut, or whose claim was denied by the carrier. That makes Meta a demand-creation channel for workers' comp, with a larger unqualified share than search. Instant forms in particular collect a lot of people injured outside the firm's state or long past the reporting deadline.
So the raw form submission should never be the optimization event. Send Lead only after intake has confirmed jurisdiction, deadline and employer coverage, through the Conversions API against the Meta lead ID or the fbc captured on landing. Signed cases follow within days or weeks, which is often longer than Meta's 7-day click window, so they work better as a value signal and in reporting than as the bidding target. If you run Spanish-language campaigns, keep them in their own ad sets with the same screened event, so cost per signed case can be compared language by language.
Expect Meta to treat injury content as health-related, which can restrict what the dataset may receive. Check Events Manager for a restriction notice before building. In every case, URLs, event names and custom data should carry no body part, injury description, employer name, claim number or treating provider. A numeric value is enough for Meta to work with.
Meta · Workers' comp · what breaks
Why Meta under-reports for workers' compensation attorneys
- 01
Premium CPCs spent on unqualified calls
Jurisdiction, statute and coverage each remove a large share of inbound.
- 02
Case values treated as uniform
A minor strain and a permanent disability claim are not one conversion.
- 03
Long claim timelines outrunning windows
The fee resolves far past any ad platform's import window.
- 04
Fbclid and _fbc never reaches the record
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Meta · Workers' comp · the fix
What working looks like
Signed cases as the conversion
From the case management system, with an expected value by injury class.
Calls filtered on jurisdiction and statute
Before anything reaches a bidding algorithm.
Expected value by case type, documented
Rather than a settlement figure nobody can know yet.
Meta · Workers' comp · architecture
How Meta and workers' compensation attorneys actually connect
- 1
The conversion in workers' compensation attorneys
The money event is a signed case, valued at an expected figure agreed with the firm by injury class. Actual fees resolve years later and cannot drive bidding.
- 2
Meta Ads needs a click to match
event_name from the standard set with exact casing, event_time in seconds, a shared event_id, an action_source, and hashed user_data that was normalized before hashing. Purchase additionally requires value and currency.
- 3
The identifier: fbclid and _fbc
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
- 4
Where it gets sent from
The case management system — cases signed by execution date, by injury class, for the same window.
- 5
Deduplication and window
This is the mechanism that decides whether adding CAPI helps or doubles your conversions. Both the Pixel and the server event must carry the same event_id — the order or booking reference works best, because both sides can produce it without coordinating. A case difference in the event name alone produces two events even with a matching ID. Read the Deduplicated indicator in Events Manager over a full week, not one session. Meta's default attribution is a 7-day click and 1-day view. View-through is included by default, which is a large part of why Meta claims more conversions than your other platforms — that overlap is expected rather than a fault.
Meta · Workers' comp · events
The conversion map for workers' compensation attorneys
Four steps, with three separate disqualification gates.
| Event | What it means here |
|---|---|
| Tracked phone call | The dominant channel. Filter by duration. |
| Qualified call | Jurisdiction, statutory deadline and employer coverage confirmed. |
| Consultation held | Where the claim is assessed properly. |
| Case signed | The money event, at expected value by injury class. |
| Injury class | Carried on the conversion, because expected values differ widely. |
Meta · Workers' comp · diagnose
Diagnostic order — Meta · Workers' comp
- 01
Count records carrying fbclid and _fbc
- 02
Unfiltered call conversions
The defining waste in this practice area, given what CPCs cost.
- 03
Statutory deadlines disqualifying callers
A hard filter that no campaign targeting can see.
- 04
Employer coverage status
Decides viability and is unknowable from the ad.
- 05
Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Match quality is where most Meta accounts lose attribution, and it's almost always normalization rather than coverage. An email hashed with a capital letter, or a phone hashed with brackets, produces a perfectly valid hash that matches nobody and errors nowhere. Normalize first, then hash, and read the score per event rather than overall.
Meta · Workers' comp · prove
How it gets proven — Meta · Workers' comp
Source of truth
The case management system — cases signed by execution date, by injury class, for the same window
- Signed cases reconciled per matter against what each platform reports.
- The share of calls carrying a session measured, since phone is the funnel.
- Expected values by injury class agreed with the firm and documented.
- The qualification filter confirmed to run before anything is sent.
- The Deduplicated indicator and the per-event match quality score, both read over seven days read directly, not inferred from an upload succeeding.
Meta · Workers' comp · free audit
What we check in the free audit
- Count records carrying fbclid and _fbc
- Unfiltered call conversions
- Statutory deadlines disqualifying callers
- Employer coverage status
- Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Checked against
The case management system — cases signed by execution date, by injury class, for the same window
Free30 minutesNo obligation
Meta · Workers' comp · when not to buy
When you don't need this — Meta · Workers' comp
- If Meta already reports conversions that reconcile against the case management system within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry fbclid and _fbc.
- If you're advertising a business type Meta restricts data collection for — health being the obvious one — the parameters you can legitimately send are narrower, and that constraint should shape the build rather than be worked around.
Meta · Workers' comp · what we deliver
What gets built — Meta · Workers' comp
Click identifier captured with the number swap running early
Phone-led intake means a deferred script loses most of the funnel.
Carried into intake and mapped onto the matter
The hop where legal attribution usually dies.
Signed case fires the conversion
With the injury class and expected value.
Declined matters excluded
The majority of intake in this practice area.
Dispatch via the Conversions API
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
Written guarantee
95%+ tracking accuracy
Measured against The case management system — cases signed by execution date, by injury class, for the same window. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Meta · Workers' comp questions, answered
No. Too many fail jurisdiction, deadline or coverage checks. Send a Lead event only after intake screening and let Meta learn from those.
No. It is health information. Send an expected value as a number and keep the injury class in your own reporting.
Not at signing — they resolve years later. Use an expected value by injury class, derived from your own history and documented. That is an honest modelling assumption; a fabricated settlement figure is not, and it would also train bidding on noise.
Only qualified ones. Jurisdiction, statutory deadline and employer coverage each disqualify a meaningful share, and at workers' comp CPCs an unfiltered call conversion is the most expensive mistake in the account.
Not for the fee. It works for the signed case, which happens within days or weeks of the click and fits comfortably inside the import window. Report actual fees separately over the real timeline.
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
By reading the Deduplicated indicator and the per-event match quality score, both read over seven days and reconciling against The case management system — cases signed by execution date, by injury class, for the same window. An upload that succeeds is not an upload that matched.
More on Meta · Workers' comp
- Workers' compConversion tracking for workers' comp, measured in signed cases
- Google Ads · Workers' compGoogle Ads conversion tracking for workers' compensation attorneys
- TikTok · Workers' compTikTok Ads conversion tracking for workers' compensation attorneys
RELATED GUIDES
More for workers compensation attorneys: other angles on the same outcome
- Workers' compConversion tracking for workers' comp, measured in signed cases
- Meta · Debt reliefMeta Ads conversion tracking for debt relief and credit repair companies
- Meta · Title and escrowMeta Ads conversion tracking for title and escrow companies
- Meta · Booked call → closed wonHow to track booked call to closed won for Meta Ads
- Meta × Call RecordsHow to reconcile Meta Ads against your call tracking records
- Meta · InsuranceMeta Ads conversion tracking for insurance companies
- Meta · Criminal defenseMeta Ads conversion tracking for criminal defense attorneys
- Meta · Tax consultantsMeta Ads conversion tracking for tax consultants
Free · 30 min
Get Meta reporting what workers' compensation attorneys actually earn
WhatsAppFree30 minutesNo obligation
