Convertr Help Centre Help Center home page
Submit a request
Sign in
  1. Convertr Help Centre
  2. Integration

Integrating with Marketo (including Static Lists) Follow

Michael Konomanyi
  • September 29, 2021 11:15
  • Updated

Introduction

With Convertr, we have the ability to integrate data directly into your Marketo database. We can add the lead into the full lead database, and we can also add them to a program or a Marketo static list.

This allows to post data quickly and securely into your client's Marketo database complete with logging and Marketo responses to ensure a smooth workflow, and strong troubleshooting capability.

This document covers the full lead database integration, as well as adding leads to a Marketo static list. This integration also has the ability to write data to a custom activity, or custom object within Marketo.

More information on the Marketo APIs that we use for this can be found below. For all calls, we use the REST API.

  • Creating/Updating Leads in Marketo Database
  • Adding a Lead to a Static List
  • Creating a Custom Activity
  • Creating a Custom Object

Prerequisites

You will need access to your client's Marketo instance in order to submit data. You will need the below as standard to create a lead in Marketo:

1. The REST API fieldnames of the data you wish to send to Marketo

2. clientID

3. clientSecret

4. identityUrl

5. These credentials must have the correct permissions associated with them on the API. To submit lead data to Marketo, we require the Read/Write Lead Permissions.

 

There are additional requirements if you also wish to submit to a static list, custom object or custom activity:

Static List

1. List ID

 

Custom Object

1. Object Name

2. Read/Write Custom Object permission

3. Deduplication field (Field to deduplicate on. If the value in the field for a given lead is not unique, an error will be returned for the lead)

 

Custom Activity

1. Activity Type ID

2. Attribute Names (Field Names). Note that it will not be the API name that we need here.

3. Read/Write Activity permission

 

 

Setup Process - Create Lead in Marketo

1. Within your campaign, go to the Processr tab, navigate to the Integration tab and click Add Job.

save image

 

2. In the drop down, select Integrate with Marketo and click Save.

save image

 

3. Select your credential source. You have the ability to store Marketo credentials using the Credential Manager. If you have done this, you can select Credential Manager and choose the credentials you wish to use. If not, select Manual.

If Manual is chosen, you will be asked to fill in the Client ID, Client Secret and Identity URL.

 

blobid0.png

 

4. In the config section, there is a single parameter excludeFieldsIfEmpty. This affects how we update data that already exists in Marketo.

If set to no, then Convertr will be able to essentially erase existing data in Marketo, if the field is being sent with no data. For example if a lead already exists in Marketo already with the telephone field populated, then if we resend that lead with the telephone field empty we will erase the existing telephone number in Marketo.

If set to yes, then we will not do this, and fields that are being submitted with no data will not be included in our Marketo API requests.

 

blobid2.png

 

5. Enter the REST field names provided by the Client and map to the Convertr field names from your lead data, then hit Save when you are happy.

Please note: The clients field names should be entered on the left and the matching Convertr field names are entered on the right.

save image

 

With this, we will be able to submit lead data to the Marketo database. Please be sure to test this and ensure your data goes through!

 

Static List

If you wish to add your leads to a static list after integration, you'll need to populate the sendToList section:

blobid1.png

 

  • leadListId: your list ID should be populated here. For example, if your list ID for this integration is 1234, you should insert that number in the empty field. Doing this will mean every lead that runs through this integration will be sent to this list.
  • leadListParamName: this should only be populated if you are collecting the List ID within your lead data. This will allow you to map the Convertr field you are collecting a list ID on to the integration, meaning that you can submit to multiple lists based on the value collected on your lead.

 

 

 

 

Articles in this section

  • Scheduled Delivery
  • Integration Requirements
  • Multiple Campaign Integration
  • List of Convertr Supported Integrations and Their Versions
  • Additional Integration Fields
  • HTTP Integration Example: Salesforce Web-to-Lead
  • The Credentials Manager
  • Hosting a Convertr Form On Your Own Page
  • HTTP Integration Example: Eloqua Forms
  • HTTP Integration Example: Marketo Forms
See more

Related articles

  • Integrating to Marketo Program
  • Integrating to Marketo Program for Smart Campaign
  • Integrating with Hubspot
  • Integration Requirements
  • Introduction to Bulk Editing
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top

Related articles

  • Integrating to Marketo Program
  • Integrating to Marketo Program for Smart Campaign
  • Integrating with Hubspot
  • Integration Requirements
  • Introduction to Bulk Editing