ssdi

SSDI Marketing Reports: Tracking Which Ads Produce Approved Cases, Not Just Leads

Learn which SSDI marketing report metrics actually matter: cost per approved case by ad set, denial-rate signals, and cohort tracking across the multi-month SSA timeline.

Quick Answer

  • Lead volume tells an SSDI firm almost nothing about which ads are working.
  • The Social Security Administration's processing timeline makes a monthly snapshot report structurally misleading for disability cases.
  • The metric that matters is cost per approved case, broken down by ad set and traffic source.
  • That metric is only possible if a click ID lives on every lead record from the moment the form is submitted through the SSA decision stage.
  • Denial-rate patterns by source are a reportable signal that belongs in the marketing report, not just in the case file.
  • Approved-case events sent back to Meta and Google via the Conversions API shift platform optimization toward the right outcome.

Why Lead Volume Is the Wrong Headline Metric for SSDI Campaigns

Most marketing reports for law firms lead with leads. This month: 84 leads. Last month: 71 leads. Trend: up.

For a car-accident firm, that number connects to revenue within weeks. A signed case often moves to resolution in months. The feedback loop is short enough that lead volume is at least a rough proxy for pipeline health.

SSDI is structurally different. According to the Social Security Administration, the average processing time for an initial disability determination at the Disability Determination Services level has historically run six months or more, and that figure does not include the reconsideration or hearing stages that follow an initial denial. The SSA's own processing data shows that a meaningful share of claimants who ultimately receive benefits do so only after an administrative law judge hearing, a stage that can arrive eighteen to twenty-four months after the original application.

A lead that entered your pipeline in March may not produce an approved case until the following spring. If your report stops at "leads this month," you are measuring the wrong thing, and you are making budget decisions on data that cannot yet tell you whether the campaign is working.

The right headline metric is cost per approved case, by ad set. Everything else in an SSDI marketing report supports that number.

Tracking the Gap Between Application Filed and Decision

The gap is the core reporting problem for SSDI firms. It is long, it is variable, and it is filled with stages that matter to the marketing signal.

A complete SSDI case pipeline has at least these stages:

  1. Lead submitted
  2. Intake completed and case accepted
  3. Application filed
  4. Initial determination received (approved or denied)
  5. Reconsideration filed (if denied)
  6. ALJ hearing scheduled
  7. ALJ decision received (approved or denied)
  8. Appeals Council or federal court (rare, but trackable)

Every one of these stages should exist in the firm's CRM pipeline. Not because the marketing team needs to manage the case, but because the stage where a case exits the pipeline carries a marketing signal.

A lead that exits at "intake completed, case rejected" is a qualifying signal. If a high share of leads from one ad set exit there, the ad is attracting claimants who do not meet the firm's acceptance criteria. That is a targeting problem, and it shows up in the report before the first approved case ever arrives.

A lead that exits at "initial determination, denied" and then stalls, never reaching reconsideration, is a different signal. It may reflect a claimant who did not have the medical documentation the case needed. Again: if one traffic source produces a disproportionate share of these exits, the report should flag it.

The mechanism is simple. Every lead gets a CRM record on submission. The record carries the original click ID, the ad set ID, the campaign, and the traffic source. As the case moves through pipeline stages, the record updates. When the SSA issues a decision, the outcome is logged. The marketing report then groups cases by the cohort period when the lead entered, not the period when the case closed.
A properly built SSDI marketing report assigns a unique click ID to every lead at the moment the form is submitted, then carries that ID through intake, the CRM, and the SSA decision record so every approved case maps back to the ad that produced it.

Cost Per Approved Case by Ad Set and Referral Source

This is the number that makes SSDI marketing reports useful.

The calculation itself is not complex: total ad spend for a given ad set over a cohort period, divided by the number of approved cases that cohort has produced to date. The complexity is in the data infrastructure that makes the calculation possible.

To get there, you need four things:

A click ID on every lead. When someone submits a form from a Meta ad, the fbclid (Facebook click identifier) should be captured in the CRM record automatically. The same applies to gclid for Google. This is a front-end tracking configuration on the landing page and a field in the CRM intake form. Without it, you can count approved cases but you cannot attribute them to an ad.

Pipeline stages that mirror the SSA process. Covered above. If the CRM has only "lead," "consultation," and "closed," the report cannot distinguish an approved case from a case that was declined at intake.

A cohort date field. Every CRM record should carry the date the lead submitted. Reports group leads by submission month or quarter, then track each cohort forward. A report run today might show the October 2024 cohort at 60% of cases resolved, with 18% approved. That is actionable. A report that lumps all approved cases into the current month is not.

A closed-won stage that triggers an event. When a case reaches "approved" in the CRM, that stage change should fire an event back to Meta via the Conversions API and to Google via the offline conversions upload. That event tells the platform: the person who converted on this ad set eventually produced an approved case. Over time, the platform's bidding model learns which audience signals correlate with approved cases, not just form fills.
Sending approved-case events back to Meta and Google via the Conversions API teaches the platforms to bid toward the profile of a claimant who reaches approval, not the profile of someone who fills out a form.

The report, then, should show a table: each active ad set, the cohort period, total spend, total leads, cases accepted, cases approved to date, cases still pending, and cost per approved case for the cases already resolved. A column for average time-to-decision by cohort helps the firm set realistic expectations for newer cohorts.

Denial-Rate Patterns Worth Flagging to Intake

The initial denial rate for SSDI claims is high. The SSA's Red Book on work incentives and disability programs and the agency's published statistical data note that a substantial majority of initial applications are denied, with many claimants ultimately receiving benefits only after reconsideration or a hearing.

That aggregate denial rate is not a marketing variable. It is a feature of the SSA process.

What is a marketing variable is the denial-rate pattern by traffic source. If your firm runs two ad sets, one targeting by geography and a broad interest audience, and one running a tighter creative aimed at claimants with specific conditions, and one of those ad sets produces a disproportionate share of claims denied at the initial level with no subsequent approval at hearing, that is a signal worth acting on.
Denial-rate patterns by traffic source are a reportable signal: if one ad set consistently feeds claims that reach denial at the initial level, tightening the qualifying questions on that ad's landing page is a concrete and actionable fix.

The fix is usually at the qualifying stage, not the ad itself. The intake-qualifying landing page for an SSDI campaign should screen for the criteria the firm uses to accept cases: duration of the disabling condition, work history, prior filings, current treatment status. If a page is not asking those questions before staff ever touch the lead, the firm is spending intake capacity on leads the marketing report will eventually show as low-quality.

The report surfaces the pattern. The intake page is where you close it.

Building a Report That Spans the Multi-Month SSDI Timeline

A monthly snapshot does not work for SSDI. The reporting structure needs to be a rolling cohort model.

The logic: group every lead by the month or quarter it entered the pipeline. Call that group a cohort. Track each cohort forward on its own timeline. A report run in October 2025 might show:

  • Q1 2024 cohort: 92% of cases resolved, cost per approved case calculable and final.
  • Q3 2024 cohort: 70% resolved, early cost per approved case visible with a note that 30% are still pending.
  • Q1 2025 cohort: 20% resolved, too early for a reliable cost per approved case but denial-at-intake rate is visible.
  • Q3 2025 cohort: 5% resolved, report shows lead volume and acceptance rate only.
    Because an SSDI case can take twelve to twenty-four months from application through appeals, disability marketing reports must use a rolling cohort model that groups leads by the month they entered the pipeline, then tracks each cohort forward.

This structure does two things. First, it gives the firm an honest picture of where each cohort stands without conflating old approved cases with new leads. Second, it gives the marketing team an early-warning signal: if the Q1 2025 cohort is showing a high denial-at-intake rate, that is visible now, not eighteen months from now.

The practical tool for this is a CRM with custom fields and a reporting layer that can filter by intake date rather than close date. Most major CRMs support this configuration. If the firm's CRM does not have cohort-date filtering, the first build task is adding that field and backfilling it for existing records. The CRM automation setup is where this gets built once and runs automatically from that point forward.

Using Report Data to Adjust Ad Targeting Quarterly

The cohort report is not a historical document. It is an optimization input.

The practical cycle for an SSDI firm:

Each quarter, pull the oldest fully resolved cohort and ask three questions.

First: which ad sets in that cohort produced the lowest cost per approved case? Shift budget toward those sets in the current campaign structure. If a geographic audience outperformed a broader interest audience on approved-case rate, the next quarter's allocation reflects that.

Second: which ad sets produced the highest denial-at-intake rate? Review the landing page and intake questions for those sets. If the creative is attracting claimants who do not meet the firm's case criteria, the page needs to qualify harder, or the creative needs to set clearer expectations about what conditions the firm handles.

Third: what does the current quarter's early data show about lead-to-acceptance rate? A drop in acceptance rate on new leads, before approved-case data is available, is the earliest signal that the intake-qualifying stage needs attention.
The question a managing partner should ask of any SSDI marketing report is not how many leads came in this month, but what is the cost per approved case for each ad set over the last two cohort periods.

This quarterly review cycle connects directly to the platform bidding strategy. As approved-case events accumulate in Meta and Google via the Conversions API, the platforms have more signal to optimize against. A campaign that has been running for two years with approved-case events firing has a materially different bidding model than a campaign optimizing for form fills. The report tells you whether the signal is strong enough yet, and what the approved-case rate looks like for each ad set that contributed events.

The Meta ads system for SSDI is set up to fire the approved-case event from the CRM, not from the landing page. The landing page fires a lead event. The CRM fires the approved-case event when the pipeline stage changes. Those are two separate optimization signals, and both matter.

For SSDI firms that also run search, the same logic applies. Law firm SEO and Google Ads for disability cases produce leads that enter the same CRM pipeline. The report should show cost per approved case by source, including organic, paid search, and paid social, so the firm can see which channel produces the most efficient path to an approved case over a full cohort period.

Frequently Asked Questions

What metrics matter most for SSDI lead generation?

The metrics that matter most for SSDI lead generation are: cost per approved case by ad set, denial-at-intake rate by traffic source, lead-to-case-acceptance rate, and the cohort-level approval rate for each quarter's leads tracked forward. Lead volume and cost per lead are useful early indicators but do not tell a firm which ads are producing approved cases, which is the only outcome that drives revenue for a contingency-fee disability practice.

How long does it take to know if an SSDI lead converts to an approved case?

The timeline varies by case and by how far through the SSA process a claimant must go. Initial determinations from Disability Determination Services can take six months or more. If a claim is denied and goes to an administrative law judge hearing, the full timeline from application to decision can reach eighteen to twenty-four months. A marketing report for an SSDI firm should not expect final approved-case data from a recent cohort. It should show the cohort's current stage distribution and flag early signals like denial-at-intake rate while the cohort is still pending.

How do you report on SSDI case outcomes to track ROI?

You track ROI by assigning a click ID to every lead at submission, carrying that ID through the CRM pipeline, logging the SSA outcome when it arrives, and grouping leads by intake cohort rather than case-close date. The report shows total spend per ad set for each cohort period, the number of approved cases that cohort has produced, and the resulting cost per approved case. Approved-case events are also sent back to Meta and Google via the Conversions API so platform bidding can optimize toward the audience profile that produces approvals, not just form fills.

What should an SSDI marketing dashboard show?

An SSDI marketing dashboard should show: active ad sets with current lead volume and lead-to-acceptance rate, cohort panels for each prior quarter showing approval status and cost per approved case for resolved cohorts, denial-at-intake rate by traffic source, and the event pipeline confirming that approved-case events are firing back to Meta and Google. A single monthly lead count without cohort structure and without approved-case attribution is not a functional SSDI marketing dashboard.

Why is the denial-at-intake rate a marketing metric and not just a case metric?

The denial-at-intake rate becomes a marketing metric when it varies by traffic source. If one ad set consistently produces leads that the firm declines at intake, the creative or the qualifying page for that ad set is attracting the wrong claimants. The marketing team can tighten the intake-qualifying questions on the landing page for that ad, adjust the creative to set clearer expectations, or shift budget away from that ad set. The case team sees individual denials. The marketing report shows the pattern by source, which is what makes it actionable at the campaign level.

Can SSDI marketing reports integrate with Google Ads and Meta at the same time?

Yes. The mechanism is the same for both platforms. Each lead carries the platform's click ID (fbclid for Meta, gclid for Google) in the CRM record. When a case reaches the approved stage in the CRM, the pipeline stage change triggers two events: an offline conversion upload to Google Ads and an approved-case event to Meta via the Conversions API. Both platforms then have the approved-case signal in their optimization models. The marketing report pulls spend and lead data from both platforms and maps them to the same CRM cohort data, so cost per approved case is visible by platform and by ad set.

How does an SSDI qualifying page reduce denial-at-intake rate?

An SSDI qualifying page asks the screening questions before a lead submits. Example: a qualifying page for an SSDI firm might ask whether the claimant's condition has prevented them from working for at least twelve months or is expected to, whether they have received treatment from a licensed provider, and whether they have previously filed and been denied. A lead who answers outside the firm's acceptance criteria sees a message explaining the firm cannot help and, where appropriate, a referral resource. A lead who qualifies continues to the intake form. This front-end screen means intake staff spend their time on leads the firm has already pre-qualified, and the CRM pipeline does not fill with records that will exit at denial-at-intake, which reduces the noise in the cohort report.

RGDM builds the full case-acquisition system for SSDI and disability practices: Meta ads, conversion tracking, CRM automation, AI lead response, and qualifying landing pages. If you want to see what a cohort report looks like for your firm's current pipeline, book a free Case Acquisition Review.

← All insights
Ready when you are

Let's turn your clicks into customers.

Book a 30-minute call. We'll review your spend, your tracking, and where customers are slipping away.

Book a call