Most B2B marketing teams treat ABM and demand generation as competing religions. The demand gen side argues that gating content and running broad paid programs fills the pipeline faster. The ABM side argues that chasing volume creates noise and burns sales bandwidth on accounts that will never close. Both camps are partially right, and the friction between them is the actual problem.
The teams that consistently outperform run a combined motion. They use demand gen to generate awareness and surface buying signals across a broad addressable market, then funnel the highest-fit signals into a focused ABM track. Neither motion cannibalizes the other. They feed each other.
This playbook walks through how to build that integration: how to structure the team, define the handoff logic, set up the shared data layer, and measure the combined result without confusing attribution.
Demand generation and ABM developed in different eras with different tooling and different success metrics.
Demand gen teams built their playbook around scale: high-volume content, broad paid channels, lead capture forms, MQL scoring, and SDR handoffs. The metric was leads in, meetings booked, pipeline created. Volume was the proxy for performance.
ABM emerged as a reaction to that volume-first model. When sales teams started complaining that most MQLs were wrong-fit accounts, ABM consultants sold a “quality over quantity” framework. Target a list. Run coordinated multi-channel campaigns against it. Measure account engagement, not lead counts.
The problem is that neither approach works well in isolation at the growth stage. Pure demand gen burns budget on companies you will never close. Pure ABM has a reach problem: you can only run so many accounts at Tier 1 depth before the program gets expensive and slow.
The integration model solves both problems. Demand gen creates efficient top-of-funnel reach and surfaces intent signals. ABM converts those signals into focused, high-conviction pipeline at the accounts that matter most.
You cannot integrate ABM and demand gen without a shared account tiering model. Without it, every conversation about budget allocation, channel choice, and measurement turns into a political fight.
Tier 1 accounts get full 1:1 ABM treatment: custom content, direct mail, executive outreach, personalized web experiences, coordinated SDR sequences. This tier should be small: typically 25 to 50 accounts at any one time, depending on your ACV and sales cycle length.
Tier 2 accounts get 1:few ABM: segment-level content, industry-specific ad campaigns, targeted LinkedIn sequences, lighter personalization. This tier can hold 100 to 300 accounts.
Tier 3 accounts sit in the demand gen motion. They receive broadly targeted content, retargeting, gated assets, and nurture sequences. If they show sufficient engagement or intent, they get promoted into Tier 2 or Tier 1.
The tiering criteria need to be explicit and written down. Common inputs: ICP fit score (company size, industry, tech stack), CRM deal history (similar companies that closed), intent signal strength, engagement history. Your tiers should be reviewed monthly and accounts should move between them.
The mechanism that makes integration work is signal-based promotion: a clear, documented set of rules that move an account from the demand gen pool into the ABM track.
Without explicit promotion criteria, you end up with two teams running parallel programs on overlapping account lists with no shared logic. Marketing ops spends its days reconciling conflicting activity reports. Sales gets confused about which accounts are being worked and how.
Define promotion triggers. These are the signals that move an account from Tier 3 (demand gen) to Tier 2 (1:few ABM):
Define escalation triggers. These move an account from Tier 2 to Tier 1:
Document these triggers in a shared playbook. Route the logic into your CRM so that when thresholds are hit, the account record updates automatically and the relevant SDR or AE gets a task.
The integration falls apart without a shared data layer that both teams trust. This is the layer that connects the demand gen funnel (engagement by contact) to the ABM view (engagement by account).
Account-level engagement scoring. Most marketing automation systems score by contact. For ABM, you need a score aggregated to the account level. Sum engagement scores across all contacts at the account. Set thresholds that trigger the promotion logic from Step 2.
Intent data feed. Pipe your intent data (whether from a dedicated platform or your own behavioral signals) into the CRM at the account level. Tag accounts with active intent signals and the relevant topics. This gives both the demand gen team and the ABM team a shared view of which accounts are in-market.
CRM as the system of record. Every touchpoint, whether from a demand gen email campaign or a Tier 1 ABM direct mail send, should be logged against the account in the CRM. This is what makes attribution tractable later.
Shared dashboards. Build a single reporting view that both teams use in their weekly standup. The view should show: account tier distribution, accounts promoted this week, accounts in active ABM motion, accounts with declining engagement that may need to be deprioritized, and pipeline created by tier.
If marketing ops is not already the hub that connects both teams, now is the time to designate them. The integrated motion breaks down if two separate ops functions are maintaining separate data pipelines.
Channel allocation is where budget decisions get made, so it needs to be explicit.
Tier 1 channels (1:1 ABM): - Personalized web experience triggered by account IP or reverse-IP identification - Direct mail for senior stakeholders confirmed in the buying committee - Custom content assets (tailored ROI model, custom comparison deck, industry-specific case study) - LinkedIn InMail and connection requests from named AEs, not company pages - Executive-to-executive outreach (your leadership to their leadership) - Exclusive roundtable or dinner invitation
Tier 2 channels (1:few ABM): - LinkedIn Matched Audiences campaigns targeted to the account list with segment-level creative - Industry-specific content tracks (landing pages, email sequences, webinar invites relevant to their vertical) - Retargeting campaigns with segment messaging - SDR cadences with account-specific research in the first touch - ABM display advertising with account-level frequency caps
Tier 3 channels (demand gen): - Broad LinkedIn and Google campaigns - Content syndication - SEO-driven blog and ungated content - Webinars open to general registration - Gated assets and lead nurture sequences - PPC for high-intent keywords
The principle here is that budget intensity increases as you move up the tiers. A Tier 1 account may receive $500 to $2,000 in marketing investment before the first conversation. A Tier 3 account receives pennies of programmatic spend.
The single biggest driver of integration failure is misaligned incentives. If the demand gen team is measured on MQL volume and the ABM team is measured on account engagement, they will optimize against each other.
Build shared OKRs that force both teams toward the same outcome: pipeline from target accounts.
A workable shared OKR structure:
Objective: Build a high-quality pipeline that converts to closed revenue within one quarter of target.
Key results: - X percent of new pipeline this quarter originated from Tier 1 or Tier 2 accounts - Y percent of Tier 1 accounts have at least one open opportunity in CRM - Z accounts promoted from Tier 3 to Tier 2 or higher based on signal logic (measures demand gen contribution to ABM) - Average deal size from ABM-sourced pipeline exceeds the company average by a target percentage
The third KR is critical: it creates an explicit metric for demand gen’s contribution to ABM. Demand gen is no longer just running programs in isolation. Its job, in part, is to surface the accounts that deserve ABM investment.
The integration requires a regular operational cadence. Without it, the two teams drift back into their silos within 60 days.
Run a monthly 60-minute sync with this agenda:
This meeting should have attendance from marketing ops, the demand gen lead, the ABM/field marketing lead, and at least one sales representative who owns the Tier 1 accounts.
The meeting output is a shared doc that gets updated monthly. Track decisions, account movements, and channel changes over time. This becomes the operating log for the integrated program.
Attribution for a combined ABM and demand gen motion is complex. You have multiple touchpoints across multiple channels, some at the contact level and some at the account level, spanning months. Fighting about first-touch versus last-touch attribution while the integrated motion is still young is a distraction.
A pragmatic attribution approach for the integrated motion:
Use multi-touch attribution with a custom weighting model that reflects your buying cycle. A reasonable starting point: give 20% credit to the first touch that introduced the account to your brand, 20% to the touch that moved the account from Tier 3 to Tier 2 (the signal that triggered ABM investment), 30% to the ABM touches that drove stakeholder engagement, and 30% to the conversion touch that drove the meeting or demo.
More important than the weighting model is tagging. Every campaign, content asset, and outreach sequence needs to be tagged with: the tier level at the time of the touch, the channel, and the motion (demand gen versus ABM). Without tagging discipline, the attribution model is built on garbage data.
Run attribution reports quarterly, not weekly. Weekly attribution analysis encourages short-term optimization that distorts the program. Your buying cycle is measured in months. Optimize for monthly or quarterly pipeline quality, not weekly lead counts.
The three metrics that actually tell you whether integration is working:
The ABM list never updates. Teams build a target account list, run campaigns for six months, and forget to refresh the list based on new signals. Static lists produce diminishing returns. Build a quarterly list review into the program calendar before you launch.
Demand gen runs campaigns to ABM accounts without coordination. ABM accounts start receiving generic demand gen nurture emails at the same time SDRs are sending personalized outreach. This looks disjointed and undermines the ABM investment. Use suppression lists in your marketing automation platform to exclude active ABM accounts from generic demand gen campaigns.
Attribution arguments stall the program. When two teams share budget and cannot agree on who gets credit for pipeline, politics stop progress. Decide on the attribution model before you launch the integrated motion, put it in writing, and commit to using it for at least two quarters before revisiting.
The data layer is never built. The integration works on paper but the two teams are pulling data from different places in different formats. The shared data layer investment (account-level scoring, unified dashboards, CRM tagging) feels like overhead. It is not. It is the infrastructure that makes the rest of the playbook function.
Days 1 to 30: - Document the account tiering criteria and get sales and marketing leadership to sign off - Export your current account list, score accounts by ICP fit, and assign preliminary tiers - Audit the existing data layer: can you aggregate engagement scores at the account level, are intent data feeds connected to CRM, is campaign tagging consistent? - Define the promotion trigger logic and build it into the CRM workflow
Days 31 to 60: - Launch Tier 2 ABM campaigns for the accounts with the strongest existing signals - Run a demand gen audit: which current campaigns are reaching Tier 3 accounts, which are reaching ABM accounts (and should be suppressed or upgraded) - Build the shared reporting dashboard - Run the first monthly sync
Days 61 to 90: - Promote the first wave of demand gen accounts into Tier 2 based on signal triggers - Review Tier 1 accounts and launch at least one custom 1:1 ABM play for the top 10 accounts - Run the second monthly sync with pipeline data - Identify one attribution question to answer with the first 90 days of data
The integrated motion does not come together overnight. Thirty days in, you will have more clarity on where the data gaps are. Sixty days in, you will start seeing accounts moving through the tiers. At 90 days, you will have enough data to have a real conversation about what is working and what to change.