mass tort marketingMarketing Stops Where Firm-Controlled Intake Begins
An operational guide to moving a mass tort inquiry from an ad or landing page into a secure, structured, and review-ready intake record.
Mass tort marketing should end at a governed handoff into firm-controlled intake. The acquisition layer may preserve source, consent, and coarse prequalification signals and stays a routing layer. Sensitive facts, documents, qualification work, exceptions, and legal review belong in the structured intake record that can become the case record.
Marketing gets an inquiry to intake, then intake takes control
Mass tort marketing can create awareness and give a person a clear path to contact a firm. Its operational job ends when the inquiry enters mass tort intake. From that point, the firm needs a controlled record with defined fields, permissions, evidence states, criteria versions, and review ownership.
This boundary keeps acquisition work subordinate to case operations. Campaign performance can still be measured. The firm can still identify which advertisement, landing page, or referral path produced an inquiry, and none of that requires placing medical facts, legal narratives, uploaded records, or reviewer decisions in an advertising platform.
The firm's lawyers should approve the advertising content, outreach procedure, consent language, and jurisdiction-specific controls. ABA Model Rule 7.2 addresses communications about a lawyer's services, payment for permitted advertising, specialist claims, and identification of the lawyer or firm responsible for a communication. ABA Model Rule 7.3 defines solicitation and restricts specified person-to-person contact. They are model rules, and the rules and laws that govern a particular campaign still apply.
Fix the Costly Disconnect Between Ad Agencies and Intake Staff
Marketing agencies blame intake staff for poor conversion while intake staff blame agencies for bad lead quality. OBE bridges the gap with end-to-end attribution.
Define the handoff as a control table
A handoff should name what each layer may receive, what it must produce, and what it may not retain or send back. The following table is a system-design starting point. Firm counsel and privacy staff should approve the final configuration.
| Control point | Acquisition layer | Firm-controlled intake | Required record |
|---|---|---|---|
| Source | Campaign, ad, landing page, and referral identifiers | Original source plus normalized source fields | Identifier, source system, capture time |
| Prequalification | Coarse, firm-approved routing questions | Case-specific questions and explicit answer states | Question version and response source |
| Consent | Permission for the stated next action or contact channel | Separate permissions for intake activities | Notice version, response, time, channel |
| Sensitive facts | Do not request or transmit | Collect only in the approved secure workflow | Field state, provenance, access rule |
| Documents | Do not collect through the ad handoff | Request, receive, classify, and review | File source, request state, classification |
| Criteria | Campaign and landing-page version only | Approved qualification criteria version | Version, effective date, approval owner |
| Duplicates | Preserve source inquiry without merging | Compare, link, merge, or separate under policy | Match reasons and reviewer action |
| Exceptions | Route technical failures | Route identity, evidence, criteria, consent, and conflict issues | Reason code, owner, allowed resolution |
| Decision | No legal or engagement result | Authorized review and disposition | Reviewer, decision state, rationale fields |
The handoff event should be immutable. Later corrections can update the governed intake record while retaining the source submission and the original campaign context.
Capture source without making campaign data the case record
Give every campaign, ad, landing page, form version, and referral partner a stable identifier. At handoff, store those identifiers with the submission time and the source system. If a tracking value is invalid or missing, record unknown and leave the inquiry's source unassigned to the current campaign.
Keep original and normalized values separate. For example, an intake system may map several tracking labels to one governed channel category for reporting. It should still preserve the source label that arrived with the inquiry. That history lets operations staff investigate routing errors without treating a marketing label as a verified fact about the prospective claimant.
Source data also needs ownership. Marketing staff may own campaign definitions and naming. Intake operations should own the mapping from a handoff to an intake record. Authorized firm staff should own decisions about qualification, conflicts, legal merit, and engagement.
Keep the ad and landing page boundary coarse
Meta describes lead ads with forms as a way to collect information through an instant form or a form hosted on the advertiser's website. Each question still has to suit an advertising surface.
Before the secure handoff, ask only questions the firm has approved for discovery and broad routing. Examples may include preferred contact method, general matter category, geographic region at a non-sensitive level, and confirmation that the person wants to continue to the firm's intake workflow. The exact set depends on firm policy, campaign scope, applicable law, and platform rules.
Do not use the ad, tracking URL, or analytics payload to collect diagnosis, injury, treatment, medication, disability, detailed exposure, financial loss, legal narrative, government identifiers, insurance identifiers, or case documents. Those facts move to a secure intake workflow with purpose-based access and retention controls.
Treat prequalification as routing
A short quiz can direct an inquiry to the correct workflow. Coarse prequalification should produce a routing state such as continue_to_secure_intake, staff_follow_up, or outside_current_campaign, and any statement about a claim, compensation, or acceptance by the firm comes only from authorized firm staff.
The record should store the quiz version, the firm approval owner, the effective period, and the answers used for routing. A changed question creates a new version, and the configuration that governed earlier inquiries stays intact.
Deeper qualification belongs in the firm's mass tort intake qualification workflow. That workflow can compare structured answers and evidence with versioned, firm-approved criteria. Lawyers or authorized firm staff retain legal and engagement decisions.
Make consent specific to the next action
Consent should describe one purpose. The handoff record should show the notice text or version, the action offered, the person's response, the time, and the source. Permission to receive a call should remain separate from permission to receive text messages, submit records, sign documents, or take another action.
Meta's Lead Ad Terms place responsibility on advertisers for required disclosures, choice mechanisms, permissions, compliant use, and protection of lead data. The terms also restrict sensitive or prohibited collection and limit use or transfer to the purpose described at collection unless additional consent applies. The firm should review the current terms and its own legal obligations before launch because platform terms and campaign configurations can change.
If consent is missing or does not match the requested activity, stop that activity and create an exception. Do not repair the gap by inferring permission from an ad click, form completion, or contact field.
Inspect the Handoff and Callback Workflow
When an inquiry arrives, the OBE platform creates the intake record with its source and a callback task for a dedicated intake agent to work on the firm's schedule.
Move sensitive facts and evidence into secure intake
The secure handoff should create or locate one prospective-claimant record, then present the correct legal intake workflow. This is where the firm may ask case-specific questions, distinguish unknown from unanswered, request evidence, apply access rules, and retain correction history.
Evidence collection should start from a defined request. Record the requested document category, acceptable substitutes, request date, current status, and follow-up owner. When a file arrives, preserve the source channel, receipt time, original filename, submitter, classification state, and connection to the relevant fact or criterion. The mass tort document collection guide explains how to keep requests, provenance, gaps, and review states connected.
No evidence value or claimant narrative should be sent back to Meta Pixel, Conversions API, or another advertising analytics channel. Meta's Business Tools Terms govern data sent through tools that include Meta Pixel and Conversions API. The terms state that advertisers should not send health, financial, or other sensitive categories described there. Firm counsel and privacy staff should decide the final event and payload policy.
Measure coarse events without exposing the intake record
An acquisition report can work with a small approved event vocabulary:
landing_viewquiz_startedhandoff_to_secure_intakesecure_intake_completed
These examples name workflow transitions only. Do not place names, contact details, answers, diagnoses, products, injuries, evidence states, criteria results, or case facts in event names, URL parameters, custom fields, or user-defined payload data. Keep the advertising identifier on the intake record under an approved access rule. Do not send the intake record back through the identifier.
Separate acquisition reporting from intake quality reporting. Marketing may measure a handoff count by campaign. Intake operations may measure duplicate rate, missing-document rate, correction rate, exception volume, and review readiness inside the governed system. Joining those reports should use approved identifiers and access controls.
Resolve duplicates before creating parallel records
Multiple ads, devices, referrals, or return visits can produce repeated inquiries from one person. Run a duplicate search at the secure intake boundary. A possible match should enter an identity review queue. Do not let the campaign system silently merge records, and do not create a new case record for every tracking event.
A duplicate review should retain each source inquiry, the match reasons, compared fields, reviewer, action, and time. Permitted outcomes may include link, merge, keep separate, or request clarification. Shared contact information is a signal that calls for review before anyone treats it as identity.
Technical handoff failures also need named exceptions. Record expired links, invalid campaign identifiers, missing consent, unavailable workflow versions, duplicate candidates, and incomplete transfer states with an owner and allowed resolution. A general error status gives staff no safe next action.
Build a review-ready handoff
The endpoint is a review-ready intake file. It should contain the source record, notice and consent history, structured answers, question and criteria versions, evidence index, duplicate result, open exceptions, corrections, contact history, and provenance for material facts. The firm's mass tort intake process should carry that record through authorized review and, if accepted, into the case.
Readiness means the file has reached a firm-defined review state with known gaps visible. Staff and software can prepare the packet, route exceptions, and propose classifications. Lawyers and authorized firm staff decide conflicts, legal merit, representation, and engagement.
Do Not Get Scammed Twice: Statutory Fee-Shifting vs. Upfront Retainers
Marketing agencies and lead affiliates frequently push mass tort prospects into signing predatory retainer contracts that include upfront administrative retainers or screening charges.
Ethical plaintiff advocacy and multidistrict litigation standards dictate that all fees and costs are recovered on pure contingency through common benefit funds and statutory fee allocations against defending companies. Prospective claimants should never pay upfront retainers to have marketing leads transferred to a litigation firm.
OBE bridges legal marketing directly into firm-controlled intake pipelines, enforcing strict compliance boundaries and qualifying fee-shifting claims on contingency from the first click.
Test the boundary before campaign launch
Use fictional records to test a normal handoff, unknown source, missing consent, duplicate inquiry, expired workflow version, secure-link failure, and attempted sensitive analytics payload. Confirm that each scenario reaches the correct owner and that no blocked state can advance by changing a marketing field.
Then inspect the final record. A reviewer should be able to trace the inquiry to its source, see what the person was asked, identify the active criteria version, locate supporting evidence, and understand every unresolved exception. If that history remains split across an ad account, spreadsheet, inbox, and intake tool, the handoff is not governed.
Mass tort marketing earns its place in the system when it delivers a documented inquiry into controlled intake, where the firm can review, correct, and carry forward a structured, source-linked record.
Find the Right Intake Software and Developers for Your Firm
Tired of friction between your ad agency and your intake team?
👉 
Schedule a Consultation with Tim Ottowitz to Review Your Case Type
I will inspect your source-tracking connections, audit your handoffs from ad to intake, and show you how OBE keeps source and consent attached to every inquiry.