Field mapping is set inside each destination step of the bridge builder, not once for the whole bridge. That means one contact can arrive in Slack with a full name, in your autoresponder with a first name only, and in a spreadsheet with everything the source sent.
First name options:
- Pass through. Use whatever the source gave you. This is the default.
- Static. Send the same fixed value for every contact, useful when a destination requires a name field you do not care about.
- Derive from email. WP Sync takes the part of the address before the at sign, cuts it at the first dot, underscore, hyphen or plus, and capitalises it. So an address beginning jane.smith becomes Jane.
- Fallback. A value used only when the resulting name would otherwise be empty. This is the fix for destinations that reject a blank name.
Last name options:
Pass through, static, or fallback. There is no derive from email option for the last name, because an email address does not reliably contain one.
Email:
The email address is passed through from the source. It is the key that identifies the contact in every destination, so it is not rewritten by the mapping.
All fields for auto capture destinations:
Destinations that record whatever they are given, such as a spreadsheet, receive every scalar field the source provided, with the mapped name and email on top. Sensitive keys are stripped before this happens, so passwords, secrets, signatures, hashes, API keys and access tokens never land in a sheet.
Older bridges:
Bridges saved before per destination mapping existed still work. Their single bridge level mapping is applied to every destination, and it is shown to you when you open the bridge for editing.