GatedContent.com forms can send submissions to Marketo forms via the Marketo Forms API 2.0 to capture user data within your Marketo instance. In addition, GatedContent.com can utilise the Marketo REST API to retrieve contact information for form pre-population. 


Integration requirements


Form submission capture

A Marketo form must be created to capture the data from GatedContent.com form submissions. Normally only a single Marketo form will be required that should contain all possible fields from all GatedContent.com form types, including hidden fields. If you intend to use multiple Marketo forms to capture data, you will need to use the Submission URL Override feature on the form type editor within GatedContent.com to control which form type submits to which Marketo form. Note that GatedContent.com can only submit to one Marketo form at a time. You can use reposts within Marketo to re-submit to other Marketo forms if necessary.


Please ensure that validation is disabled on all fields on the Marketo form. Validation rules can cause form submissions to fail for users. 

In addition, ensure that all your GatedContent.com field names match the HTML name (SOAP API name) of the receiving fields on your Eloqua forms.


Once you have created your form, supply the following details to your account manager so it can be added to your GatedContent.com account:

  • Marketo account ID 
  • Form submission URL


Overriding the Marketo form ID for some gates

Because form submissions to Marketo utilise the Marketo JS Forms API, you can't submit to a different Marketo form on a gate-by-gate basis using the "Override submission URL" option in the form type editor (although this option can still be used to divert submissions to a different, non-Marketo platform). Instead, you need to create a new hidden field called "marketoFormIDOverride". If this field exists on a gate and contains a value, it is assumed to be a Marketo form ID and the submission will be sent to this form instead of the account default. You can then use rules or pre-population settings to set a value in this hidden field where needed.



Pre-population data

Note that within Marketo, the REST API field names are used for pre-population.

You should create an API account specifically for GatedContent.com, following the official Marketo instructions (http://developers.marketo.com/rest-api/) with read access to the following endpoints:

  • API - Lead (Read Only)

In order to activate the integration, GatedContent.com requires the following information:

  • The Munchkin ID for the Marketo account to be integrated with, normally an 11 character string
  • The Marketo form ID(s) for the form(s) that will be used to capture submissions
  • The app URL for your Marketo instance
  • For the API account please provide:
  • Client ID
  • Client secret
  • REST endpoint URL
  • REST identity URL


Once fully integrated, you will be able to select Marketo fields to pre-populate GatedContent.com fields with from the field editor.


Email token pre-population

Because pre-population based on Marketo email tokens only works on Marketo landing pages, in order to use email-based pre-population, you will first need to create a landing page within your Marketo instance that contains a Marketo form with all fields that you want to pre-populate from. This page must be on the same primary domain as the one you will be using GCDC gates on.


Ensure that this page also contains your GCDC installation script and this custom script:


https://app.gatedcontent.com/assets/js/marketo_lp.min.js


Once created, provide the URL of the landing page to your GCDC account manager who will add this to your account configuration.


Please note that for pre-population to work, you must include the Pardot tracking script on any webpage where GatedContent.com gates are located.