> Field mapping

TL;DR: Unstuck Engine records carry standard, targeting and signal-context fields. Destinations have their own schemas, and field types must be compatible between the two.

The fields

Unstuck Engine has ~30 fields per Lead and ~25 per Account. Destinations have their own schemas.

Three categories of fields:

• Standard — email, first name, last name, company name, title, phone, LinkedIn URL.
• Targeting — ICP code, Persona code, ICP score, Persona score, engagement stage.
• Signal context — last signal type, last signal at, signals count.

Behavior on sync

For each member synced:

1. Unstuck Engine reads the current value of each field on the record
2. POSTs (create) or PATCHes (update) the destination record
3. The overwrite policy decides whether to overwrite existing destination values (Overwrite / Append / Skip-if-exists)

Field type compatibility

Field types must match between Unstuck and destination:

Unstuck type | Compatible destination types
string | string, text, picklist (if value matches), email, url
number | number, integer, decimal
boolean | boolean, picklist (yes/no)
date | date, datetime
string[] | multi-select picklist, text (comma-joined)

Related

• Connecting a destination
• Pushing an audience to a destination
• Using the Signals API