Skip to main content

Account Field Mappings for ABM

Account Field Mappings turn raw event metadata into the firmographics that drive your ABM program — industry, company size, revenue, region, and any custom signal that defines a target account. This page focuses on the ABM strategy behind account mapping. For the configuration walkthrough — UI, source fields, update behavior, backfill, history — see the canonical Account Mapping page.

Why Account Mapping Matters For ABM​

ABM lives at the company level. You can't tier accounts, route territories, or coordinate plays without firmographic data on every account in your pipeline. Account mapping is what turns the metadata your tracking already collects into the structured, scorable, segmentable account fields ABM needs:

  • Account scoring depends on it. A rule like "+25 if industry is SaaS" silently does nothing without a mapping that populates industry.
  • Account-level segmentation depends on it. Audiences like "Enterprise SaaS in EMEA" only exist if industry, employee_count, and region are populated on every account.
  • Sales prioritization depends on it. AEs can't tier accounts without seeing fit signals; account mapping is what makes those signals visible.
  • Integrations depend on it. Pushing tier and fit data to Salesforce, HubSpot, or Slack only works if your accounts carry the firmographic fields those systems expect.

If account scoring is "off" or accounts feel under-tiered, look at mapping coverage first.

What To Map First​

Most ABM teams start with the same shortlist. These are the highest-leverage signals — covering them first gets you 80% of the value.

Tier 1: Core Firmographics​

Account PropertyWhat It Drives
industryVertical fit, ICP gating, vertical-specific plays
employee_countSize band (SMB / Mid / Enterprise), pricing tier eligibility
country / regionTerritory routing, regional campaign assignment
domainStable identity, deduping, integration matching

Tier 2: Pipeline Signals​

Account PropertyWhat It Drives
annual_revenueRevenue-tier targeting, deal-size forecasting
planFree / Pro / Enterprise scoring (PLG motions)
account_statusCustomer / Prospect / Churned segmentation
mrrExpansion-targeting and CSM workload

Tier 3: Vertical-Specific​

Anything custom to your motion: vertical, tech_stack, funding_round, parent_company, sub_industry, compliance_required, etc. Add these as your scoring model matures.

For the full set of common mappings and the configuration UI, see Account Mapping.

Where Account Mapping Data Comes From​

ABM teams typically source firmographics from a mix of inputs. Account mapping doesn't care where the metadata originates — it only cares that the field is on the event payload. Common sources:

  • CRM sync. Salesforce or HubSpot company fields surfaced through the HubSpot integration or webhook ingestion.
  • Enrichment providers. Clearbit, ZoomInfo, or similar — push enriched firmographics into your event stream and map them onto accounts.
  • Web tracking. Reverse-IP lookup or self-identified company data on form submissions, included in Web Beacon events.
  • Manual import. CSV import for a strategic-account list with hand-curated firmographics.
  • Product events. For PLG motions, in-app events naturally carry plan, mrr, account_status, and similar lifecycle fields.

The mapping layer is what unifies these sources. Map each provider's field-naming convention onto a single canonical account property and the downstream scoring and segmentation work consistently regardless of source.

ABM Strategy: Map for the Plays You Run​

A property is only worth mapping if a play depends on it. Before you add a mapping, answer:

  1. What scoring rule, segment, or trigger will consume this field?
  2. Which team member(s) will see it surfaced in the UI?
  3. What action changes when this field is populated vs. empty?

If you can't answer all three, the mapping is premature. Trim aggressively — a small, well-curated set of mappings produces cleaner scoring than a sprawl of half-populated fields.

Common ABM Mapping Mistakes​

  • Skipping account_id on events. Account mappings only fire on events that already carry an account_id. If your tracking doesn't include it, derive it via Profile Mapping (e.g. from email domain) before expecting account fields to populate.
  • Inconsistent data types. employee_count should always be numeric. Mixing "500", "500–1000", and "Mid-market" breaks numeric scoring rules. Pick a type per field and standardize at the source.
  • Mapping fields no scoring rule uses. Adds noise without value. Mappings should be downstream of a scoring or segmentation decision, not upstream.
  • Forgetting to backfill after a mapping change. New mappings apply to new events only. If you've changed sources or naming, run a backfill so existing accounts catch up.
  • Hand-mapping custom fields when an integration already exposes them. If your CRM already has industry standardized, prefer the integration field over a custom industry_v2 mapping.

Where To Go Next​