LEADCONDUIT INTEGRATION
Marketo | Create Lead
The leading Engagement Platform that empowers #marketers to create lasting relationships and grow revenue.
SPECIFICATION
Fields & configuration
The exact fields LeadConduit uses, appends, and the configuration options available for this integration.
Push a Lead using the REST API.
Appended Fields
Marketo will append the following data to your lead.
| Appended Field | Description |
|---|---|
Outcome | The outcome of the transaction (default is success) |
Reason | If the outcome was a failure, this is the reason |
Id | The ID of the Marketo lead that was created |
Status | The status of the transaction from Marketo |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
Email Required fieldMarketo needs this data to function. | Email address |
First Name | First name |
Last Name | Last name |
Phone 1 | Telephone number |
Address 1 | Address 1 |
Address 2 | Address 2 |
City | City |
State | State |
Postal Code | Postal Code |
Country | Country |
Title | Job title |
Company Name | Company Name |
Company Number Employees | Number of employees of lead's company |
Website | Website |
Industry | Industry |
Dob | Date of birth |
Gender | Gender |
Linkedin Profile Url | Lead's LinkedIn profile URL |
Custom Input Variables
The following are configuration options (typically not collected with lead data).
| Variable | Description |
|---|---|
| Marketo Endpoint Url | Marketo Endpoint URL |
| Marketo Identity Url | Marketo Identity URL |
| Marketo Lookup Field | Name of Marketo field to de-dupe on (defaults to email) |
| Marketo Partition Name | Name of lead partition, if the instance has lead partitions |
| Marketo Custom | false |
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
Push/Update a Lead to using the REST API.
Appended Fields
Marketo will append the following data to your lead.
| Appended Field | Description |
|---|---|
Outcome | The outcome of the transaction (default is success) |
Reason | If the outcome was a failure, this is the reason |
Id | The ID of the Marketo lead that was updated |
Status | The status of the transaction from Marketo |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
Email Required fieldMarketo needs this data to function. | Email address |
First Name | First name |
Last Name | Last name |
Phone 1 | Telephone number |
Address 1 | Address 1 |
Address 2 | Address 2 |
City | City |
State | State |
Postal Code | Postal Code |
Country | Country |
Title | Job title |
Company Name | Company Name |
Company Number Employees | Number of employees of lead's company |
Website | Website |
Industry | Industry |
Dob | Date of birth |
Gender | Gender |
Linkedin Profile Url | Lead's LinkedIn profile URL |
Custom Input Variables
The following are configuration options (typically not collected with lead data).
| Variable | Description |
|---|---|
| Marketo Endpoint Url | Marketo Endpoint URL |
| Marketo Identity Url | Marketo Identity URL |
| Marketo Lookup Field | Name of Marketo field to de-dupe on (defaults to email) |
| Marketo Partition Name | Name of lead partition, if the instance has lead partitions |
| Marketo Custom | false |
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
GETTING STARTED
Add Marketo in three steps
Add the integration
Find Marketo in your LeadConduit flow and add it as a step, no IT or code required.
Map your fields
Match your lead data to Marketo's fields. Required fields are added to your flow automatically when missing.
Route & go live
Match your lead data to Marketo's fields. Required fields are added to your flow automatically when missing.
KEEP EXPLORING
More integrations
Start routing leads with Marketo
Connect Marketo to your lead flow in minutes, or tell us what else you need and we'll support it.