SanfordWhiteman

I just got reCAPTCHA working with Marketo forms. If you're interested, follow me and I'll follow you back and we can discuss it.

The concept is very easily foiled, since can be readily detected by a spambot and skipped over. You'd have better luck (but it's still just luck) having a standard , but hiding it via CSS instead. Other approaches using JavaScript to dynamically assemble the form post can make it harder still for...

If you you want the Thank You page as a page view in the ActLog, you can do a Munchkin.munchkinFunction('visitWebPage'...) in the onSuccess.

You put it in the HTML source view, right?And you probably didn't include this CSS:/* hide the last rich text div used to pass JSON translate map */.mktoFormRow:not([data-wrapper-for]) { display: none; }#translateMap { display: none; }What's the actual URL you're working on?

Yes, absolutely. But don't include those gt/lt (<>) symbols, and make sure to include or as well.

If you're missing the utm_medium and that can be assumed to be "email" for referrals from go.example.com, then you can update the GA info based on that:ga('create', 'UA-XXXXXXXX-X');if ( /^https?:\/\/go.example.com(\/|$)/.test(document.referrer) ) { ga('set','campaignMedium','email');}You raise an ...

Remove the .nth-of-type rule and try:.mktoForm LABEL[for="ContactSales"] { float: right !important; width: 210px !important; margin-top: 6px;}.mktoForm INPUT#ContactSales { margin-top: 8px;}

OK. They should use the Munchkin API (associateLead) for this project. Definitely avoid REST and SOAP APIs here because you'll just create an opening for a DoS attack. Those APIs should be used for bulk/server-to-server projects, not for proxying end user activities.

The margin-top is for the checkbox relative to its container. If you wanted the whole row to move down you'd apply margin to the row:.mktoFormRow:nth-of-type(2) { margin-top: 4px;}

But don't forget the other INPUT types which you can add to a Marketo form even if they don't show up in the builder...