Skip to main content

Mapping

Mapping connects incoming event data to standardized fields that LeadVibe uses for profile and account scoring. Without mappings, LeadVibe can only score leads based on what they do (behavioral events). With mappings, LeadVibe can also score leads based on who they are (demographics, firmographics, and company attributes).

Why Mapping Matters​

When events arrive in LeadVibe, they often carry metadata -- extra details like a lead's job title, company size, or industry. Mapping tells LeadVibe which metadata fields correspond to which profile or account properties, so the scoring engine can evaluate leads based on attributes as well as actions.

Example: An event with metadata {"job_title": "VP of Sales", "company_size": "201-500"} is useful only if LeadVibe knows that job_title maps to the profile property contact_job_title and company_size maps to company_employee_count. Mapping makes this connection.

Profile Mapping​

Profile mapping links event metadata fields to lead profile properties. This enables profile scoring, which evaluates how well a lead matches your ideal customer profile (ICP).

Navigate to: Configure > Mapping > Profile

Profile mapping configuration showing source fields mapped to profile properties

How Profile Mapping Works​

  1. Select an event type to view the metadata fields available from that event type
  2. Map source fields to standardized profile properties by pairing each incoming metadata field with a target profile property
  3. Choose update behavior to control how mappings handle existing data:
    • Always Latest: Overwrites the profile property with the most recent value every time a matching event arrives
    • Only If Empty: Sets the profile property only when it has no existing value, preserving the first value received

Common Profile Mappings​

Source Field (Event Metadata)Profile PropertyPurpose
job_titlecontact_job_titleScore leads by role seniority
company_sizecompany_employee_countPrioritize enterprise vs. SMB leads
industrycompany_industryTarget specific verticals
senioritycontact_seniorityWeight decision-maker engagement higher
company_revenuecompany_revenueFocus on high-value accounts
locationcompany_locationGeographic targeting

Setting Up Profile Mappings​

  1. Navigate to Configure > Mapping > Profile
  2. Select an event type from the dropdown to see available metadata fields
  3. For each field you want to map, select the target profile property from the dropdown
  4. Choose the update behavior (Always Latest or Only If Empty)
  5. Click Save Mappings to apply your changes

Backfilling Existing Leads​

If you set up profile mappings after leads have already been created, you can retroactively apply mappings to all existing leads:

  1. On the Configure > Mapping > Profile page, click Backfill Profile Metadata
  2. LeadVibe processes all existing leads and populates profile properties from their historical event metadata
  3. The backfill respects your update behavior settings -- if set to "Only If Empty," leads that already have a value will not be overwritten

Backfilling is safe to run multiple times. Leads that already have the correct metadata are skipped.

Account Mapping​

Account mapping links event metadata fields to account-level properties. This enables account scoring, which evaluates how well a company matches your target account profile.

Navigate to: Configure > Mapping > Account

Account mapping configuration showing source fields mapped to account properties

ABM Feature

Account mapping is available when Account-Based Marketing (ABM) is enabled in your organization's scoring settings. Navigate to Settings > Scoring and enable the ABM toggle to access account mapping.

How Account Mapping Works​

Account mapping follows the same principles as profile mapping, but targets account-level properties instead of lead profile properties:

  1. Map source fields from event metadata to standardized account properties
  2. Choose update behavior to control how existing account data is handled
  3. Save to activate the mappings

Common Account Mappings​

Source Field (Event Metadata)Account PropertyPurpose
company_domaindomainAssociate leads with accounts
company_industryindustryScore accounts by vertical fit
company_sizeemployee_countPrioritize by company size
company_revenueannual_revenueTarget revenue tiers
company_namenameDisplay company names in reports

Backfilling Existing Accounts​

Similar to profile backfilling, you can retroactively apply account mappings to existing accounts by clicking Backfill Account Metadata on the Account mapping page.

The Mapping and Scoring Workflow​

Mapping is one step in a larger scoring workflow:

  1. Send events with metadata: Include profile and account data in your event payloads (via API, web beacon, or integrations)
  2. Create mappings (this page): Tell LeadVibe which metadata fields map to which properties
  3. Create scoring rules: In Configure > Scoring > Profile (or Account), create rules that award points based on mapped property values
  4. Scores update automatically: As new events arrive, LeadVibe maps metadata to properties and evaluates scoring rules in real time

Best Practices​

Map Early​

Set up mappings before importing large volumes of data. This way, profile and account properties are populated as events arrive, avoiding the need for large backfill operations.

Use Consistent Metadata Keys​

Coordinate with your development team to ensure event metadata uses consistent field names across all sources (API, web beacon, CRM integrations). Inconsistent naming (e.g., job_title from one source and jobTitle from another) requires separate mappings.

Choose Update Behavior Carefully​

  • Use Always Latest for fields that change over time (job title, company size)
  • Use Only If Empty for fields where the first value is most reliable (original lead source, signup date)

Start with High-Impact Fields​

Focus on mapping the fields that will have the biggest impact on lead prioritization:

  1. Job title / seniority -- Identifies decision-makers
  2. Company size -- Distinguishes enterprise from SMB
  3. Industry -- Enables vertical-specific scoring

Troubleshooting​

Mapped Fields Not Appearing on Leads​

  • Verify that the source metadata field name exactly matches what appears in your event payloads (field names are case-sensitive)
  • Check that events with the relevant metadata have been ingested after the mapping was created
  • If leads existed before the mapping, run the backfill operation

Backfill Not Updating Leads​

  • If update behavior is set to Only If Empty, leads that already have a value for that property will be skipped
  • Verify that the event metadata actually contains the source field you mapped