Marketing integration guide
Marketo + UbiGrowth workflows
Marketo is Adobe's enterprise marketing automation platform, used for programme-level campaign operations and lead lifecycle management. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Marketo part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a marketing workflow around Marketo with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Lead, Program, Campaign, Smart List, Activity, and Opportunity. Marketo keys on email address and its Salesforce sync claims ownership of the lead record, so writes from a third system can be overwritten on the next sync cycle without any error surfacing.
Marketo is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Marketing integrations usually fail at the join, not at the connection. Marketo can report on what it did, but connecting that to what happened downstream requires a shared definition of a lead, an opportunity, and a sourced deal that most organizations have never actually written down.
Without those definitions, every reporting cycle turns into a negotiation. Marketing counts one number, sales counts another, and the meeting is spent reconciling definitions instead of deciding what to do next.
You're likely here because
- Campaign reporting is reconciled by hand every cycle
- Marketing and sales count leads and opportunities differently
- Conversion context is lost before anyone follows up
Record model
What a Marketo integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Marketo's.
Identity and matching
Marketo keys on email address and its Salesforce sync claims ownership of the lead record, so writes from a third system can be overwritten on the next sync cycle without any error surfacing.
Start here
Read Program membership and its Activity history, and report which programs produced opportunities rather than which produced MQLs.
What this will not do
It will not simplify the program taxonomy. If nobody can say what a program means, connected reporting produces the same disagreement faster.
The constraint to plan around
Marketo enforces a daily API call quota per subscription that is shared by every integration, and exceeding it stops the CRM sync too. Budget calls against the whole estate, not against your workflow.
Build notes
What you actually have to reason about in Marketo.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| email address | the deduplication key by default, which makes shared and role addresses collapse records |
| leadScore | the qualification signal, computed by rules that live in Marketo rather than in your logic |
| program membership / status | the unit of campaign attribution, and what reporting should join on |
| SFDC id | the sync link; records not yet synced have none and are invisible from the CRM side |
| updatedAt | the bulk-extract cursor, since row-by-row polling is not viable at Marketo's limits |
Authentication
OAuth against a Marketo REST identity endpoint with a per-instance munchkin id, using a role-scoped API user. Creating that user with the right role is the step teams skip, and over-granting it is the usual shortcut.
Events and delivery
No general webhook feed for record changes — Marketo's webhooks are outbound calls from a campaign step, which is a different thing. Bulk extract jobs are the supported path for volume, and they are asynchronous.
Workflow
How the Marketo workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Agree the definitions
Lead, qualified lead, and sourced opportunity are defined and agreed with sales before any reporting is built on them.
Step 02
Read campaign and engagement state
Connected Marketo data provides what ran, to whom, and what they did, as an input rather than as a standalone report.
Step 03
Join to downstream outcomes
Campaign activity is joined to CRM outcomes using the agreed definitions, so the answer survives contact with the sales team.
Step 04
Carry context into follow-up
Conversions reach follow-up with the campaign, page, and stated interest attached, so the first reply is specific.
Design decisions
The marketing decisions this connection forces.
Each of these has to be settled before the Marketo workflow is allowed to write anything.
Step 01
Agree the measurement definitions
Write down what counts as a lead, a qualified lead, and a sourced opportunity before connecting Marketo. Most attribution disputes are definitional rather than technical.
Step 02
Carry campaign context into follow-up
The campaign, page, and stated interest should travel with the conversion into the follow-up workflow, so the first reply is specific rather than generic.
Implementation path
How to implement the Marketo workflow.
- 01
Decide which measurement Marketo is authoritative for and which questions must be answered from the CRM instead.
- 02
Write down the lead, MQL, and opportunity definitions and get sales to agree to them before you build reporting.
- 03
Instrument one campaign end to end rather than connecting everything and hoping the picture assembles itself.
- 04
Once program-to-opportunity reporting works, add program hygiene: programs with cost and no attributable pipeline, which is the conversation that changes budget.
Governance
Controls that matter.
Control 01
Consent, preference, and suppression state is respected as a first-class input, not a downstream filter.
Control 02
Public and brand-facing copy stays under human review before publication or send.
Control 03
Reporting definitions are documented and versioned so a change in the numbers can be explained.
Failure modes
How a Marketo integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Values written by the integration disappear within minutes.
Cause
The Salesforce connector owns the field and reverts external writes on its next sync.
Fix
Check connector field ownership before writing, and write to unowned fields or through the CRM instead.
Symptom 02
The CRM sync stops for everyone.
Cause
The integration consumed the subscription's shared daily API quota.
Fix
Use Bulk Extract for volume, and monitor quota against the whole estate rather than your own usage.
Symptom 03
Records are merged unexpectedly.
Cause
Marketo deduplicates on email address by default, so role addresses collapse distinct people.
Fix
Understand the org's dedupe configuration before importing anything with shared addresses.
What changes at scale
The daily API call quota is per subscription and shared. Bulk Extract jobs are asynchronous and count differently, which is why they are the supported path above modest volume.
Examples
What a working Marketo workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Enterprise campaign operations
With Marketo connected, campaign and engagement data can be analyzed alongside pipeline context rather than in isolation, which is what makes the answer actionable rather than descriptive.
Campaign-to-pipeline reporting
A Launch-built dashboard joins Marketo activity with CRM outcomes using agreed definitions, replacing the monthly manual reconciliation.
Limitations and considerations
What to validate before you depend on this.
- Marketo enforces a daily API call quota per subscription that is shared by every integration, and exceeding it stops the CRM sync too. Budget calls against the whole estate, not against your workflow.
- The Salesforce sync claims ownership of mapped fields. An external write to one is silently reverted on the next sync cycle, so the integration appears to work and the data does not persist.
- When the daily API quota is already consumed by the CRM sync. Marketo's quota is per subscription and shared, so adding an integration can break the sync everyone depends on.
- Attribution stays a model. Connected data makes it consistent and explainable; it does not make it a single objective truth.
- Platform reporting inside Marketo and workflow reporting will not always match exactly, because they measure different things at different times. Decide which answers which question.
FAQ
Marketo integration questions.
What records does a Marketo integration actually work with?
The primary records are Lead, Program, Campaign, Smart List, Activity, and Opportunity. Marketo keys on email address and its Salesforce sync claims ownership of the lead record, so writes from a third system can be overwritten on the next sync cycle without any error surfacing.
What should the first Marketo workflow be?
Read Program membership and its Activity history, and report which programs produced opportunities rather than which produced MQLs.
What will a Marketo integration not do?
It will not simplify the program taxonomy. If nobody can say what a program means, connected reporting produces the same disagreement faster.
What is the main constraint to plan around?
Marketo enforces a daily API call quota per subscription that is shared by every integration, and exceeding it stops the CRM sync too. Budget calls against the whole estate, not against your workflow.
What changes about a Marketo integration at scale?
The daily API call quota is per subscription and shared. Bulk Extract jobs are asynchronous and count differently, which is why they are the supported path above modest volume.
How does authentication work for Marketo?
OAuth against a Marketo REST identity endpoint with a per-instance munchkin id, using a role-scoped API user. Creating that user with the right role is the step teams skip, and over-granting it is the usual shortcut.
Does Marketo support webhooks, and can they be trusted?
No general webhook feed for record changes — Marketo's webhooks are outbound calls from a campaign step, which is a different thing. Bulk extract jobs are the supported path for volume, and they are asynchronous.
What is the risk of writing to Marketo?
The Salesforce sync claims ownership of mapped fields. An external write to one is silently reverted on the next sync cycle, so the integration appears to work and the data does not persist.
When is connecting Marketo the wrong call?
When the daily API quota is already consumed by the CRM sync. Marketo's quota is per subscription and shared, so adding an integration can break the sync everyone depends on.
What should a Marketo integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Marketo to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can Marketo data be joined to pipeline outcomes?
Yes, provided the lead and opportunity definitions are agreed first. The join is straightforward; the definitions are where these projects usually stall.
Why do the numbers differ from the platform dashboard?
Platform reporting and workflow reporting measure different events over different windows. Decide which system answers which question rather than trying to force them to agree.
Does campaign context survive into follow-up?
It should. The campaign, page, and stated interest travel with the conversion so the first reply is specific rather than a generic acknowledgement.
How this access is governed
What ARIA is allowed to do in Marketo, and who decides.
Connecting Marketo is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.