Looking to added contacts to Marketo from a 3rd party form | Community
Skip to main content
New Participant
February 14, 2022
Question

Looking to added contacts to Marketo from a 3rd party form

  • February 14, 2022
  • 1 reply
  • 2716 views

Having trouble finding documentation of the process of setting up an API that feeds into a list that is part of a campaign.

 

Goal is to import new registrants via API (or FTP if possible) who then receive a welcome email right away. The form collecting this data is not a Marketo form.

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

1 reply

Jo_Pitts1
Community Manager
February 14, 2022

@seanmun,

you are better off to use a hidden Marketo form, take the data from the third party form and submit into Marketo that way.  

 

Something along these lines:

MktoForms2.loadForm("//app-ab00.marketo.com", "785-UHP-775", 1057); // Find the button element that you want to attach the event to var btn = document.getElementById("MyAlternativeSubmitButtonId"); btn.onclick = function() { // When the button is clicked, get the form object and submit it MktoForms2.whenReady(function (form) { form.vals({ "FirstName": $('#first').val(), "LastName": $('#last').val(), "Email": $('#email').val(), "Phone": $('#phone').val() }); form.submit(); }); };

 

If you submit the records via API or FTP, you don't get all the awesome Known Visitor tracking being activated, or the ability to trigger journeys off a form fill activity.

 

Cheers

Jo

   

SanfordWhiteman
New Participant
February 15, 2022

I definitely support using the Forms 2.0 JS API in every possible case, like Jo says.

 

But you can get Munchkin-associated sessions when you use the Submit Form API. That part does work, if the cookie is part of the input.

 

The Submit Form API is a lot less scalable than the Forms 2.0 JS API. On a busy site the Submit Form API, if not otherwise policed, will overwhelm your API calls.

 

There’s no such thing as FTP uploads into Marketo. You certainly can write an app that periodically pulls lists from an FTP/SFTP server and then pushes them into Marketo using the API. But that kind of periodic pull-translate-push (basically a mini-ETL process) runs counter to the idea of form fills showing up promptly in the production database. Of course it is possible, but I would challenge such a design quite strongly given that the JS API is right there for you.