Field Mapping - A Merge feature that allows new fields to be attached to Merge Common Models.

Integration-Wide Field Mapping - A Field Mapping that applies across all Linked Accounts for a specific application.

Related Articles:

Any integration-wide field mapping is considered an organization_defined_targets in the API response — see below:

Example: You set a Linked Account-level target for your customer, Walmart (who uses Greenhouse), called prospect pool. You now want to create an Integration-Wide mapping for Greenhouse called prospect pool.

It will automatically be 're-associated’ to an organization_defined_target. This will be reflected in the Dashboard UI for Walmart’s Linked Account page:

Note that this will change the API response from the target field being returned as a linked_account_defined_targets to a organization_defined_targets. This change will be reflected on the subsequent sync!

If enabled, this will allow you to adjust the Origin of a specific Linked Account, using the existing Target Field you’ve already created.

This will not adjust the API response: the Target Field will still be returned as part of organization_defined_targets

If disabled, you will not be able to create a new mapping from the same origin field, but past linked account level mappings should not be affected.

When creating a Target Field in a Linked Account settings, you have the option to apply it to your Merge Organization's Field Mappings. This will allow you to map this Target Field to other integrations' Origin Fields.

When a field mapping change is made or a field mapping is deleted, we will not immediately kick off resyncs for linked account(s) automatically. The next resync (scheduled or forced) for any affected linked account will be a full resync. You can expect this sync to take longer than a normal sync, as it will be treated as an initial sync.