Convertr Help Centre Help Center home page
Submit a request
Sign in
  1. Convertr Help Centre
  2. Product
  3. Leads - Delivery - Direct Integrations

Integrating with Marketo (including Static Lists) Follow

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 from Marketo 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.

6. For a Static List - List ID is required

More information on how to find these details can be found in our document Introduction To Marketo, Prerequisites And Where To Find The Key Integration Details.

 

Video Walkthrough

 

Setup Process - Create Lead in Marketo

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

Screenshot 2024-07-02 at 9.03.54 AM.png

 

2. In the drop down, select Integrate with Marketo Processr job

Screenshot 2024-07-02 at 9.06.00 AM.png

 

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.

Screenshot 2024-07-02 at 9.10.19 AM.png

4. We use the email field to check for duplicate leads within Marketo, and update the existing record if one is found, rather than creating a duplicate entry. In the config section, there is a single parameter ExcludeFieldsIfEmpty. This determines how we update the existing lead record. 

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 exists in Marketo with the telephone field already populated, and 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.

Screenshot 2024-07-02 at 9.11.18 AM.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.

Screenshot 2024-07-02 at 9.13.37 AM.png

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:

Screenshot 2024-07-02 at 9.14.38 AM.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 and do an optional Search. The LeadListId can be searched based on the API details entered. Doing this will mean every lead that runs through the 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

  • Convertr Connect: Integration
  • Eloqua Custom Objects and Fields
  • Eloqua Integration
  • Integrating to Eloqua Custom Fields
  • Integrating to Marketo - Troubleshooting and FAQ
  • Integrating to Marketo Program
  • Integrating with Hubspot
  • Integrating with Marketo (including Static Lists)
  • Integrating With Marketo - Custom Data Objects and Activities
  • Introduction To Eloqua And How To Create Your Custom Application In Eloqua
See more

Related articles

  • Integrating to Marketo Program
  • HTTP Integration Example: Marketo Forms
  • Introduction to Marketo, Prerequisites and Where to Find The Key Integration Details
  • Integrating With Marketo - Custom Data Objects and Activities
  • Campaign Templates
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
  • HTTP Integration Example: Marketo Forms
  • Introduction to Marketo, Prerequisites and Where to Find The Key Integration Details
  • Integrating With Marketo - Custom Data Objects and Activities
  • Campaign Templates
Convertr