API Merge functionality for Boolean fields

Prior to March 2026, a boolean FALSE value was treated as "no value" during an API merge. This meant that if either of the merged leads had a TRUE value, the result would be TRUE. But in cases when FALSE was an important value, it could cause problems (for example, if a lead's value changed and then merged with an old record, the value could be erroneously reverted back). This behavior was different than other field types.

In the March '26 release, Adobe fixed this issue. For API merges, Salesforce merges when they are synced to Marketo, as well as Automerge (if you have it configured); only NULL values in boolean fields are treated as "No Value" when determining which lead to take the value from.

The result is that the conflicting field values are now taken from the "winning" record (the resulting lead or contact), unless the winning lead has NULL for that field and the "losing" record (the one disappearing) has a value (TRUE or FALSE). Standard Marketo boolean fields, such as Unsubscribed, will always have a value (TRUE or FALSE), so these will be taken from the winning lead in all cases.