Cookie hidden fields don't work if custom html is used for known visitors

Hi Nick,

Log ideas rather than questions . People can vote and they are reviewed by Product Management.

Idea 1: pre-fill known fields

There are a lot of discussions and ideas already in the community on this. To make it short, there are good data security reasons for not doing this as someone could use your JS code to steal your data.

Idea 2: "If Known Visitor, Show:" custom html

Worth and idea so that we can vote for. Can be worked around with javascript, though.

-Greg

Nick, you can reenable cookie (and query param) support via the code here: MktoForms2 :: KL HTML w/Auto-Fill

Note the dependency on the FormsPlus::Util (the <script> in the HTML pane).

Once you have that set, the only part you need to change is this little JSON block:

   var hiddenFieldMap = {
      Last_Result__c: {
         channel: "query",
         selector: "utm_results"
      },
      Field_From_Cookie: {
         channel: "cookie",
         selector: "ahoy_visitor"
      },
      Another_Field_From_Constant: {
         channel: "constant",
         selector: "Always use this value."
      }
   };

Hopefully, this is nearly self-explanatory...

• the top-level properties (Last_Result__c, etc.) are the Marketo form field names
• you set the channel (this is the term used by the Forms 2.0 API, so I reused it here) to either "query", "cookie", or "constant"
• set the selector to the specific place to pluck the value from (the name of the cookie or query param to look for, or a static string in the case of "constant")

Sanford Whiteman‌ - This is awesome! Thank you for this script. It worked perfectly!

One question - is there a way to set default utm_params with this script? For example, in the event that a return visitor comes to a page with Custom HTML set, and there are no utm parameters defined in the URL, we still want to attribute their visit with some type default utm params.