Marketo Salesforce Integration: How the Native Sync Works and How to Set It Up

Your options for a Marketo and Salesforce integration

Unlike most tool pairs, Marketo and Salesforce don’t need a marketplace connector: the sync is part of Marketo Engage. Your real choice is what to add on top of it. For Salesforce integrations in general, see our Salesforce integration guide.

Four questions to find your setup:

What the native sync does, object by object

Adobe’s documentation describes a sync that runs all day: it completes a cycle, waits 5 minutes and starts again. Regular cycles take seconds or minutes because they carry only changes. The first sync copies your entire Salesforce database and can take hours or days. Only data the sync user can see in Salesforce comes across.

When both systems change the same record in the same cycle, Adobe says Marketo wins for leads and Salesforce wins for contacts. Collisions are rare, but they explain the occasional value that “won’t stick”.

Requirements before you connect

According to Adobe’s Experience League documentation as of October 2026:

• Salesforce API access. Enterprise and Unlimited editions have it. Professional Edition doesn’t by default; you need to ask your Salesforce account executive for it. Adobe has separate setup guides for the two cases: Professional sets field access through page layouts instead of profiles.
• A dedicated sync user (for example marketo@yourcompany.com) on its own profile, so you can tell Marketo’s changes from people’s and control exactly what Marketo sees. Adobe’s guide creates it with the Salesforce user license.
• Profile permissions: API Enabled, Edit HTML Templates, Manage Public Documents, Manage Public Templates, Convert Leads, Edit Events, Edit Tasks, and read, create, edit and delete on accounts, contacts, leads, opportunities and, for campaign sync, campaigns. For campaign sync, tick Marketing User on the sync user.
• Authentication. If your Marketo subscription shows a Login with Salesforce button, it connects through OAuth; otherwise it uses the sync user’s username, password and security token. Salesforce began restricting the use of uninstalled connected apps in September 2025, and since the Spring ’26 release new connected apps can’t be created by default, so Adobe now documents creating an External Client App for the sync. Marketo Support enables OAuth on the Marketo side.
• One org, chosen on purpose. Adobe’s setup guide warns that once the sync starts with a set of credentials, you can’t switch the Salesforce credentials or subscription. Connect a Marketo sandbox only to a Salesforce sandbox, and production only to production.

How to set up the Marketo Salesforce sync, step by step

Plan one to three weeks end to end. The clicks take an hour; the decisions and cleanup take the rest.

1. Write down the handoffAgree with sales on the score or behavior that makes a person a marketing-qualified lead, who assigns the owner (Salesforce assignment rules or a queue) and what sales does next. Every later setting follows from this page.
2. Add the Marketo fields in SalesforceOn both leads and contacts, create Score (number), Acquisition Program (text) and Acquisition Date (date/time) with the field names from Adobe’s guide (mkto71_Lead_Score and so on). Make them read-only for people and editable for the sync user’s profile, and map the lead fields to contact fields so values survive lead conversion.
3. Create the sync user and profileClone Standard User into a “Marketo-Salesforce Sync” profile with the permissions above, then create the dedicated user on it. Adobe suggests Password Never Expires on the profile so the sync doesn’t stop on a password reset.
4. Trim what the sync user seesIn field-level security, clear read and edit access on custom fields marketing doesn’t need. If whole groups of records shouldn’t sync (partners, internal test leads, non-marketable records), ask Marketo Support about a custom sync filter, ideally before the first sync.
5. Clean Salesforce dataMerge duplicate leads and contacts, fill Company and Last Name, and list validation rules and required fields the sync user will hit. Marketo respects them: a record that fails a rule fails to sync.
6. Connect in a sandbox pair firstIn Marketo, go to Admin, CRM, Sync with Salesforce.com. Log in with the sync user (OAuth) or enter username, password and security token, tick Sandbox for a sandbox pair, and click Sync Fields. Review field mappings before you click Start Salesforce Sync: Adobe warns that this step is final.
7. Turn on what you need, nothing moreIn Admin, Salesforce, enable campaign sync if programs should map to Salesforce campaigns (match program and campaign statuses first). Enable custom objects in Salesforce Objects Sync only if marketing will segment on them.
8. Build the handoff campaignA Marketo smart campaign that, when a person crosses your threshold, runs Sync Person to SFDC with the owner set by assignment rules or a queue. Optionally add Create Task so the owner gets a follow-up.
9. Test real scenariosPush a new lead, change an owner in Salesforce, convert a lead, add a contact role to an opportunity, change a picklist value, delete a lead. Check each result on both sides and in the person’s Activity Log.
10. Go live and watch the dashboardsRepeat the setup in production. During the first weeks, check the Sync Errors, Sync Status and backlog views in Admin, Salesforce every day until the backlog stays flat.

Field sync: what the docs say happens to your fields

Field behavior is where most surprises come from. From Adobe’s field sync documentation:

To stop Marketo from overwriting a Salesforce-owned field, take edit access on that field away from the sync user’s profile. To protect a Marketo field from certain sources, use Block Field Updates under Admin, Field Management, Field Actions, and check which sources your instance offers. Blocking protects existing values: an empty field still accepts the first value it receives.

Lead lifecycle and the scoring handoff

The integration exists for one moment: the handoff from marketing to sales. A clean version looks like this:

1. Marketo scores a person from behavior and fit. The score syncs to the Score field on the Salesforce lead or contact.
2. When the person crosses your threshold, a smart campaign runs Sync Person to SFDC. The lead appears in Salesforce right away and gets an owner from your assignment rules or a queue you choose. Salesforce rejects leads without Company and Last Name, so set defaults or require both on forms.
3. The owner works the lead in Salesforce. Status changes sync back to Marketo, where you can pause nurture or change it.
4. When the rep converts the lead, Marketo sees one contact. Opportunity stage and amount flow into Marketo as long as the contact has a contact role on the opportunity.
5. Campaign sync and opportunity data feed reporting, so marketing can see which programs led to pipeline.

Watch for implied actions. Adobe documents that flow steps such as Add to SFDC Campaign, Change Owner, Create Task and Convert Person first push the person to Salesforce if they aren’t there yet. A campaign meant only to add people to a Salesforce campaign can quietly create thousands of leads. Also avoid Convert Person unless you’re sure: it creates a new contact, account and opportunity, and Adobe recommends converting in Salesforce to avoid duplicate accounts.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Marketo Sales Insight: marketing data inside Salesforce

The sync moves records. Marketo Sales Insight (MSI) shows reps why a lead matters. It’s a package you install in Salesforce from AppExchange (now AgentExchange), with an option to install in a sandbox first. It adds a Marketo panel to lead, contact, account and opportunity pages with Interesting Moments, web activity, email and score tabs, “Stars and Flames” priority indicators, and actions such as Add to Marketo Campaign and Send Marketo Email.

Adobe also offers Sales Insight Actions, a web application that works with Salesforce through the MSI package. It adds sales emails with tracking, sequences of emails and tasks, and calling. If you don’t use MSI, the sync’s Customize Activities Sync option can instead push selected Marketo activities (form fills, emails sent and so on) to Salesforce as Activity History. Adobe notes that turning it on pushes three months of history, which can take several days.

Salesforce API usage and the sync backlog

The sync runs on your Salesforce API allocation, which every other integration shares. Adobe’s knowledge base article on how Marketo uses the Salesforce API, as of October 2026, says:

• About 25 calls per sync session just to check for changes, or roughly 7,200 a day at the default 5 minute interval.
• Records move in batches of up to 200 per call. Trigger campaigns with Salesforce flow steps use at least one call per person; batch campaigns can send up to 200 people per call.
• Enterprise Edition orgs rarely hit the limit; orgs with more limited editions or few licenses can. Marketo Support can lengthen the sync interval (around 1,000 calls a day at 30 minutes). Check usage in Salesforce under Company Information, “API Requests, Last 24 Hours”.

Backlog is the other limit. Any Salesforce update that changes a record’s system timestamp queues it for sync, so a bulk update, a busy integration or a frequently changing field can pile up thousands of records. Marketo’s Admin, Salesforce page shows a backlog trend for the last five days, throughput per object and a Backlog Status that reads “Growing” when the backlog is bigger than six hours earlier. Adobe’s fixes: hide fields and records marketing doesn’t need, schedule bulk updates off-hours, disable custom objects and activity syncs nobody uses, and clear sync errors.

If you build your own integration on Marketo’s REST API, its limits apply too. According to Adobe’s developer documentation, a subscription gets 50,000 API calls a day, with at most 100 calls per 20 seconds and ten concurrent calls per instance.

Common problems and how to fix them

Merges are mostly automatic. Merging leads in Salesforce merges the people in Marketo; scores are summed, activity logs are combined, and a non-empty value from the losing record fills an empty field on the winner.

When to customize beyond the native sync

The native sync is built for one Marketo instance and one Salesforce org sharing people and campaigns. Look further when:

• Marketing data must land on opportunities or accounts, such as engagement scores on accounts for ABM. The sync only reads these objects, so a Salesforce Flow or an external service has to write them.
• Several Salesforce orgs or regions feed one Marketo instance, or you are mid-merger with two orgs.
• A third system is in the flow: product usage, billing, a data warehouse or a second CRM. Our guide to the Salesforce MuleSoft integration covers the iPaaS route.
• Compliance needs such as per-record audit trails or consent logic that the sync can’t express.

Custom work here is usually small and targeted: a Salesforce Flow, an iPaaS recipe or a service that reads Marketo’s REST API, applies your rules and writes to Salesforce with retries and logging. Our API integration cost guide breaks down where the hours go.

Comparing marketing platforms? See how the HubSpot Salesforce integration and the Mailchimp Salesforce integration handle the same handoff, and how website forms reach Salesforce. For projects that combine several systems, see the cost of data integration.

Go-live checklist

Tick what is true for your setup. It shows how ready you are to start the sync in production.

FAQ

Where Gilzor fits

The native sync is the right start for almost every Marketo and Salesforce pair. When you need more, such as account-level data from Marketo, several orgs or a third system in the flow, Gilzor’s engineers in Poland and Cyprus can map the data flow, build the integration and support it after launch. See Gilzor’s Salesforce integration services.