Quick Answer
- Mass torts have defined class criteria. A qualifying page has to enforce those criteria before intake ever picks up the phone.
- The core filters are: product or drug name, exposure or usage window, documented injury or diagnosis, and, where relevant, documented medical treatment.
- Branching logic means each visitor answers only the questions that apply to their specific case type.
- Disqualified leads go to a soft-exit path, not a dead end. They become a retargeting audience.
- Landing page answers should map to CRM tags automatically through a webhook or native integration, not through manual re-entry.
- The optimization event sent back to Meta should fire on a qualified submission, not on every form fill.
Why Mass Tort Pages Need Harder Filters Than Single-Incident PI Pages
A car accident case has one primary screen: was the person injured, and were they not at fault? The qualifying window is wide. A mass tort case is the opposite. Every mass tort is built around a defined class, and that class has strict criteria around which product was used, how long it was used, what injury or diagnosis resulted, and sometimes the specific dosage or model number.
When a disqualified contact reaches intake, the cost is not just wasted call time. It is a signal sent to whoever is managing your ad account that this kind of contact is a conversion. If your Meta campaign is optimized toward form fills instead of qualified submissions, the algorithm will find more contacts who fill out forms. It will not know those contacts failed the class criteria, because you never told it.
A mass tort landing page needs harder filters than a single-incident PI page because mass torts have defined class criteria: exposure window, product name, dosage, and a documented injury or diagnosis.
The qualifying page is the place to enforce those criteria. Not the intake call, not the retainer conversation. The page.
This also applies to budget protection. Mass tort media tends to run at scale across Meta and Google, and disqualified traffic is expensive at scale. A page that lets anyone submit creates a queue of contacts that intake has to work through before finding a viable case. A page that filters first means intake's time goes to contacts who already passed the threshold.
For a deeper look at how RGDM structures landing pages for law firms, see our landing pages and CRO service page.
Exposure, Usage, or Diagnosis Window Questions That Cut Disqualified Traffic
The exposure window question is the first hard gate on most mass tort pages. Most active litigations define a date range during which the exposure, use, or diagnosis had to occur. A contact outside that window does not qualify regardless of their injury. Asking this question early prevents the rest of the form from being completed by someone who cannot be in the class.
Example: a qualifying page for a firefighting foam case might ask the visitor to confirm whether they were stationed at or worked at a facility that used the product, and to specify the approximate years of that work. A visitor who worked at the facility after the litigation cutoff date should be routed to a soft exit immediately.
For a pharmaceutical case, the equivalent is: did you take this medication, and during which time period? The page needs a date range selector or a checkbox set that covers the defined class window, not a free-text field that intake has to interpret.
The diagnosis question functions as a second gate. Most mass tort litigations require a specific medical diagnosis, not just symptoms. A qualifying page should ask the visitor to confirm whether they have received a formal diagnosis, and often which diagnosis, before allowing the submission to proceed. A visitor who checks "I have symptoms but no diagnosis" should be routed differently than a visitor who checks "I have been diagnosed by a doctor."
Note: which diagnoses qualify depends entirely on the specific litigation. The firm's attorneys need to define the qualifying criteria before the form is built. This is not a decision a marketing team makes independently.
Documentation Questions That Predict Case Viability
Once a contact passes the exposure and diagnosis gates, the documentation questions determine how fast the case can move and how much work intake will need to do before the attorney reviews it.
The most useful documentation questions at the page level are:
- Do you have medical records that reference the diagnosis?
- Do you have purchase records, prescription records, or proof of the product you used?
- Have you spoken with an attorney about this claim before?
These questions do two things. First, they give intake a head start. A contact who has medical records ready is a different conversation than a contact who has a diagnosis but no paperwork yet. Second, they give the CRM a tag that intake can act on before the first call.
A contact who answers "yes" to documented diagnosis and "yes" to existing records moves to the top of the intake queue. A contact who answers "yes" to diagnosis but "no" to any records moves to a follow-up sequence that walks them through gathering documentation before the qualifying call.
This is not about discarding undocumented contacts. In many mass tort litigations, documentation can be obtained later. The point is that intake's time is limited, and the contacts most likely to move through the intake process fastest should get the fastest response.
For a look at how AI lead response can handle tiered follow-up automatically, see the AI lead response service page.
Branching Logic by Product or Drug Name
If a firm is active in more than one mass tort litigation, the qualifying page cannot ask every question about every case in a single linear form. A visitor landing on a page about talcum powder litigation should not be asked about firefighting foam. A visitor landing on a page about a specific pharmaceutical should see the dosage question for that drug, not generic exposure questions that could apply to a dozen different cases.
Branching logic routes each visitor to only the questions that apply to their specific product or drug, so a Camp Lejeune claimant never sees questions written for a talc case.
Branching logic solves this at the form level. The first question identifies which case the visitor believes they have a claim in. The answers to that question determine which branch of the form they see next. Each branch contains the specific exposure window, diagnosis, and documentation questions for that litigation.
This structure also makes the page easier to maintain. When a litigation's class criteria change, or when a new litigation is added to the firm's portfolio, only that branch needs to be updated rather than the entire form.
From a platform optimization standpoint, branching also improves conversion quality. A visitor who reaches a page asking questions irrelevant to their situation will abandon the form. Abandonment on a qualifying page, if your Meta campaign is tracking form initiations, sends a negative signal. Keeping each visitor on a path relevant to their specific situation increases completion rates among qualified visitors, which is the only completion rate that matters.
See how RGDM structures Meta ads for law firms to drive traffic to case-specific qualifying pages rather than generic intake forms.
What to Do With Leads That Fail the Filter Instead of Discarding Them
A disqualified contact is not worthless. The person clicked an ad, visited a page, and started a form. That means they believed they had a claim. That intent is valuable even when the current case criteria exclude them.
Leads that fail the filter should never be simply discarded. They become a retargeting audience for related cases and a warm list for any future expansion of the class definition.
The soft-exit path for a disqualified lead should do three things:
- Tell the contact clearly and honestly that based on their answers, they may not qualify for this specific claim, and that eligibility criteria can vary. Do not tell them they have no case. That is a legal conclusion.
- Offer them a next step: a free consultation to discuss whether another claim might apply, or a way to be notified if the class definition expands.
- Tag them in the CRM with the specific reason they did not qualify (wrong exposure window, no diagnosis, wrong product variant) so that if the litigation evolves, the firm can contact them again.
Note on attorney-advertising rules: any language on the page about whether a visitor qualifies must be framed as a screening question, not a legal opinion. The ABA Model Rules of Professional Conduct and each state's rules govern how attorneys communicate about potential representation. The soft-exit copy should be reviewed by a supervising attorney before going live, and the disclaimer requirements differ by state. Do not generalize one state's rule to all jurisdictions.
From a media efficiency standpoint, disqualified contacts who opted in during the form process can be added to a custom audience in Meta. That audience excludes them from the main qualifying campaign (no point in paying to reach them again for the same case) while keeping them available for a different case campaign where they might qualify. This is a standard use of conversion tracking and custom audiences in a multi-litigation firm.
Connecting Landing Page Answers to CRM Tags Automatically
The intake call is the most expensive part of the case acquisition process on a per-contact basis. Anything that shortens the call or eliminates redundant questions protects that cost.
When a lead's answers map directly to CRM tags through a webhook, intake staff see case-specific context before they dial, which shortens the qualifying call and improves show rates.
Every qualifying question on the page should produce a corresponding CRM field or tag on submission. The implementation depends on which form tool and CRM the firm uses, but the principle is the same: the form submission fires a webhook or uses a native integration to write the contact's answers into the CRM record before intake ever sees the name.
The CRM record for a mass tort lead should show, at minimum:
- Which litigation they are claiming
- Whether they confirmed the qualifying exposure or usage window
- Whether they confirmed a formal diagnosis
- Whether they have documentation
- Whether they have previously spoken with an attorney
Intake's first call becomes a verification call, not a re-qualifying call. The staff member already knows the contact said they were diagnosed and have records. The call confirms those answers, gathers the contact's identifying information, and moves to scheduling. That is a shorter call, which means more calls per hour, which means more signed cases per intake FTE.
The CRM pipeline stage for a mass tort case should separate "submitted qualifying answers" from "intake confirmed answers" from "attorney reviewed" from "signed." If every new form submission lands in the same stage as a contact whose answers have been verified by intake, the pipeline loses its value as a management tool. For a look at how RGDM builds CRM pipelines for law firms, see the CRM automation service page.
Sending the Right Signal Back to the Platform
The final piece connects the qualifying page to the ad platform's learning algorithm.
Most mass tort campaigns are set up to optimize toward form fills or page conversions. The platform sees a submission as a success and goes looking for more people who will submit. If disqualified contacts submit the form at a high rate because the form did not screen them out, the platform's definition of "success" drifts toward disqualified contacts.
The signed-case signal sent back to Meta or Google should fire on a qualified submission, not on every page completion, so the algorithm learns to find people who match the class, not people who fill out forms.
The correct signal is a qualified submission: a contact who passed the exposure window check, confirmed the diagnosis, and completed the form. That event, and only that event, should be sent back to Meta through the Conversions API or to Google through offline conversion import.
Better still, the signal hierarchy should include a downstream event: a signed retainer, sent back to the platform after the case is retained. Meta's Conversions API and Google's offline conversion import both support delayed events. A signed-case event uploaded from the CRM tells the algorithm what a retained client actually looks like, at a level of precision that a form fill cannot approximate.
This is the full loop: the ad drives traffic to a qualifying page, the qualifying page filters by class criteria, the qualified submission enters the CRM, intake converts the contact, the signed case fires back to the platform, and the algorithm optimizes toward more signed cases. Each step depends on the previous one working correctly.
For a look at how RGDM implements this loop for law firms across practice areas, see the law firms industry page and the Meta ads service page.
Frequently Asked Questions
What qualifying questions belong on a mass tort landing page?
The core questions for a mass tort qualifying page are: which product or drug the visitor was exposed to or used, the dates of that exposure or use (to confirm they fall within the litigation's class window), whether they have received a formal diagnosis of the injury the litigation covers, whether they have medical documentation of that diagnosis, and whether they have any product or purchase records. The specific questions depend on the litigation. The firm's attorneys should define which answers qualify before the form is built.
How do you filter mass tort leads before intake calls them?
Filtering happens at two points. First, the qualifying page uses branching logic and hard-stop questions to prevent disqualified visitors from completing a submission. A visitor who answers outside the exposure window is routed to a soft exit before the form completes. Second, the CRM record created by each qualified submission includes the visitor's answers as tags or fields, so intake staff can see which criteria the contact met before making the first call. This turns the intake call from a re-qualifying conversation into a verification and scheduling call.
Should a mass tort landing page ask about exposure dates?
Yes. The exposure or usage date range is typically one of the defining criteria of the class definition in a mass tort litigation. A contact outside the date range does not qualify regardless of their injury, and allowing them to submit wastes intake time and degrades the optimization signal sent back to the ad platform. The date question should appear early in the form, before documentation or contact information questions.
What should happen when a visitor fails the qualifying questions?
They should be routed to a soft-exit page that explains, without making a legal conclusion, that their answers suggest they may not meet the current criteria for this specific claim. The soft exit should offer a next step, such as a free consultation to discuss other potential claims, and should capture enough contact information to allow the firm to follow up if the class definition changes. Disqualified contacts should be tagged in the CRM with the specific reason they did not qualify.
How does branching logic improve a mass tort qualifying page?
Branching logic shows each visitor only the questions that apply to their specific product, drug, or case type. A visitor claiming a pharmaceutical injury should not see questions written for a medical device or environmental exposure case. Keeping each visitor on a relevant path reduces abandonment among qualified visitors, improves the quality of the optimization signal sent to the ad platform, and makes the form easier to maintain when class criteria change.
Can disqualified mass tort leads be used for retargeting?
Yes, with appropriate handling. Contacts who began the form process and were disqualified based on their answers represent a warm audience that had enough intent to engage with the ad and start a form. They can be added to a custom audience in Meta and excluded from the current campaign while being made available for campaigns covering related litigations where they might qualify. Their CRM tag noting the disqualification reason also makes them reachable if the class definition expands.
How do landing page answers connect to a CRM automatically?
The form submission triggers a webhook or uses a native integration between the form tool and the CRM. Each qualifying question maps to a corresponding CRM field or tag. When the form is submitted, the contact record is created in the CRM with those fields already populated. Intake staff see the contact's case-specific answers before the first call without any manual data entry.
What is the correct optimization event for a mass tort Meta campaign?
The optimization event should be a qualified submission, meaning a contact who passed the qualifying questions and completed the form, not every form initiation or page visit. The event is sent to Meta through the Conversions API. If the firm's CRM tracks signed retainers, that downstream event should also be uploaded as an offline conversion, so the algorithm can optimize toward the profile of a contact who actually signed rather than a contact who merely qualified at the page level.
If you want RGDM to audit your current mass tort qualifying page or build the full loop from ad to signed case, book a free Case Acquisition Review.