Unified Mapping

​

Control Where Your Data Comes From

Unified Mapping gives you one place to control where every field of your customer data comes from. Each field on each entity reads from one or more sources: Salesforce, your data warehouse, Segment, Amplitude and Inflection resolves them into a single unified record (the golden record) that powers your dynamic lists, journeys, tokens, and personalization across the platform.

​

Open the Mapping Page

Click Connections in the left navigation, then click Unified Mapping. The Mapping page has one tab per entity: Contact Mapping, Account Mapping, Opportunity Mapping, Product User Mapping, Organization Mapping, and Product User Organization Mapping plus a Change Log. Each tab lists the entity’s fields, their sources, and their settings. Click How mapping works in the top bar any time for an in-product explainer.

​

The Six Entities

​

How Mapping Works

​

The Unified Record

Each field reads from one or more sources. Inflection resolves the sources into one value per field, the unified record, and that value is what you filter on, personalize with, and trigger from everywhere in Inflection.

​

Backfill and Resolution

Resolution runs when a source sends an update. Here’s which changes reach back into records you already have: Applies from the next source update Backfills existing records

​

Sources and Priority

Every connection is its own source block. The Salesforce block contains both Contact and Lead properties for Person fields; each data warehouse connection, Segment, and Amplitude are separate blocks. When a field has more than one source, choose how conflicts resolve:

• Priority order: the first source in the list that has a value wins. Reorder sources with the arrows next to each source number.
• Last wins: the newest change across all sources wins.

Contact and Account fields support both modes. Product User, Organization, and Product User Organization Mapping fields resolve with last wins. Opportunity fields have a single source (Salesforce).

​

Accept Null Values

By default, when a source’s value for a field is blank or null, that source is skipped and the next source that has a real value wins instead. Turn on Accept null values for a source to let its blank value win its priority slot and clear the field, which is useful when an empty value is a meaningful signal. Leave it off for sources like event streams where blanks are just noise.

​

Editing in Inflection

The Editing toggle controls whether a field can be changed from inside Inflection: forms, manual edits, CSV uploads, Journeys, Webhooks, and Data Normalization. When on, Inflection edits compete with the sources on a last-write-wins basis. Turn it off to make the field read-only on all Inflection surfaces.

​

Write Back to Salesforce

The Write back toggle sends the unified value back to Salesforce. It requires Salesforce to be one of the field’s sources, and when the field uses Priority order, Salesforce must stay at the top of the order. The page enforces this and shows Salesforce must stay at the top while write-back is enabled. Blank values are never written back: Inflection only updates a Salesforce field when the unified record has a non-empty value.

​

Map a Field to a Source

1. On the entity’s tab, click Edit mapping.
2. Find the field. Use Search fields to filter the list.
3. Click + Add source on the field row.
4. Select the connection block (for example, Salesforce, Segment, or your warehouse connection).
5. Select the source property to read from. For Salesforce Person fields, set the Contact and Lead properties.
6. Optionally turn on Accept null values for the source.
7. Click Save changes.

To remove a single source from a field, click the × on its source block. The field itself and its current values are preserved, and the remaining sources continue to resolve.

​

Create a Custom Field

1. Click + Add new field on the entity’s tab.
2. Enter a Field name. Names are case- and space-insensitive.
3. Select a Field type — String, Number, Boolean, or Datetime.
4. Optionally add a Description (up to 300 characters) so your team and Inflection’s AI agents know what the field represents.
5. Click Add field.

​

Delete a Custom Field

Only custom fields can be deleted: system, default, and Inflection-managed fields are protected. Deletion is blocked while the field is in use by journeys, segments, exports, or forms, while changes are still saving, or while another delete is in progress. Inflection runs a dependency check and asks for confirmation before removing anything.

​

Field Descriptions and Insights

Click Add description or Edit description under a field name to document what the field represents. Descriptions appear here and in Insights from data dictionary wherever you build filters. Click the book icon next to a field name to open Insights from data dictionary for that field — how many records have a value (populated count and percentage) and a searchable list of distinct values sorted by frequency.

​

Track Mapping Changes

Click Change Log to see every mapping change in the workspace — date and time, entity, change type (for example Field created or Mapping changed), the field, and who changed it. Filter by field name or date range, and click Show details on any row.

​

Fields You Can’t Map

• Identity fields (marked Identifier) uniquely identify records and cannot be mapped — for example Person Inflection ID and Email, Account Account Id, and Opportunity Opportunity ID.
• System fields are managed by Inflection and cannot be edited.
• Inflection-managed fields, such as account scoring fields, always have Inflection as their locked source — no external source can be mapped to them.
• Unsubscribed always allows Inflection edits, and when Salesforce is one of its sources it always writes back — this keeps opt-outs consistent everywhere.

​

Common Use Cases

• Keep Salesforce authoritative with product data as backup. Put Salesforce first in the Priority order and Segment second — Salesforce wins whenever it has a value, and Segment fills the gaps.
• Let the freshest system win. Use Last wins on fields fed by both your warehouse and product events so the most recent update always shows.
• Lock a field against manual changes. Turn Editing off to make a warehouse-owned field read-only in forms, CSV imports, and manual edits.
• Push enriched values back to your CRM. Map a field from your warehouse, turn on Write back, and Inflection keeps the Salesforce field up to date.

​

Frequently Asked Questions