Skip to main content

How to Connect Marketo as a Data Source in Alta (Connectors)

Connect Marketo through the Connectors library so Alta syncs your leads, activities, and campaigns to power marketing analytics, metrics, and Luna.

Written by Katie Supporté

Marketo is a marketing-automation platform that manages leads, the activities they take, and the campaigns that drive them. Connecting it as a data source through the Connectors library syncs that data into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure lead generation, campaign performance, and engagement — and ask Luna questions in plain English. Marketo connects with credentials.

Who this is for: Marketing ops and analytics teams who want Marketo lead and campaign data measured across Alta.


Before you start

  • Create a Marketo REST API service (a LaunchPoint custom service) and have its credentials ready: client ID, client secret, and your Marketo endpoint/instance (the unique subdomain in your REST API URL).

  • Connect a source only once per workspace. If Marketo already shows Connected, edit the existing connection.

Connect Marketo

  1. Open Connectors from the sidebar.

  2. Find Marketo via the category tabs or the Search data sources box.

  3. Click the Marketo card to open the Create connector screen.

  4. Fill in the connection fields shown (such as client ID, client secret, and endpoint), then click Create.

  5. Alta runs a connect test. If it fails you'll see The connect test has failed with Marketo's error — fix the field and retry.

  6. The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

  1. Open the connection. Marketo brings in tables like leads, activities, and campaigns.

  2. Use the Synced toggle in the Marketo tables section to control what's pulled in.

  3. Turn off Show only synced tables to see everything available.

Key tables and fields synced

  • leads — people: id, email, leadStatus, leadSource, company, createdAt, updatedAt

  • activities — what leads do: leadId, activityTypeId (email sent/opened/clicked, form fill, etc.), activityDate, primaryAttributeValue

  • campaigns — programs: id, name, status, type

  • programs (when available) — higher-level grouping with channel and cost data

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

  • "How many new leads per source last month?" — counts leads by leadSource and createdAt.

  • "Which campaigns generate the most leads?" — joins activities / membership to campaigns.name.

  • "What's the lead status distribution?" — groups leads by leadStatus.

  • "How many email opens and clicks per campaign?" — filters activities by type and groups by campaign.

  • "What's our lead-to-MQL rate over time?" — tracks leadStatus transitions by month.

Example use cases

  • Demand-gen dashboard. New leads by source and campaign, trended over time.

  • Campaign performance. Opens, clicks, and lead volume per campaign to find your best programs.

  • Funnel handoff. Combine with CRM data to follow leads from Marketo into pipeline and revenue.

  • Train Alta on engaged segments. Lead attributes and engagement teach Alta which profiles respond.

Keep it in sync

  • Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.

  • Click Sync now to refresh immediately; it's disabled while a sync runs.

  • Use the overflow menu () to Disable, Enable, or Delete.

Tips and common pitfalls

  • Get the endpoint right. A wrong Marketo instance/endpoint is the most common reason the connect test fails.

  • Activities are high-volume. Sync the activity tables only if you need them, and consider focusing on the activity types you actually report on.

  • Watch API limits. Marketo enforces daily API quotas — very frequent syncs can hit them.

  • Deleting is permanent. Disable instead to pause.


Related

Did this answer your question?