Web form API Sync into Marketo - Not Marketo Form - Help! | Community
Skip to main content
Lindsay_Zanga
Lindsay_Zanga
Level 2
October 16, 2015
Question

Web form API Sync into Marketo - Not Marketo Form - Help!

  • October 16, 2015
  • 3 replies
  • 5728 views

Hi all,

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:

  • Right now when someone submits the demo request form the system would fill in the "lead source" field to be "demo request". However, if the lead is not net new to the system I do not want to override the original source with the new "demo request" source.  But if this is not overridden I do not know how I will know if someone submitted a demo request form or not.  Any ideas on how I could do a workaround? I was wondering if I could do a marketo field checkbox field that passes over via API to say demo request = True.  Then I could run my trigger campaign on "lead source = demo request" or "data value changes and demo request checkbox = true".  I have heard from some people that you shouldn't have more than 1 trigger per smart campaign - is this true? What are the implications of having more than one?

Thanks in advance to anyone who can provide some advice!!

Lindsay

3 replies

A
Anonymous
October 16, 2015

Hi Lindsay,


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.


Steve

    D
    Adobe Employee
    dadolyAdobe Employee
    Adobe Employee
    October 16, 2015

    Hi Lindsay,

    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:

    http://developers.marketo.com/blog/server-side-form-post/

      Lindsay_Zanga
      Lindsay_ZangaAuthor
      Level 2
      October 16, 2015

      Hi Mel,

      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!

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      October 16, 2015

      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.

        Conor_Fitzpatri
        Conor_Fitzpatri
        Level 5
        October 16, 2015

        Hi Sanford,

        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 test@example.com to be what the user inputted in the non-Marketo form). Can you provide any insight on how to accomplish that?

        Terms & ConditionsAccessibility statement

        Loading footer...