Activate the target account list with one identity resolution and one exclusion list across paid display, paid social, direct mail, and BDR outreach, so the same account stops getting contradictory treatment
ABM done badly is the same target account being approached by paid display, paid social, direct mail, and BDR outreach independently, each channel running its own segmentation, each one treating the account as if it were the only one in conversation, and the account experiencing a brand that does not seem to know what it is doing. The display ad and the LinkedIn post arrive contradicting the BDR's email, the direct mail piece lands a week after the account has already booked a demo, and the prospect's read is not that the brand is everywhere; it is that the brand is uncoordinated.
The coordination problem is harder than it looks because each channel runs against a different identifier. Paid display targets accounts by IP-and-firmographic match, paid social by LinkedIn account match, BDR outreach by CRM contact ID, direct mail by mailing-address lookup. Without one shared account identifier that all channels resolve to, the exclusion list "account is in late-stage opportunity, do not run prospecting ads at them" cannot reach the platforms running the prospecting ads, and the conflict persists.
This recipe builds the shared account resolution and the shared exclusion that lets each channel know what every other channel is doing, so the account experiences one coherent motion rather than four independent ones.
A target account list activated consistently across paid display, paid social, direct mail, and BDR outreach, with shared identity resolution and a shared exclusion list that keeps the channels coordinated. The metric is account coverage consistency: the percentage of target accounts receiving the channel mix appropriate to their stage, measured against the percentage receiving conflicting or contradictory treatment. The value shows up in the prospect experience (the brand reads as deliberate rather than as buckshot), in the BDR's working day (fewer cold calls to accounts already in late-stage), and in the channel spend (less wasted prospecting on accounts that should be excluded from prospecting).
The second outcome is the operational discipline of treating the account as the unit of activation rather than the channel: a target account moves through stages, and the channels operate against the account's stage rather than against their own pipeline view.
An account-level activation layer that resolves accounts across channels and pushes the target list, with stage and exclusion, to each platform on the cadence the platform needs (daily for most paid platforms, near-real-time for the BDR queue, batched for direct mail). Composable stacks suit this because the account resolution lives in the warehouse and the activation paths fan out from there. The capability that decides whether the recipe holds together is the resolution: a platform that cannot be reached with the account identifier (a display platform that only takes domain matches, a social platform that only takes company names) reduces to a softer match and the exclusion list does not reach it cleanly. The channels that can take a deterministic account identifier are the ones the recipe holds tightest on; the others get fuzzier coordination and the gotcha section calls it out.
Compare the tools on Martech Stack Builder
Marketing ops owns the target-list curation, the cross-channel coordination, and the discipline of holding the exclusion list as one list rather than four. Sales ops owns the BDR queue and the handoff rules, because BDR outreach is the channel that most often runs in parallel without coordination and the rules for when BDR engages and when other channels lead are sales-ops decisions. Data engineering owns the account resolution across systems and the activation feeds to each channel, because the recipe lives or dies on the resolution layer. Analytics measures coverage consistency and the per-channel touch pattern, which is how the team knows whether the coordination is actually working at the account level. The recipe takes months because the account resolution work takes months. The target list is straightforward; agreeing on the resolution across the channels' different identifiers, building the mapping, and holding it current as accounts merge, spin off, and rename is where the time goes.
Work in this order. The first two steps decide whether the channels can coordinate at all.
Household or account-level resolution covers steps 1 and 6, suppression and exclusion logic steps 2 to 4, and channel handoff step 5.
The first failure is the per-channel target list. Each channel maintaining its own version of "the target accounts" drifts from the others within a quarter as accounts are added and removed, and the coordination the recipe promises stops being real because the lists no longer match. One target list with one source of truth is the structural decision that keeps the channels honest; per-channel lists collapse back into the original problem.
The second is the exclusion that does not reach every channel. A late-stage opportunity excluded from BDR outreach but not from paid prospecting still receives the prospecting ad, and the prospect's experience is the brand pitching them while the BDR they have been talking to is closing the deal. The exclusion has to fan out to every channel the account is reachable on, which is a function of the resolution: a channel without a clean account identifier cannot honour the exclusion cleanly, and the recipe has to either fix the identifier or accept the gap explicitly.
The third is the resolution that quietly degrades. Account identifiers change (renames, mergers, acquisitions, parent-subsidiary splits), and a resolution that is correct at deploy time drifts over months as the corporate landscape moves. A resolution that does not have a maintenance loop (reconcile against the source-of-truth account list on a cadence, surface unmatched accounts as exceptions, retire identifiers that are no longer current) produces increasingly mismatched coordination, and the channels run on stale joins.
The Workshop works out with your team which of these matter for your stack right now, and what to do first: a 90-minute session with the people who own the decision.
The account resolution that lets every channel reach the same account, the exclusion list shared across channels with the reasons behind each exclusion, the channel handoff that moves the account through stages coherently, and the resolution maintenance that keeps the coordination current: those are the decisions that turn parallel channel motions into one account motion the prospect experiences as deliberate.
Did this recipe match your situation?Anonymous response. Sign up to leave a longer note tied to your account.
Aggregate the signals from every contact in the account into one account score, because the buying committee is buying together and scoring leads in isolation misses the picture that matters
Lower acquisition cost by feeding the bidding algorithms better conversions, deduplicated, consent-valid, and weighted by value, rather than just more of them
Target CTV from your own customer segments and measure the reach you actually added above linear, rather than buying impressions on faith