Before setting up the Marketo destination in RudderStack, you must create two fields in Marketo with the API names exactly as userId and anonymousId. RudderStack looks up the Marketo Lead objects using these properties. Without these two fields, all events will fail.
Before configuring Marketo as a destination in RudderStack, verify if the source platform is supported by Marketo by referring to the table below:
Assign a name to the destination and click Continue.
To successfully configure Marketo as a destination in RudderStack, you need to configure the following settings:
Munchkin Account ID: Enter your Munchkin account ID.
You can find the Munchkin Account ID by logging into your Marketo instance and going to Admin > Integration > Munchkin. Your Munchkin ID is listed on the main screen in the Tracking Code section. For more information, refer to the Marketo documentation.
Client ID: Enter your Marketo client ID.
Client Secret: Enter your Marketo client secret next.
You can find the client ID and client secret by logging into your Marketo instance and going to Admin > Integration > LaunchPoint. Select the API service and click View Details to get the credentials. For more information, refer to the FAQ section below.
Custom Activity Settings
Track anonymous events: Enable this setting to track events that don’t contain a userId.
If this setting is disabled, events that don’t contain the userId field will automatically fail.
Create lead if it does not exist: If enabled, RudderStack will create a new Marketo lead if the user is not present.
The following settings are associated with the track events and require you to first create a Custom Activity in Marketo before sending an event. You also need to approve the activity in order to get the Custom Activity ID.
Map events to Marketo Activity ID: Use this setting to map the event name in track call to Marketo’s custom activity ID. For example, you can map a Product Clicked event to a custom activity with the ID 100001 and name Product wishlisted.
Map your event properties to Marketo custom activity’s field: Use this setting to map your track event properties to the Marketo fields listed in your custom activity. For example, you can map Product Clicked event’s product_name property to the Marketo’s productName field in the Product wishlisted custom activity.
Map event name to Marketo primary key: Map the track event name to the Marketo primary key associated with the custom activity. For example, you can map the Product Clicked event to Marketo’s product_id primary field in the Product wishlisted custom activity. The primary field for Marketo’s custom activity is marked with an asterisk (*).
Map your traits to Marketo custom fields: RudderStack maps some of the user traits to the custom Marketo fields by default (listed in the Supported mappings section). You can use this setting to override the default mappings or map any other traits to the custom Marketo fields. For custom Marketo fields, you can use the list of standard Marketo fields (REST API Name column) or any other custom field names existing in your lead records.
You can use the identify call to create or update a Lead object in Marketo.
By default, RudderStack maps the following traits to the Marketo fields:
For the rest of the fields that you want to sync with Marketo, you can create a mapping of your traits and custom Marketo fields in the RudderStack dashboard, as specified in the Lead Mapping settings section.
You can use the track events to register custom activities in Marketo.
Why are my requests failing with the message “Lookup failed”?
Make sure you have created two fields in Marketo with the names userId and anonymousId, so that RudderStack can look up the Marketo lead database for leadId with the userId that are passed along with the event.
Why are my track events failing?
Make sure you have created two fields in Marketo with the API names exactly as userId and anonymousId. RudderStack looks up the Marketo lead objects using these properties. Without these two fields, all events will fail.
If you’re sending track events without userId, make sure you have enabled the Track Anonymous events setting in the RudderStack dashboard. If this setting is disabled, events that don’t contain the userId field will fail.
How do I obtain the Marketo client ID and secret?
To set up the Marketo API service and obtain the client ID and secret associated with it, follow these steps:
Log into your Marketo instance and click the Admin tab.
Here, you will able to see all installed services used for connecting to Marketo.
To create a new service, click New > New Service.
Enter the Display Name. From the Service dropdown, select Custom.
Under Settings, enter the Description and select the API Only User, as shown. Finally, click CREATE.
Make sure the API Only User associated with the API service has the necessary permissions to create or update contacts as wellas the custom activities.
Once the setup is complete, you should have the client ID and client secret for the API service. Use this to configure the Marketo destination in RudderStack.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.