Create Custom Forms and Sync to Marketo

Mutiny's agent can write the JavaScript needed to connect your custom form to Marketo's Forms API, so visitor data captured through your Mutiny asset is sent to Marketo without requiring the Marketo form embed on your page.

What you'll need before asking the agent

The agent needs four pieces of information from you to generate working code. You can find all of them in your Marketo instance.

Your Munchkin ID is a nine-character alphanumeric string (formatted as XXX-XXX-XXX) that identifies your Marketo account. Find it in Marketo under Admin > Munchkin.

Your Form ID is the numeric ID of the Marketo form you want to submit data into. You can find it in the URL when editing the form in Marketo's Form Editor, or in the form list under Marketing Activities.

Your Marketo base URL is the domain used to load Marketo's script library. It follows the pattern //[munchkin-id].mktoweb.com. Your Munchkin ID appears as the subdomain.

Your field API names are the internal names Marketo uses for each form field. These are not the same as the labels that appear on the form. Find them in Marketo under Admin > Field Management, or by inspecting the fields inside the Form Editor. Common examples include Email, FirstName, LastName, and Company.

Asking the agent to write the code

Once you have those four things, in the asset editor, prompt the agent to create a custom form on the page, and that you want to submit data from a custom form to Marketo. In your prompt, provide your Munchkin ID, Form ID, base URL, and the list of field API names you want to map.

The agent will generate a JavaScript snippet that loads the Marketo Forms 2.0 library invisibly, maps your form's input values to the correct Marketo fields, and submits them on form submission.

What happens after submission

When a visitor submits your form, their data is sent to the Marketo form you specified. Marketo processes the submission the same way it would for a natively embedded form, including triggering any smart campaigns, workflows, or lead scoring rules tied to that form. The Munchkin tracking cookie is also set when the script loads, so lead attribution carries over normally.