Marketo Source

You will need Admin permissions to your Marketo account.

1. From your workspace's sources page, click add source.

2. Choose Marketo.

3. Give the source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. Both can be whatever you like, but Segment recommends that you stick to something that reflects the source itself, like Marketo for nickname and marketo or marketo_prod for the schema name.

4. Configure your Marketo source with the required settings (see section below for details)

   Expand image

1. Open Marketo.

2. Go to Admin > Munchkin to find your Munchkin Account ID.

   Expand image

3. Go to Admin > LaunchPoint

   1. If you don't already have a REST service setup, follow these steps.

   2. Then, copy the "Client ID" and "Client Secret" parameters.

      Expand image

   3. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings.

Data should start flowing into your warehouse in the next few hours.

The Marketo source is built with a sync component, which means Segment makes requests to Marketo's API on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, Segment grabs all the Marketo objects (and their corresponding properties) according to the Collections Table below. The objects will be written into a separate schema, corresponding to the source instance's schema name you designated upon creation (for example, my_source.charges).

The sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in Marketo. For example, if first_name goes from Jess to Jessica between syncs, on its next sync that field will be Jessica.

The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every three hours. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.

Collections are the groupings of resources Segment pulls from your source. In your warehouse, each collection gets its own table.

Currently, Warehouses are the only supported destination for object-cloud sources.

Segment doesn't provide statistics for these consumed API calls, since Segment systems only log the number of objects pulled from Marketo as throughput.

Yes. You can specific a daily limit to the API calls the source will consume. If you don't set a limit, Segment will, by default, consume as many API calls as are available in the limit you agreed to with Marketo to sync the entire source.

Segment also uses the Lead and Activity Bulk Extract APIs to reduce the number of requests needed to sync the data. For these syncs, Segment has a limit of 500 MB worth of files downloaded per day.

If your source needs more than 10,000 REST API calls or more than 500 MB of data to sync, Segment will continue the sync when a new batch of API calls is available.

Marketo's API quota applies across your subscription. If other applications share the quota, it could interfere with Segment's ability to sync the source.

You first need to enable the Activity Type IDs (optional) setting in the Marketo source, which must be enabled for Segment to pull the lead_activities collection source. Once Segment pulls the data, it will be available in your data warehouses.

Contact Support to get additional collections added to your source.

Yes. For leads and activities, choose Custom Lead Fields (optional), which lets you enter comma-separated custom files that will be synced by Marketo's REST API name.

View Marketo's List of Standard Fields documentation for a complete list of standard fields and Marketo's REST API names. Reach out to Segment support if you're interested in other fields.