I've bookmarked several pages that used to exist on the Developers site (http://developers.marketo.com/ ). Now that the site's been redesigned, none of them work. At the moment, I'm trying to access the documentation that existed in Kenny's blog blog post: http://developers.marketo.com/blog/server-side-form-post/ . And nothing comes up when searching for this.
Kenny Elkington, is this still available?
We've got redirects in place for almost all old URLs on the new site. If you find any broken links, please report them to firstname.lastname@example.org. That post, however, was intentionally removed as it's not a desirable usage, and causes a lot of issues. We've released a new endpoint which covers all of the cases of that functionality which you can see here: http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Leads/p... It should be available to all clients by Monday.
Thanks Kenny, but I'm not finding an appropriate usage for our case. When syndicating our content on third-party networks, users are required to first submit a form on these sites (these are not our forms; and more than likely, these are new leads that have never been cookied (and won't be, since these aren't our web pages). In the past these leads would also be sent to our Marketo instance - into a dedicated program - using a post URL. What is the recommended approach to use for this now?
For example, let say the user submitted their name and email address with this form. As part of OnSubmit, this POST URL would be called so that the lead would also be entered into our instance of Marketo in real time:
Following are the parameters:
Hit my email (or phone, I think you have it) and I can tell you what's up with this.
Please use this method if you need client-side submission for some reason: http://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/ It's supported, unlike ss post.
Kenny, I'm a huge user + fan of the background form.submit(), but it doesn't patch all the gaps because you must have some control (either political or technical) over the client-side code. For example, I've been able to get boutique LP agencies to convert to background submit instead of bouncing off their own servers, bur 3rd-party services like Unbounce must use classic form post to work (their Marketo "integration" is broken, and their webhook integration doesn't support Marketo REST semantics).
It hasn't been officially supported for awhile, with good reason since a moderately successful campaign can overrun rate limits and cause lost data. On the other hand there are some situations in which it is the only choice, and even with the chance of data loss it's better than nothing.
The good news is as long as the forms endpoint is up, there will always be --technically -- post support.
Agreed, it is the ugliest choice of all available, but for the aforementioned reasons it is sometimes the only one available.