Hey Gerard, Had to laugh when I read this post; you and I are taking a VERY similar approach to this, bud! I also worked out that booleans don't like being added to strings. And there's another gotcha, too... Marketo will write a datetime to a string in the instance timezone... So, what I've done to overcome this is to change my Consent - Change Log (which is similar to your Consent Notes field) using choices in the Change Data Value flow step Choice 1: If Consent - Preference - Information Opt-In is 'true' Attribute: Consent - Change Log New Value: '{{lead.Consent - Preference - Information Timestamp}} (EST). User changed INFORMATION Opt-In to TRUE. {{my.linebreak}}{{lead.Consent - Change Log}}' Default choice: Attribute: Consent - Change Log New Value: '{{lead.Consent - Preference - Information Timestamp}} (EST). User changed INFORMATION Opt-In to FALSE. {{my.linebreak}}{{lead.Consent - Change Log}}' This checks the value of the relevant opt-in field and then writes the timestamp (with the instance timezone specified) and then hardcodes the change that was made to the opt-in. The bit at the end is a bit of 'Whiteman Wizardry'... it basically prepends the new change to the old one, but instead of using a pipe, it uses a token linebreak. Almost done with my Preference Centre... it's been a slog!! Good luck! g
... View more