Perfect that worked wonders thank you!
One quick question:
The hidden <select> field is missing the default "Select..." from the options. All the non hidden ones have it properly, but for the hidden field for some reason it's missing so it's just blank. I compared the hidden with the non-hidden ones and the ONLY difference is Visibility Rules: Enable.
I'm curious why that is just missing when something is set to hidden. Any ideas?
Some pics for reference..
Form loaded (my existing product is the hidden field)
This picture shows 2 select in the marketo settings and they have no differences other than the visibility settings.
This is the hidden field setting it shows that "Select..." is there but on the form itself it dosn't show in the HTML.
Edit: nvm i figured it out was in the visibility settings i had to add the fields again but didn't have the "Select...|"
... View more
OK. To start off with more precision: it's Munchkin (the Munchkin JS library) that sets the _mkto_trk cookie, not the form. You can embed a Forms 2.0 form without Munchkin, and thus without a (new) cookie. And you can (and should) load Munchkin even if there's no form. You definitely don't need to always create, then delete the cookie (that's actually a violation of the promise you're making to the end user). First and foremost, you need to defer running Munchkin.init() at all until you have their opt-in. On a non-Marketo page this should be extremely easy, since you have full control over what runs when. Check to see if there's an existing LastPreference cookie set to Accept, and if not, wait for the onAccept event to fire, and then run Munchkin.init() . In the onAccept listener, also set a secondary LastPreference cookie -- if your cookie consent manager doesn't already set one -- indicating that their last action was Accept, so you can consult this later. If the onRevoke listener, set the LastPreference to Revoke for later. Delete any existing cookies. Do not run Munchkin.init() . You can also set ?mkto_opt_out=true in the query string, which will force Munchkin to not track from that point onward (until switched to false ). But this feature can be difficult to coordinate with 3rd-party managers, and if you get your code right, you don't need it.
... View more