Why is pooling case types a problem?
Because the ad platform optimizes toward the inquiries it can buy most cheaply, and across EB-5, NIW, and marriage green card those are almost never the ones you make the most money on. One shared budget bends toward the low-fee case type by default.
Google and Meta do not know which inquiry becomes a high-value retainer. They know which one is cheapest to generate. Put three case types with wildly different fees into one campaign and the algorithm chases volume at the lowest cost per lead, which pulls spend toward marriage green card inquiries and starves EB-5. Your most valuable case type gets capped at the low-fee average without anyone deciding that on purpose.
The damage is hidden because the dashboard metric stays green. Cost per lead can look excellent while the mix underneath rots: EB-5 leads arrive with marriage green card pricing expectations, marriage green card leads cannot afford EB-5, and attorneys burn hours on prospects who were never a fit. That is why the honest metric is cost per signed case, read separately for each case type, not one blended cost per lead.
How different are EB-5, NIW, and marriage green card?
Different enough that treating them as one audience makes no sense. They differ on retainer size, how fast a signed client closes, and who the buyer even is. A campaign tuned for one is the wrong campaign for the other two.
Retainer figures are typical market ranges, not any single firm's results. They vary by market, complexity, and firm.
On these market benchmarks, an EB-5 client is worth several times a marriage green card client, yet in a shared campaign both are counted as one more lead. The buyers do not overlap either: on the same benchmarks, the person weighing a $25,000+ investor petition is nothing like the price-sensitive spouse comparing a $3,500 filing. One message, one bid, and one intake path cannot serve all three without shortchanging two of them.
What does pooling do to cost per lead vs cost per signed case?
It pulls cost per lead down and pushes cost per signed case up, at the same time. The cheap-inquiry mix flatters the dashboard while the cases that actually pay the firm get more expensive to win.
When a shared budget floods with low-fee inquiries, the blended cost per lead drops and everyone relaxes. But those inquiries convert into low-fee retainers, if they convert at all, so the number that matches revenue, cost per signed case, quietly climbs for your high-value work. You are optimizing the metric that looks good and neglecting the one that pays.
Directional illustration of the pooling trap, not figures from any specific firm.
This is the same discipline behind judging marketing on cost per signed case rather than cost per lead: a low cost per lead can hide a high cost per signed case. Pooling case types is one of the fastest ways to open that gap, because it lets the platform optimize the exact wrong number.
What does the fix look like?
One independent campaign track per case type. Each case type gets its own creative, its own bid strategy, its own cost ceiling, and its own intake path, so no case type can quietly cannibalize another's budget.
- 01Split into one track per case type
EB-5, NIW, and marriage green card each run as a separate campaign. They never share a budget, so the algorithm can no longer drain the expensive line to feed the cheap one.
- 02Give each track its own creative and message
The investor ad speaks to a high net worth, often international buyer. The NIW ad speaks to a self-petitioning professional. The marriage green card ad speaks to a price-aware couple. No shared message can do all three.
- 03Set a bid strategy and cost ceiling per track
EB-5 can absorb a far higher cost per signed case than marriage green card, so each track carries its own ceiling. Budgets are set against each case type's real economics, not a blended average.
- 04Route each track to its own intake path
An EB-5 inquiry and a marriage green card inquiry need different questions, different pacing, and different expectations set. Separate intake keeps mismatched leads off the wrong desk.
Done together, separation stops the silent subsidy and lets each case type be measured, funded, and scaled on its own terms. The clearest proof we can publish comes from a multi-year immigration engagement built exactly this way. Across that anonymized engagement, cost per signed case fell 55% across a three-year engagement.
Our immigration law client approved one public result: a 760% marketing revenue increase.
How Digital Rocket separates case types
We build each case type as its own campaign track from the start, then judge every track on cost per signed case, never on a blended cost per lead. Separation is the default, not an optimization we get around to.
In practice that means EB-5, NIW, and marriage green card run as distinct campaigns with distinct creative, distinct bid strategies, and distinct cost ceilings tied to each case type's economics. Signed retainers are tracked per case type in the CRM and fed back to Google and Meta, so spend follows the cases that actually sign rather than the cheapest inquiries. One tracked dataset showed a +78% improvement and a 55% qualification rate, per our client data.
The result is that no case type subsidizes another by accident. EB-5 gets funded like EB-5, marriage green card gets funded like marriage green card, and you can see which line genuinely pays instead of trusting a green dashboard that averages three different businesses into one misleading number. That is the core of CaseFlow, our signed-case acquisition system for immigration firms.