Intent Data vs Firmographic Data

• Start with the account attributes that matter to your product and service area. HubSpot lists industry group, employee range, annual revenue and country or region among company enrichment properties.✓ 1
• Add a dated activity signal only when you know what was observed and at what level. 6sense defines intent data through research behavior and distinguishes first-party from third-party sources.✓ 2
• Apply permission and suppression rules before acting on a person-level record. UK ICO guidance says B2B use of personal data still engages UK GDPR and requires a lawful basis.✓ 4

1. What firmographic data can answer

Firmographics are account attributes. In common CRM enrichment, those fields include employee range, annual revenue, industry and country or region. They help a team express a target-account hypothesis in fields that can be filtered and reviewed. For example, a service with support only in certain countries may need geography as an eligibility rule, while a product built for a specific company size may need employee range. These are proposed decision rules, not measured claims that any one band buys more often.✓ 1

The word “static” can mislead. An industry's label may stay stable for a while, but employee counts, revenue bands and locations can change. Even an unchanged value can be misclassified or based on an estimate. HubSpot says all previous enrichment activities appear on the record's activity timeline, which gives a way to ask when a field was last enriched. Store the source and retrieval date as well as the normalized value before making a consequential routing decision.✓ 1

Firmographics do not establish fit by themselves. 6sense defines an ideal customer profile as a description of the type of company that gets the most value from your product, used to guide targeting and prioritization. That is a hypothesis about customer value, not an industry field or a purchased list. A team should state the use case, buying constraints and disqualifiers in plain language, then choose a small set of account attributes that approximate those conditions. Review exceptions manually when a company looks promising despite missing or ambiguous fields.✓ 2

LinkedIn's prospecting guidance illustrates the operational use: company headcount, company type, industry and geography can narrow an account list. Those filters are useful for surfacing candidates; they are not evidence that a surfaced company is evaluating your product. Preserve this distinction in the CRM by keeping account attributes separate from activity events.✓ 3

2. What intent data can answer

6sense uses “intent data” for digital signals such as content consumed, topics searched and review sites visited. It distinguishes first-party data gathered from an organization's own audience, including website visits, form submissions and CRM records, from third-party data aggregated by outside providers. When you receive a score, ask which underlying event, source, date and account-matching rule produced it. A score without that metadata is hard to audit.✓ 2

Activity is narrower than a confirmed purchase plan. A visit may be research, comparison, training, support work or curiosity. At the account level, the observed activity may not identify the actual buying committee. Do not turn a category-interest label into “the chief buyer is ready to purchase.” LinkedIn describes category interest as engagement with content, companies or conversations related to a product category. That still leaves the reason for the activity open.✓ 3

Intent signals also depend on the product and the observed surface. LinkedIn lists account buyer intent among its signals and says that feature is limited to Advanced and Advanced Plus. This is a product example of signal provenance and package scope, not a universal definition for all providers. Ask each data supplier what is first party, what is externally sourced, what is modeled and what the customer may actually inspect.✓ 23

If the signal is old, the next action may be different. A recent form submission might warrant a prompt response under your existing consent and routing rules; an old topic-surge score may only justify more research. Record the event timestamp, ingestion timestamp and any expiration rule separately. This is a recommended operating convention, not a claim that a fixed number of days predicts demand.

3. Combine them without inventing a multiplier

A practical sequence is to define account eligibility, review activity, identify a legitimate person or account owner, and choose a proportionate action. Start with the account properties that matter for the service, then add a signal column that records event type, source and date. 6sense describes rule-based workflows that can trigger alerts or list changes from account or contact activity. Use that capability to route a review task, rather than to declare a sale inevitable.✓ 12

This matrix is an editorial workflow, not a vendor performance test. There is no verified three-times conversion lift in the sources reviewed for this article. To evaluate whether the combined approach helps your team, compare cohorts drawn from the same target market and time period, using the same outcome definition. Keep acquisition channel, account size, product, seller and prior relationship visible. Do not present a change in who was targeted as proof that a data vendor caused the outcome.

Lead-to-account matching matters because events, people and companies are different entities. 6sense defines matching as linking a lead to an existing account or creating a new account where none exists. If you join a person-level event to the wrong company, a useful activity signal can be assigned to an irrelevant account. Keep the raw event and the matched account ID so someone can review ambiguous joins.✓ 2

4. Provenance, refresh and lawful use

For every company property, store the supplier, original value, normalized value and date seen. HubSpot's enrichment history is one example of a record-level audit trail. For each activity signal, store the observed event, source, account match, observed time and processing time. Assign different review windows to different fields and events based on their actual business use. Neither dataset should be silently overwritten by a later score.✓ 12

When person-level information is used for direct marketing, the applicable rules need a separate review. For the UK, the ICO says the UK GDPR still applies to B2B marketing that processes personal data; consent and legitimate interests are the two lawful bases it highlights as most relevant. It also says people must be told when their business contact details are used for direct marketing. This is UK-specific guidance, not a blanket permission to contact everyone in an account list.✓ 4

The ICO says processing for B2B direct marketing must stop when an individual withdraws consent or objects, and that the business or contact's details should go on a 'do not contact' or suppression list instead of simply deleting all record of them. Build that stop rule into account and contact workflows before automated alerts create tasks. The presence of an intent signal does not override a person's objection.✓ 4

FAQ

How we researched this

We reviewed four primary sources on October 3, 2026: HubSpot's company-enrichment documentation, the 6sense product glossary, LinkedIn's Sales Navigator prospecting guide and the UK Information Commissioner's Office B2B marketing guidance. The snapshots retain selected exact excerpts, one page per file. Vendor documents describe their own fields and features; the ICO guidance supplies the stated UK legal context. The proposed workflow and cautions are editorial inferences, with no claimed conversion multiplier or universal vendor ranking.