In the step-by-step instructions, #3 references appropriate token for the field containing the cookie value.
Todd’s post on how to do the association is totally on-point. But it does assume you have a way of storing the value of the Munchkin cookie (the cookie named _mkto_trk) in a hidden field on whatever form you’re using, so the field is in turn passed to Marketo and can be shuttled to FlowBoost.
This is very easy if you have sufficient control over the form — that is, if you can add hidden fields and either (a) the form provider automatically supports mapping cookie values to hidden fields or (b) the provider lets you add custom JS to the page to do the same thing.
Unfortunately, I don’t know that Splash offers either of these capabilities. They discourage user-injected JS in favor of having their professional services team add what you request, and their docs don’t mention cookies being used like this. You might ask them specifically: “Can I have a hidden form field that is automatically filled with the current value of a cookie?”
.png)