Kenny_Elkington

You're probably looking for the "Created At" attribute. This records the first date of creation and should be preserved through merges

This is already available, you just need to pass the additional parameter 'isExecutable' and set it to true. I'll make sure this gets into the next documentation release

@Mike_Crook7 Self-Service Flow Steps is currently in closed beta. This will allow customers and partners to implement services that can be deployed as flow steps within Marketo. There's some development required, but you can build a service to call our custom object apis in order to perform CRUD ...

What you're suggesting really is not possible. Without the customer identifying themselves and attaching their identity to the cookie value there would be no way to look up data from that person's record. That said, you do not need to use the munchkin cookie to leverage that method, you can use an...

Changing this would make it so that you could not rely on Data Value Changes in flow step choices following a Call Webhook step, which is an important and common use case.

We don't have any plans to update existing webhook functionality. We're actively working on a new feature to supplant them, and we're planning to go into open Beta sometime early next year.

There are several options to do this on Marketo Landing Pages including Greg's great example here. We have no plans to make this a feature available via form embed code. You can set default values either static or dynamic with the Forms JS API See the "Set Values on Hidden Fields on the Form" Exa...

We're testing a solution to this and hoping to make it available early next year