SOAP APIs on Multiple Pages - Best way to categorize?

[Anonymous]

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

[Anonymous]

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?

[Anonymous]

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?

[Anonymous]

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.

[Anonymous]

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?

[Anonymous]

Form IDs are created automatically when you create a form in Marketo. You can find them in the URL. It will be the 4-5 digits after the FO in the URL.

You might want to review the instructions on how server side post is set up, which I just posted here: Using Server Side Post for Forms  I think this will clear up a lot of your confusion. Once you have the blank forms in Marketo, you just act as if they were regular Marketo forms and set up your campaigns accordingly, just as you would if you were putting Marketo forms on Marketo landing pages. The only difference is that no one ever actually sees the Marketo form; it's filled out by the API after someone fills out the live form on your website.

[Anonymous]

Thanks Kristen - I had a look at the instructions - am I missing something between points 5 and 6? and how can i link that into the API and then into the relevant campaign? (apologies if i'm asking a really obvious question!)

[Anonymous]

The field information with the API names is just something you need to provide to the person who has set up the original non-Marketo form so that they can send the data from your external form into the right place in Marketo.

When you build the smart campaign in Marketo, it will be set up the same as any other smart campaign you would build for a regular Marketo form, e.g. Trigger - Fills Out Form (Form Name is...Server Side Post Form Name in Marketo)

Change Program Status to 01 Filled Out Form - Success (or your equivalent campaign)

If Acquisition Program is empty, Change Acquisition Program to (this program's name)

Does that answer the question?