I wanted our demo request form to be a marketo form but our engineering team insisted on creating our own form and then having an API call into marketo (not sure why they refused to just drop the iframe code in from my pretty form). Because of this I can't use standard trigger campaigns based on "fills out form" instead I am needing to use a trigger of "lead is created and original source info = web service API or lead source = demo request". I am wondering if others have forms that sync via API that could give some guidance/best practices on how they manager their trigger campaigns. Some concerns that I have and am wondering if others have workarounds are:
Thanks in advance to anyone who can provide some advice!!
Not sure if this will help you. If your major fear is having the field update, you could block the field update from forms fills so the original source will never be overridden. You would go to administration/field management / click on the lead source field/ field actions / block field updates. You can drill down on what you want to block by clicking on block field updates.
Hope this helps.
If you use a server side form post, you can log a form fill activity in Marketo because this posts to a Marketo form (this allows you to continue to use the non-Marketo form). This blog post from our dev blog has more details on that:
This sounds very promising. I have passed this article to the dev team in hopes that we can create a "hidden" marketo form so it would allow me the marketo functionality and keep them happy w/ the form remaining in our homegrown format. I am not sure if we are using a "server side form post" but I hope this is the case! Thanks again!
Please do not use this method. I highly recommend this instead: http://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/
Lindsay, the decision to use an API call for every form post was reckless. You can tell your engineering team I said that.
I strongly recommend you change the architecture. You can still use your custom form but use a hidden form post as detailed by Marketo's Kenny E. Then you will no longer be inviting malicious use of your (and Marketo's) infrastructure, and you will be using real form posts so you can trap those events appropriately.
I'm also trying to use an external form to submit into Marketo (HR forms for job applicants) and read Kenny's article. However, I didn't understand how to reference the values in the external form so they'd match up with the corresponding hidden fields in the Marketo form (i.e. how we get email@example.com to be what the user inputted in the non-Marketo form). Can you provide any insight on how to accomplish that?
Thanks for your advice! As with the Server Side post I have passed this on to my dev team in hopes that this is a solution we can use. Unfortunately I am not very knowledgable on the API and coding aspects so I will need them to tell me if it is possible. Fingers crossed!! Thanks again
Certainly the client-side hidden form post is technically possible, since it doesn't involve server code at all (that is, if you didn't have a server you controlled, the server-side options wouldn't be available, but you almost always have control on the client).
There are 7 technologies I can think of that could all be described as "posting form data to Marketo." In decreasing order of preference:
Can you elaborate on the technical consequences of using (7)?
(4) seems like the clear way to go when you must use a custom form. Benefit of keeping the fills out form trigger and it's all client side.
Do you know if there's any rate limiting or other restriction as with a server-side post?