What Field is used to tie Marketing Lead to Web Form ID?

[Joon_Park]

Hello Marketo Nation!

We are planning to create leads using the REST API. We have a custom built form (using our branding guidelines) and we will be creating the lead from the data from our form.

We want to distinguish our leads depending on which form that the user filled out. Is there a default Field in Leads that we can store a Marketo Web Form ID? Or is there another field that we can use in order to distinguish which form the lead came from?

Currently we are loading a blank Marketo Web Form and pushing the data via the Forms API, however we want to do the push server-side using the REST API.

Any help is appreciated, thank you!

[SanfordWhiteman]

We are planning to create leads using the REST API.

Why?

Are you aware of the Denial of Service vulnerability that comes with this decision?

Moving from Forms API to REST API is just a terrible, terrible idea.

[Joon_Park]

Well we needed to store a file (resumes) somewhere and store it with the lead. So what we did was we created a REST call that passes the file and stores it in our S3 bucket, and returns the URL.

So what we want to do is store the URL of the file in our S3 bucket in a field with our lead. What would you recommend?

[SanfordWhiteman]

Why would uploading a file and retrieving its URL have to do with submitting the form data via REST?  You could get the URL and add that (string) field to a Marketo Forms post. That's what a service like UploadCare is great at.

[Joon_Park]

Would there be a way to submit the form from the server instead of using JavaScript? We are doing the file upload server-side due to CORS.

[SanfordWhiteman · Accepted solution]

We are doing the file upload server-side due to CORS.

So do the upload, return the generated URL to the page, and submit the form.

Also, a good client-side library can do a cross-origin binary post. That's what UploadCare is doing.

Would there be a way to submit the form from the server instead of using JavaScript?

Yes, but you will have another DoS vulnerability on your hands (though in this case at least more generous -- you might need a 28K modem instead of a 14.4 to break your site).

[Joon_Park]

Thanks for your help, just talked to our dev team and we can enable CORS for the service we created.

UploadCare would be nice, but we didn't want another repo to use just for this functionality when we already have an AWS subscription.