9 Replies Latest reply on Oct 27, 2017 12:23 PM by Sanford Whiteman

    What is your preferred method for forms?

    Anita Singh

      We have a discussion going at work and I'm curious what others think.


      These are the options I know that exist at this time:


      • Marketo landing pages living in the larger website. This entails having all the links on the website go to Marketo landing pages. These can either have the same form or have their own form in the program.
      • Marketo embedded forms for the CMS. This would mean that every asset on the website has its own form.
      • Marketo blind form. Allows you to pass the information from the CMS form into Marketo and have it still show as a form submission. Can have just one form for many CMS pages.
      • Marketo API with the CMS. The CMS passes the form information directly into the activity log.


      Which method do you use? How does it affect your lead scoring and nurture programs? What do you do to make it scalable for your team?

        • Re: What is your preferred method for forms?
          Sanford Whiteman

          Why would "Marketo embedded forms for the CMS" mean one form per asset? That sounds like an assumption that's getting ahead of your call for recommendations.


          Also the 4th bullet is not an option for a professional site, so it's difficult to weigh the pros and cons with that in the mix.

          • Re: What is your preferred method for forms?
            Sanford Whiteman

            Add the asset URL as a hidden field, or add it directly to the form's onSuccess. I don't know why anyone would not mention these common options to you.

            1 of 1 people found this helpful
              • Re: What is your preferred method for forms?
                Anita Singh

                Thank you! That's a great option

                • Re: What is your preferred method for forms?
                  Anita Singh

                  Hi Sanford,

                  My web team is unsure of how to implement what you recommended. We definitely want to not have two buttons on our gated content pages, but how to do it with an embed form to only one form is causing the dilemma.


                  Here's the response I have from them:


                     Here’s the state of where we are at now:


                  • We ”gate” select digital assets (PDFs, videos) on RSA.com behind Marketo forms
                  • These Marketo forms are placed in iframes
                  • These forms have no styling, look very plain, and have a few minor usability issues on mobile devices
                  • The RSA.com page, looking equally plain, has an inactive hyperlink (in its default state ) to view the gated asset
                  • The Marketo template includes a snippet of JavaScript to activate the hyperlink, allowing the visitor to view the gated asset
                  • The “trigger” for hyperlink activation is a successful submission of the Marketo form


                     As I understand it, by switching from iframe-based forms to JavaScript embedded forms, we lose the ability to host the JavaScript in Marketo (since there’s no Market template in this scenario), and we lose the “trigger” event that activates the hyperlink.  We could easily move the JavaScript to the RSA.com page, but we are dead in the water if we have no “trigger” event to unlock the hyperlink.  Without it, we just have normal hyperlink to the digital asset, and a form that no longer serves as the gate to view that asset.  And very few people will fill in the form unless they need to, which would significantly reduce the number of leads that we collect.


                     So, the big question is “what can we use to replace the ‘trigger’ event if/when we shift to JavaScript embedded forms?”


                     For reference, (with apologies for obnoxious use of font color), here’s the JavaScript for the current “trigger” event that unlocks the hyperlink:


                  MktoForms2.whenReady(function (form) {

                  // unrelated stuff deleted...


                  form.onSuccess(function (values, url){




                  // more unrelated stuff deleted...