How to measure account based marketing when your tools were built to count leads, and what no attribution model can ever prove.

How to measure account based marketing, in plain terms

How to measure account based marketing comes down to one change: you stop counting leads and start counting accounts. Every number on the report is filtered to the named list of companies you decided to work, and compared with everything outside that list.

That sounds small. In practice it changes the source of almost every metric, because most marketing tools count people, sessions and forms, while an ABM strategy is a bet on companies.

The honest version of this guide has three parts: the numbers a small team can genuinely produce, a scorecard that fits on one screen, and a clear statement of what your analytics cannot tell you no matter how the report is built.

Why lead metrics mislead in ABM

Lead metrics answer a question ABM is not asking. They count individuals who raised a hand, and they reward volume. An account program deliberately narrows the audience, so the lead count almost always falls in the first quarter.

If leadership is watching lead volume while the team runs ABM, the program looks like a failure exactly when it is working as designed.

The replacement column is not better because it is more sophisticated. It is better because it matches the decision you made when you chose the list.

A single MQL still matters, but only as a signal inside an account, not as the unit that gets reported to the board.

The account is the unit, the buying group is the detail

In ABM the row in your report is a company. Inside that row sits a buying group: the people who will decide, use, approve and block. Both levels need numbers, and they answer different questions.

• Account level: is this company moving? Coverage, engagement, opportunity, pipeline, revenue.
• Person level: is the right group inside the company involved? Roles reached, roles engaged, roles in the last meeting.
• Program level: is the list as a whole better than the rest of the funnel? Win rate, deal size, cycle length, cost.

Teams that only report the account level miss the most useful warning sign in B2B: a deal moving forward on one contact. Multithreading is a measurement problem before it is a sales problem.

ABM metrics in five layers

Most confusion about ABM metrics comes from mixing layers. Coverage is not engagement. Engagement is not pipeline. Each layer has its own question, its own source and its own honest reporting frequency.

Read the table downward and you get a funnel. Read it as a set of independent checks and you get something more useful: a way to tell whether a bad quarter was a targeting problem, a message problem or a sales problem.

Measuring ABM by tier: one-to-one, one-to-few, one-to-many

An account based marketing strategy usually runs in three tiers, and each tier deserves different ABM metrics. Judging a one-to-many program on meetings, or a one-to-one program on impressions, is the fastest way to reach a wrong conclusion about the whole strategy.

Report the tiers separately and never blend them into one ABM average. A one-to-many campaign will always dominate the counts, and a one-to-one campaign will always look tiny next to it, whatever either one is worth.

The tier also sets a fair sample size. With eight one-to-one accounts, no rate is meaningful, so report those accounts by name and describe what happened at each. Rates belong to the one-to-many tier, where the numbers are large enough to behave.

Coverage: is the list actually covered?

Coverage is the least glamorous number and the first one to check. It asks whether you have enough of the right people on file at each account to run a program at all.

Coverage is the one metric you can improve in a week, and it is usually the cheapest fix available. A target account list with weak coverage will produce weak engagement no matter how good the creative is.

Report coverage as a count of accounts, not a percentage of contacts. Percentages of contacts hide the account that has forty people on file and the account that has none.

Account engagement, and how to score it without a platform

Account engagement is the sum of what people at one company did, rolled up to the company. ABM platforms do this automatically. Without one you can still do it, as long as you accept a simpler definition and keep it fixed.

The trick is to define engagement once, in writing, and never quietly change it. A definition that moves makes every trend line meaningless.

• Count actions, not points, at first. Meetings, replies, event attendance and demo requests are unambiguous and easy to defend.
• Weight by role, not by channel. A reply from the budget owner is worth more than five opens from an intern.
• Require recency. Engagement older than ninety days should stop counting, or every account looks engaged forever.
• Count distinct people. Three actions from one contact is one person interested, not a buying group.
• Separate marketing and sales activity. Otherwise a busy rep can make a cold account look warm.

A worked definition, written for this page

An account counts as engaged in a month when at least two distinct people took at least one meaningful action each, where meaningful means a reply, a meeting, an event registration, a webinar attendance or a visit to a pricing or product page.

That definition is deliberately strict and deliberately boring. It was written for this page as an example, not taken from a vendor model, and you should adapt the thresholds to your own volume before using it.

If you use B2B intent data, keep it in a separate column. Third party intent is a targeting input, and mixing it into engagement makes the score look better without anyone at the account doing anything.

Content engagement at target accounts

Most ABM marketing budget goes into content, so content deserves its own track on the report. The question is not how many people read a piece. It is whether the target accounts you care about read it, and which roles inside them did.

• Assets opened by target accounts. Count named accounts per asset, not total downloads, so a popular guide with no list traction is visible.
• Content that preceded meetings. Look back from booked meetings and note which piece was in play. Directional, not proof, but useful.
• Role of the reader. The same case study means one thing to a technical evaluator and another to a finance approver.
• Repeat visits from one account. Two people from the same customer returning to a page is a stronger signal than one person reading everything.
• Content with zero list engagement. Track it so you can retire it. Content nobody on the target list touches has no ABM value.

Keep this section short on the scorecard. Content metrics are the easiest place to build an impressive slide that no revenue decision depends on, and they belong under engagement rather than beside pipeline.

Pipeline and revenue from target accounts

Pipeline and revenue from target accounts is the layer that decides whether the program survives. It is also the layer where most teams get sloppy, because there are two very different ways to count it.

For a team without an attribution platform, the third row is the one to use. You froze a list, you worked it, and you report what happened at those companies compared with everything else in the same period.

Alongside the total, report deal size, win rate and sales cycle length for the list against non-list deals. Those three comparisons carry more argument than any attribution chart, and they come straight out of the CRM.

Revenue is the last number, not the first. If you need a definition to align finance and marketing on what counts, our revenue entry sets it out.

ABM ROI and pipeline velocity, handled carefully

Two ABM metrics get quoted more often than they are earned: ROI and pipeline velocity. Both are simple formulas, and both go wrong in the same place, which is the numbers you feed them rather than the arithmetic.

ROI

ROI on an ABM program is revenue from target accounts, minus the cost of the program, divided by that cost. Revenue is the easy half. Cost is where teams quietly understate the investment and produce a flattering figure.

• Count people time. Marketing and sales hours spent on the list are usually the largest cost in the whole program.
• Count content production. Custom assets for named accounts are expensive, and they are part of the campaigns you are measuring.
• Count data and tools. Enrichment, intent and ad platforms are direct costs of the strategy, not general overhead.
• Count events. Dinners, roundtables and field marketing belong to the accounts they were run for.
• Wait a full cycle. ROI computed before the first deals could close is guaranteed to be negative and tells you nothing.

Pipeline velocity

Pipeline velocity multiplies the number of open opportunities by average deal value and win rate, then divides by the average sales cycle length. It is a useful trend line for a large one-to-many tier and a misleading single figure for a small list.

With twelve opportunities, one unusual deal moves every input at once. Report the components separately as well, so a reader can see whether velocity changed because of volume, value, win rate or time.

Customer retention, expansion and account value

ABM does not end at the first win, because target accounts are usually chosen for their long term value rather than for a single deal. A program judged only on new business misses most of the value it was designed to create.

These metrics move slowly, which is why they belong on the yearly view. They are also the strongest argument for the strategy, because a customer base built from a chosen list should behave better than one built from whoever filled in a form.

Leading indicators, lagging indicators, and the gap between them

Coverage, reach and engagement are leading indicators: they move within weeks and they tell you whether the program is running. Pipeline, win rate and revenue are lagging: they move in quarters and they tell you whether it worked.

The gap between the two is the length of your sales cycle, and that is the single most important number for interpreting an ABM report.

• Short cycle, say one quarter: leading and lagging numbers can appear on the same monthly report.
• Long cycle, a year or more: the first four reports will contain leading indicators only, and everyone should know that in advance.
• Mixed portfolio: split the report by segment, because one enterprise deal will otherwise drown every other signal.

Write the expected gap at the top of the report. It prevents the quarterly conversation where someone asks why revenue has not moved eight weeks into a nine month cycle.

Which numbers a small B2B team can actually produce

Most ABM measurement advice assumes an intent platform, an attribution tool and a data team. Without those, some metrics are still easy, some take work, and some are simply not available. Saying which is which is the honest part.

The pattern is clear. Anything anchored to a known person or a CRM record is within reach. Anything that requires identifying anonymous behavior at company level needs a vendor, and comes with accuracy you cannot audit.

A team of two can produce the first five rows in an afternoon once accounts are tagged. That is a complete, defensible ABM report, and it beats a sophisticated one nobody trusts.

A simple ABM scorecard

This scorecard was written for this page. It is built from numbers a small team can pull from a CRM and one ad platform, and it fits on a single screen so it actually gets read.

Two rules make this scorecard work. The list is frozen for the quarter, so the denominator cannot drift. And every line is a count of accounts, never a count of leads.

Add a comparison column for the same period last quarter and one for the non-list pipeline. Without those two columns the scorecard is a set of numbers with nothing to argue against.

Attribution limits: what attribution cannot tell you

Attribution assigns credit for a recorded conversion to the touchpoints a tool could see. Everything in that sentence is a limit. It only covers recorded conversions, only touchpoints, and only the ones inside one tool's view.

The deeper problem in ABM is that attribution models credit, not cause. A model can tell you a webinar appeared in the path. It cannot tell you the deal happened because of the webinar, and no change of model fixes that.

There is also a counting trap. Credit models are designed to distribute a conversion, so if two teams each report their attributed pipeline, the two numbers can add up to more pipeline than exists.

What to do instead

• Compare populations. Target list against non-list, over the same period, on win rate, deal size and cycle length.
• Hold the list still. A list that grows mid quarter turns every rate into noise.
• Ask the buyer. One question in the discovery call about how they first heard of you beats a model, and costs nothing.
• Report ranges, not decimals. Precision you cannot defend invites an argument you cannot win.

What Google Analytics and LinkedIn actually report

Two tools sit behind most ABM reports at small companies. Both are well documented, and both state limits that matter a great deal when the audience is fifty companies rather than fifty thousand visitors.

Google Analytics

• Direct traffic gets no credit. Google states that all attribution models exclude direct visits from receiving attribution credit, unless the whole path is direct.
• Credit can move after the fact. Under data-driven attribution, Google says conversions can be reattributed for up to seven days after the conversion.
• Low volume rows get hidden. Google applies thresholding so that viewers cannot infer the identity of individual users, and the thresholds are system defined and cannot be adjusted.
• History is shorter than your sales cycle. Standard properties retain user and event data for two or fourteen months, and that setting affects explorations and funnel reports.

The thresholding point is the one that surprises ABM teams. A report filtered down to a handful of companies is exactly the shape of report that gets withheld, and the tool tells you it applied thresholding rather than showing a smaller number.

LinkedIn Campaign Manager

• Company level reporting exists. LinkedIn's Companies view reports engagement level, organic and paid impressions, paid clicks, engagements, conversions and leads by company.
• Engagement level is relative. LinkedIn calculates it from paid engagement rate plus organic engagements, normalized over the time range, then compares it with other companies advertising on LinkedIn.
• Small numbers show as a dash. LinkedIn states that impression, engagement and click metrics must meet thresholds, and shows a dash in the table when they do not.
• Revenue columns need a CRM connection. Deal status, pipeline value and revenue won in that view require CRM Sync.
• The window is a setting, not a fact. Conversion windows can be set to one, seven, thirty or ninety days, with ninety day click and view as the Campaign Manager default.
• One model double counts on purpose. With last touch for each ad set, every ad set with an interaction in the window gets credited, so summing ad sets overstates conversions.

LinkedIn also replaced the older Company Engagement Report with the Companies view in November 2024, which matters if your reporting template still refers to the old report by name. For the organic side, our LinkedIn analytics guide covers what the page reports natively.

Neither tool is wrong. Both are built to protect individual privacy and to report advertising, and an ABM program asks them a question about a small, named set of companies, which is the case they handle least well.

Set the baseline before the program starts

An ABM report without a baseline is a list of numbers with no meaning. Before the first campaign runs, write down what the same accounts looked like in the previous period, and what the rest of the business looks like now.

1. Freeze the account list and store it with a date.
2. Record current coverage: accounts with contacts, and accounts with role coverage.
3. Record open pipeline and closed revenue at those accounts for the last four quarters.
4. Record win rate, average deal size and cycle length for non-list deals.
5. Note the expected gap between leading and lagging indicators.

Five minutes of work at the start removes the most common argument at the end, which is whether anything changed at all.

The reporting cadence

The reporting cadence matters as much as the metrics, because reviewing a lagging number weekly produces panic and reviewing a leading number yearly produces nothing.

One rule keeps the cadence honest: no account joins or leaves the list mid quarter. Add new accounts at the quarter boundary and report them as a separate cohort until they have a full quarter behind them.

The weekly view is an account review, not a metrics review. It should name companies and next steps, and the sales handoff rules should be visible in it.

When to judge an ABM program

The fair moment to judge an ABM program is one full sales cycle after launch, plus the time it took to get the first campaigns live. Judging earlier measures your setup speed, not the strategy.

• Month one to three: judge execution only. Is coverage improving, are campaigns live, are accounts engaging?
• Month three to six: judge conversation. Meetings, opportunities created, roles reached per account.
• One full cycle on: judge pipeline. Compare list and non-list on win rate, deal size and cycle length.
• Two cycles on: judge revenue, retention and expansion. This is the only point where a stop decision is fair.

There is one exception worth acting on early. If coverage and engagement are both flat after a quarter of real effort, the list or the message is wrong, and waiting for revenue data will only make the correction more expensive.

How to build the measurement, step by step

1. Freeze the list and tag it everywhere

   Store the account list with a date, then tag those accounts in the CRM so every later report is one filter rather than a manual match on company names.

2. Write the baseline down first

   Record coverage, open pipeline, closed revenue, win rate, deal size and cycle length for the list and for everything outside it, before the first campaign runs.

3. Define engagement once, in writing

   Decide which actions count, how many distinct people are needed and how long an action stays fresh, then keep that definition fixed for at least two quarters.

4. Connect the three sources you actually have

   CRM for opportunities and revenue, the sequencing tool for replies, the ad platform for company level reach. Export to one sheet rather than chasing a single dashboard.

5. Build the scorecard on one screen

   Use account counts, add a previous period column and a non-list column, and put the expected leading to lagging gap at the top so nobody reads it wrongly.

6. Review monthly, judge quarterly

   Change one thing per month based on leading indicators, and reserve keep or stop decisions for the quarterly view after at least one full sales cycle.

Where the numbers live

No vendors are ranked here. These are the four places a small team pulls ABM numbers from, and what each one is good and bad at.

A spreadsheet joining these four on company domain is a perfectly respectable ABM reporting stack. If pipeline definitions are the sticking point, our guide on how to build a sales pipeline covers the stages this report depends on.

Mistakes that produce confident, wrong ABM reports

• Letting accounts join the list mid quarter, so every rate quietly changes denominator.
• Changing the engagement definition to make a bad month look better.
• Reporting influenced pipeline as if it were sourced pipeline.
• Summing attributed numbers from two tools and treating the total as real.
• Counting one enthusiastic contact as an engaged account.
• Judging revenue before one full sales cycle has passed.
• Reporting percentages when the denominator is under twenty accounts.
• Ignoring a tool's own note that it withheld or thresholded the data.
• Keeping lead volume on the same slide as account metrics, so the story contradicts itself.

The last one is worth repeating. A program that trades volume for focus will always look bad on a volume chart, and leaving that chart in the deck invites the wrong conclusion. Nurture programs have the same problem, which our B2B lead nurturing guide covers from the lead side.

The monthly note that carries the numbers

A scorecard rarely travels on its own. The note below is the short message that goes with it: what moved, what did not, what changes next month, and which decision is not due yet.

Subject: {{month}} ABM report, {{listName}} ({{accountCount}} accounts)

Hi all,

The list was frozen on {{freezeDate}} and has not changed this month.

Moved: {{engagedCount}} accounts met the engagement definition, {{multiRoleCount}} of them with two or more roles. {{meetingCount}} meetings were held with list accounts.

Did not move: {{flatCount}} accounts had no activity from either team. The blocker on most of them is {{blocker}}.

Changing next month: {{oneChange}}. One change only, so we can tell what caused the difference.

Not due yet: pipeline and win rate. Our cycle is about {{cycleLength}}, so the first fair read on those is {{judgeDate}}.

Numbers and definitions are in {{scorecardLink}}.

{{senderName}}

Frequently asked questions