Marketo integration

What Management OS does with your Marketo data.

How it connects: a Marketo Custom Service (REST endpoint URL, client ID and client secret), read-only. Checked against the product on 5 November 2026.

1. What Management OS reads

  • Engagement activities: form fills, email opens and clicks, web visits, score changes, interesting moments and new leads. The first sync goes back 30 days; after that each daily read continues from where the last one stopped.
  • The leads behind that engagement: name, email, company, title, score, status and source.
  • The list of activity types in your instance, so it asks only for the types above.

2. What it writes

Nothing. Every request to your Marketo instance is a read, plus the sign-in request that gets a short-lived access token. It never creates or changes a lead, never sends email through Marketo and never changes a program.

3. The access it asks for, and why

Marketo grants API access through an API Only user and a Custom Service owned by it. Give that user's role the Access API permission and read access only; Management OS needs nothing more.

REST Endpoint URL

Your instance's API address, from Admin, then Integration, then Web Services. The identity address used to sign in is worked out from the same host.

Client ID and Client secret

The Custom Service's credentials. Management OS uses them to get an access token that lasts an hour; tokens are never stored.

4. How fresh the data is

  • Management OS reads Marketo once a day, early in the morning UTC. The first read goes back 30 days.
  • To pull right away, choose Sync now on the Marketo page in Settings. Results appear in a few minutes.
  • Each run is capped in pages and leads, and paced, so it stays well inside your instance's API limits.

5. Where it shows up in Management OS

  • A Monday brief of the hottest hand-raisers from the last 7 days, ranked by engagement (form fills weigh most), with their contact details, so sales follows up the same week. If there was no engagement that week, no brief is sent.
  • Engagement next to your accounts and contacts, in the brief and in Ask Anything.

6. Where your Marketo data lives

Your credential. The client ID and secret are sealed with application-layer encryption before they are stored, and are never shown back in your browser or written to logs. Access tokens are fetched for each run and never stored.

Hosting. Runs in the United States on Vercel and Supabase.

AI processing. The data a brief or an answer needs is sent to Anthropic or OpenAI, on API terms that prohibit training. Each keeps prompts up to 30 days for abuse monitoring, with narrow exceptions listed on Sub-processors. We do not use Customer Data, prompts, or AI Output to train, fine-tune, or improve any AI model, including our own.

If you leave. Revoke access at any time, and export or delete your data on request. Active data is deleted within 30 days of termination; encrypted backups roll off within 90 days. See the Privacy Policy and the Data Processing Addendum.

7. How to connect Marketo

Before you start.

  • A Marketo admin to create the API Only user and the Custom Service.
  1. In Marketo, an admin opens Admin, then Users & Roles, and creates an API Only user whose role has the Access API permission.
  2. Still in Admin, open Integration, then LaunchPoint, and create a new service of type Custom, owned by that API Only user. This gives you the Client ID and Client secret.
  3. Open Integration, then Web Services, and copy the REST Endpoint URL.
  4. Open Management OS, then Settings, then Integrations. Find Marketo and choose Connect.
  5. Enter the REST Endpoint URL, Client ID and Client secret, and connect. Management OS signs in to your instance and lists activity types to check them before saving anything.
  6. Choose Sync now to pull the last 30 days right away, or wait for the next daily read.

8. How to disconnect

In Management OS, open Settings, then Integrations, find Marketo and choose Disconnect.

Management OS deletes the stored endpoint, client ID and secret, and stops reading. The disconnect is recorded in your workspace's audit log.

Leads and activities already brought in stay in your workspace as history; they stop updating. Email privacy@mgmt-os.ai to have them deleted.

9. How to revoke access from Marketo

In Marketo, an admin deletes the Custom Service in Admin, then Integration, then LaunchPoint, or deactivates the API Only user. Marketo then refuses the credentials.

10. If something goes wrong

The Marketo page says the provider rejected the stored credentials.
Marketo refused the saved client ID or secret, usually because the Custom Service was deleted or the API Only user was deactivated. Disconnect, then connect again with fresh credentials.
Connecting fails with a sign-in error.
Marketo refused the client ID or secret, or the endpoint URL is not your instance's REST endpoint. Copy the URL from Admin, then Integration, then Web Services, and the ID and secret from the Custom Service's details in LaunchPoint.
No Monday hand-raiser brief arrived.
The brief is skipped when there was no engagement in the last 7 days. Check that the daily sync is running in Settings.

11. Contact

Help connecting: support@mgmt-os.ai
Privacy and data requests: privacy@mgmt-os.ai
Security reports: security@mgmt-os.ai

Every other guide is on the Help page, and every connection is listed on Integrations.