Account Field Mappings

Account Field Mappings define how account metadata is extracted from event properties and lead data. Mappings automatically populate account attributes used for scoring, segmentation, and analysis.

Understanding Account Field Mappings

Account Field Mappings answer: "How do we extract company information from our data?"

When events are tracked or leads are imported, they often contain company information:

• Company size
• Industry
• Revenue
• Employee count
• Geographic location

Account Field Mappings tell LeadVibe:

1. Which event/lead properties contain this data
2. What to name the account property
3. How to handle conflicts or updates

Accessing Account Field Mappings

Navigate to Configure > Rules & Scoring > Account Mapping.

How Mappings Work

Mapping Process

When an event is ingested or lead is updated:

1. LeadVibe identifies the associated account (via account_id)

2. Checks all account field mappings

3. For each mapping:

   • Extracts the source field value from the event/lead
   • Maps it to the target account property
   • Updates the account metadata

4. The updated metadata is then available for:

   • Account scoring rules
   • Account segmentation
   • Timeline and reporting
   • Integrations and exports

Example

Mapping Configuration:

Source Field: company_size
Account Property: company_size

Event Payload:

{
  "event_type": "page_view",
  "account_id": "acct_123",
  "company_size": "Enterprise"
}

Result: Account acct_123 now has company_size: "Enterprise" in its metadata, which can be used in scoring rules.

Creating Mappings

Add a Mapping

1. Navigate to Account Mapping

2. Click Add Mapping

3. Configure:

   • Source Field - The property name in events/leads
   • Account Property - What to call it in account metadata

4. Click Save

Mapping Configuration

Field	Description
Source Field	The property key in event payloads or lead data (e.g., company_size, industry, employees)
Account Property	The standardized property name in account metadata (e.g., company_size, industry, employee_count)

Important: Source field and account property can be the same or different. Use different names to standardize variations (e.g., map both company_size and org_size to company_size).

Common Mappings

Firmographic Attributes

Map company characteristics for account scoring:

Source Field	Account Property	Description
company_size	company_size	Small, Medium, Enterprise
industry	industry	Business sector
employees	employees	Number of employees
revenue	revenue	Annual revenue
country	country	Geographic location
state	state	State/province
city	city	City
domain	domain	Company email domain

Company Identifiers

Map identifying information:

Source Field	Account Property	Description
company_name	name	Legal company name
account_name	name	Company display name
website	website	Company website URL
domain	domain	Primary email domain

Subscription Data

Map customer lifecycle information:

Source Field	Account Property	Description
plan	plan	Subscription tier (Free, Pro, Enterprise)
mrr	mrr	Monthly recurring revenue
account_status	status	Customer, Prospect, Trial, Churned
signup_date	signup_date	When account was created
trial_end_date	trial_end_date	Trial expiration

Custom Attributes

Map business-specific properties:

Source Field	Account Property	Description
vertical	vertical	Sub-industry or vertical
use_case	use_case	How they use your product
account_tier	tier	Internal account classification
partner	partner	Partner or reseller affiliation

Managing Mappings

Edit a Mapping

1. Click the mapping row
2. Update source field or account property
3. Click Save

Changing a mapping applies to future events. Existing account metadata is not retroactively updated.

Delete a Mapping

1. Click ⋯ on the mapping
2. Select Delete
3. Confirm deletion

Deleting a mapping:

• Stops extracting that property from future events
• Does not remove existing account metadata
• Can be recreated if needed

Reorder Mappings

Order doesn't affect mapping behavior - all mappings are evaluated for each event.

Data Flow

From Events

When you track an event with account properties:

leadvibe.track('page_view', {
  account_id: 'acct_123',
  company_size: 'Enterprise',
  industry: 'Technology',
  employees: 2500
});

If you have mappings for company_size, industry, and employees, these values are extracted and stored in the account's metadata.

From Leads

When lead properties are set:

PUT /leads/{leadID}
{
  "account_id": "acct_123",
  "metadata": {
    "company_size": "Enterprise",
    "industry": "Technology"
  }
}

Account field mappings check lead metadata for matching source fields and update the account.

From Integrations

When syncing data from HubSpot, Salesforce, or other systems:

• Integration provides company properties
• Mappings extract relevant fields
• Account metadata is populated automatically

Mapping Strategies

Standardize Property Names

Use mappings to normalize variations:

Multiple sources, one account property:

• Map company_size → company_size
• Map org_size → company_size
• Map business_size → company_size

Now all three variations populate the same account property.

Consistent Data Types

Ensure account properties have consistent types:

Good:

• employees always a number: 100, 500, 2500
• revenue always a number: 1000000, 5000000

Bad:

• employees mixed: "100", "500-1000", "Large"
• revenue mixed: "$1M", "1000000", "High"

Inconsistent data types break scoring rules. Standardize at the source or use transformations.

Separate Account Properties from Profile Properties

Profile Mappings (lead-level) vs Account Mappings (account-level):

Profile Mappings:

• Individual attributes: job title, role, department
• Contact information: name, email, phone
• Personal preferences: language, timezone

Account Mappings:

• Company attributes: size, industry, revenue
• Firmographic data: location, employees
• Account relationship: plan, status, MRR

Don't mix individual and company properties.

Critical Restriction: Cannot Map account_id

LeadVibe prevents mapping account_id as an account property:

• account_id is a special field that links leads to accounts
• It must be set directly in events, via API, or through Profile Mappings
• Attempting to create an Account Mapping with account_id as the account property will fail

To link leads to accounts:

• Include account_id in your tracking events
• Set account_id via API (PUT /leads/{leadID})
• Use Profile Mappings to derive account_id from email domain or other lead properties

Best Practices

Map Only What You Need

Don't map every possible field:

• Focus on properties used in scoring rules
• Include attributes for segmentation
• Add fields needed for reporting
• Avoid mapping sensitive or redundant data

Start with 5-10 core mappings:

• Company size
• Industry
• Country
• Employees
• Revenue

Add more as needed.

Use Consistent Naming

Standardize account property names:

• Use lowercase with underscores: company_size, employee_count
• Be consistent across all accounts
• Match property names in scoring rules

Good: company_size, industry, country Bad: CompanySize, Industry Type, country_name

Document Your Mappings

Keep a reference of:

• What each mapping extracts
• Where source data comes from
• What the account property is used for
• Any special handling or transformations

This helps team members understand your data model.

Test Mappings with Sample Events

Before relying on mappings:

1. Create the mapping
2. Send a test event with the source property
3. Check the account detail page for the mapped value
4. Verify scoring rules recognize the property
5. Adjust if needed

Handle Missing Data Gracefully

Not all events will have all properties:

• Mappings only update if source field is present
• Missing properties don't overwrite existing account data
• Account metadata accumulates over time

Example:

• Event 1 includes company_size: Enterprise
• Event 2 includes industry: Technology
• Account metadata now has both company_size and industry

Review Mappings When Scoring Changes

When you update Account Scoring Rules:

• Ensure mappings exist for properties used in rules
• Verify account metadata is populated
• Test scoring with real account data

A scoring rule that references employees won't work if you don't have an employees mapping.

Use Enrichment for Missing Data

If events don't include firmographic data:

• Integrate with enrichment providers (Clearbit, ZoomInfo)
• Use reverse IP lookup for anonymous visitors
• Import account data from your CRM
• Manually populate high-value accounts

Common Use Cases

CRM Sync

Sync company data from Salesforce or HubSpot:

Source: salesforce_company_size → company_size
Source: salesforce_industry → industry
Source: salesforce_annual_revenue → revenue
Source: salesforce_employees → employees

Mappings automatically populate LeadVibe account metadata from CRM data.

Product Analytics

Extract account attributes from in-app events:

Source: account_plan → plan
Source: account_mrr → mrr
Source: account_status → status
Source: account_created_at → signup_date

Enrich accounts with product usage and subscription data.

Marketing Automation

Map attributes from marketing tools:

Source: company_segment → segment
Source: lead_source → source
Source: campaign_name → campaign
Source: utm_source → utm_source

Track which campaigns and sources bring in high-value accounts.

Form Submissions

Extract company info from lead forms:

Source: company → name
Source: company_size → company_size
Source: industry → industry
Source: country → country

Populate accounts when leads fill out forms.

Troubleshooting

Mapping Not Extracting Data

Problem: Created a mapping but account metadata isn't populating.

Solution:

• Verify events include the source field
• Check source field name matches exactly (case-sensitive)
• Ensure events have account_id set
• Review recent events to confirm property is present
• Test with a manual event to isolate the issue

Account Properties Not Used in Scoring

Problem: Account has metadata but scoring rules don't recognize it.

Solution:

• Verify account property names match scoring rule property names exactly
• Check for typos or case mismatches
• Ensure scoring rules are saved and enabled
• Confirm the primary ruleset is selected

Duplicate or Conflicting Mappings

Problem: Multiple mappings target the same account property.

Solution:

• This is intentional for standardizing variations
• Last mapping evaluated wins if values differ
• Consider which source is most authoritative
• Delete redundant mappings if causing issues

Account Metadata Overwritten

Problem: Account property keeps changing or reverting.

Solution:

• Check if multiple events update the same property
• Review which mappings affect the property
• Consider disabling mappings for properties that shouldn't change
• Use "last write wins" expectation for account metadata

Cannot Map account_id

Problem: Trying to create a mapping with account_id as account property fails.

Solution:

• This is intentional and enforced by LeadVibe
• account_id is a special field for linking leads to accounts
• Set account_id directly in events, via API, or through Profile Mappings
• Do not attempt to map account_id as an account property

API Access

Manage account field mappings programmatically:

• List Account Mappings
• Create Account Mapping
• Update Account Mapping
• Delete Account Mapping

Related Documentation

• Account Scoring Rules - Use mapped properties in scoring
• Account Management - View account metadata
• Profile Mappings - Map lead-level properties
• Event Tracking - Include account properties in events
• ABM Overview - Understanding Account-Based Marketing