SOAP APIs on Multiple Pages - Best way to categorize? | Community
Skip to main content
A
Anonymous
June 23, 2015
Question

SOAP APIs on Multiple Pages - Best way to categorize?

  • June 23, 2015
  • 2 replies
  • 2050 views

At the moment, I have the same SOAP API on multiple external landing pages - how best can I group these by source page? e.g. the form fills are for different things, but collecting the same information - does an extra element need to be included in the API itself to differentiate each page / a different API for each web page, or should I "group" in the Marketo flow? I've tried source = web api and web page = x but that doesn't seem to work

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

A
Anonymous
June 23, 2015

Are you talking about our Munchkin Javascript code for web page visits? Or do you mean that you're using server side post to put external form data into Marketo so you can use the Fills Out Form trigger?

    A
    Anonymous
    June 23, 2015

    Hi Kristen, I think it is the SOAP API code we've got in our various web pages to sync the external form data over into marketo. Currently I have been trying to constrain by:

    source = web api + web address = x , but that doesn't seem to work - i'm not sure exactly where in the process I'm missing a trick - getting our techinical team to add in info in the code (e.g. lead source / request campaign) or something I can update within marketo itself?

    A
    Anonymous
    June 23, 2015

    Sounds like you are talking about server side post then. Typically you create separate blank forms for each page that your form is on and you modify the code slightly for each page so that you have a unique Marketo form ID that you're posting into. This will allow you to track which specific form and which specific page it was filled out on so you can set up programs and track success.

      A
      Anonymous
      June 23, 2015

      So in laymans terms (i'm trying to bridge the gap between our marketing and technical sides!) would that mean that we'd have each API named differently so it can be identified separately in trigger - source? Do you have any recommendations of how / what to create this form ID as? Is it as simple as adding in a particular name within the API code and having marketo listening out for that? or having a "call" into a particular campaign?  e.g. request campaign for x?

      Terms & ConditionsAccessibility statement

      Loading footer...