User-level vs account-level analytics
A sales rep asks for a report by account. What they want to know is whether the company is worth their time, and who to call. The two answers sit at two different levels.
User-level data describes what one person did: the pages they read, the content they downloaded, the features they tried. Account-level data groups those people under the company they work for, so you see how many are involved, how active they are and where the company stands in your funnel. Account-level reporting tells you which companies to work on. User-level data tells you who to talk to inside them.
Finance team, Halden Group No opportunity in the CRM
- 4 people active this month
- 2 guides downloaded
- 3 visits to the pricing page
- 1 trial started
| Person | Recent activity |
|---|---|
| Finance managerPerson to call | Started a trial, back on the pricing page 2 days ago |
| Controller | Read the pricing page |
| Financial analyst | Downloaded a guide, read the pricing page |
| Financial analyst | Downloaded a guide |
One analyst's download is a lead like many others. Up at the account, four people from one team show a project. Back down at the person, the manager who started the trial is the one to call.
Start from what you want to know
The question decides where a report starts and where it ends. Most commercial questions need both user-level and account-level data, in a different order.
| What you want to know | Start from | End with |
|---|---|---|
| Which companies to work on | Accounts: how many people, how active, which stage | The teams involved inside each one |
| Who to call in an account | The account's contacts and users | The one whose role and activity fit the offer |
| Which campaigns work | The leads each campaign brought | The opportunities on their accounts |
| Whether a customer is at risk | The account's usage and renewal date | The users who stopped being active |
When several people from one team read the site, download content or start a trial within a few days, there's often a project behind it. That's a good moment to reach out, and the account alone won't tell a rep which of its twenty contacts to call first.
Who the person is changes what the activity means. A university account full of student sign-ups is easy to dismiss, yet one of them may be someone from IT evaluating the product for the whole campus. And a CTO who downloads a white paper looks like the obvious contact, but an IT manager who has tested the product all week is the person to reach now.
The same choice shapes the message
Marketing faces the same choice. Data at the account level lets a campaign speak to the company as a whole: why the project matters to the business, which teams are already involved, what each person weighing the decision needs to hear. That's what account-based marketing is for, and it only pays off when it serves a sales objective.
Data at the person level lets the message follow what someone has actually done: the guide they read, the feature they tried, the page they keep coming back to. A follow-up that picks up from there usually lands better than one written for a job title alone.
Before you trust an account view
People sign up with personal email addresses, subsidiaries use their own domains, and one group can appear as several accounts in the CRM. Each of these splits a company into fragments or leaves people outside it.
3 to check · 1 OK
- OKLeads matched to an account by email domain78% of leads
- CheckPersonal email addresses, matched through enrichment or by hand13% of leads
- CheckSubsidiaries on their own domain, not linked to the parent account6% of leads
- CheckGroups split across several CRM accounts3 groups
The account itself can mislead. When a product is used by one department, the CRM account still covers the whole group, so a few active users can look like a small footprint in a large company, or like broad adoption when they all sit in one team. Read the account together with the teams behind it.
A grouped signal still needs context. A partner may start a trial to test the product for a client, an existing customer may sign up its staff for trials to train them, and a department may not know its company already holds licences. Each looks like new interest, and each calls for a different conversation.
In Funnelsight, activity can be filtered by account or by person, and you switch from one view to the other in a click, without a second export.
Move from the account to the person, and back, in one view.
Start free trialHow do you build an account-level report?
Start by matching every lead and product user to the company they belong to, by email domain first, then through enrichment and the CRM's parent accounts. Then choose what to count for each account, such as the people active this month, the funnel stage reached and product usage. Keep the list of people one click away, because the account tells you which companies to work on and the people tell you who to contact.
How does lead-to-account matching work?
Matching usually starts with the email domain, then fills the gaps: enrichment data for people who sign up with a personal address, the CRM's parent and child accounts for subsidiaries, and a manual review of the leads that remain unmatched. Agree on the rules once, so marketing and sales count the same accounts.