What we do
Tools
Industries
Department
How we workLet's talk →
Home/Marketo/Marketo Salesforce Integration
Marketo + Salesforce

Marketo Salesforce Integration: When the Native Sync Is On and Things Still Slip

A lead crosses your hot-score threshold on Tuesday morning. The score field in Salesforce updates once the sync gets to it, and no rep is told. Adobe's native connector does sync leads, contacts, accounts, opportunities and campaigns between the two, and Sales Insight shows Marketo activity on the Salesforce record. Here's where to see whether the sync is healthy, and the gaps it leaves that cause most complaints.

Where to look in Marketo

Is the sync keeping up? The Salesforce admin page shows the backlog per object for the last 24 hours, a five-day trend, and a status of Growing or Normal.

Admin Salesforce

Which records failed? Sync Errors lists each failure with Salesforce's own return message. It only covers the last five days.

Admin Salesforce Sync Errors

Which custom objects come across? Salesforce Objects Sync is where custom objects are added to the sync, with global sync paused while you do it.

Admin Salesforce Objects Sync

Why records arrive late, wrong or not at all

Each of these comes up in a sync that's technically working.

The backlog keeps growing

How you'll know: Backlog Status reads Growing, and the estimated time to clear it is measured in hours. New leads show up in Salesforce late.

Fix: Large imports and records that update constantly are the usual causes, along with fields nobody needs. Cut the fields the sync user can see, and spread big data loads out instead of running them all at once.

You limited fields with a permission set

How you'll know: Fields you meant to hide from Marketo still sync.

Fix: The Marketo sync user's access has to be narrowed on its profile. A permission set that leaves a field out doesn't take away access the profile already grants.

A field was renamed or changed type in Salesforce

How you'll know: Marketo still shows the old name or type, or stops writing to the field.

Fix: Marketo keeps the properties it captured on the first sync. The change has to be made on the Marketo side too, sometimes with Marketo support.

A custom object never appears in the list

How you'll know: Your product-interest or subscription object can't be picked in Salesforce Objects Sync.

Fix: Marketo only syncs custom objects linked to a lead, contact or account, one or two levels deep, and the sync user needs read access. Anything further out needs its data moved by a custom integration.

Marketing wants to update a custom object from Marketo

How you'll know: A smart campaign can read the object but there's no way to change it.

Fix: Synced Salesforce custom objects are read-only in Marketo. Writing back means a webhook or service calling the Salesforce API, built and tested outside the native sync.

A score changes and nothing happens

How you'll know: Hot leads sit in a report until someone thinks to open it.

Fix: The sync moves the value. It doesn't create a task, alert a rep or route by territory. That's a rule someone has to build, in Salesforce Flow or as a small integration.

A B2B software company whose hot leads waited a day

B2B software company · Marketo for nurture, Salesforce for pipeline, native sync on

Before

A lead crossing the hot-score threshold showed up correctly in Salesforce, and nothing told a rep.

Reps checked a report when they remembered, so a hot lead could wait a day or more for a call.

After

Crossing the threshold now creates a Salesforce task, assigned to the right rep by territory.

The task carries the nurture program context, so the rep sees what the lead has already read before calling.

The score change became the thing that gets a call made, not a field nobody watched.

If sales runs on something other than Salesforce

Marketo's native CRM syncs are for Salesforce and Microsoft Dynamics. With HubSpot, Pipedrive or a CRM you built yourself, there's no switch to flip, and the connection is built against Marketo's REST API and the CRM's own API, with your rules for which system owns each field.

n-frames builds both kinds of work: the pieces around a native Marketo and Salesforce sync, such as rep alerts, custom object write-back and failed-record digests, and full integrations where no native sync exists. Rules that belong inside Salesforce are often a record-triggered flow, and anything Flow can't reach goes through the Salesforce API.

Marketo and Salesforce sync questions

Does Marketo integrate with Salesforce natively?

Yes. Adobe builds and maintains the connector. It syncs leads, contacts, accounts, opportunities and campaign membership, and Sales Insight shows Marketo emails, visits and score changes on the Salesforce record.

Can Marketo connect to a CRM other than Salesforce?

Natively, only to Microsoft Dynamics as well. Any other CRM is connected through Marketo's REST API and the CRM's API, with a rule for which system wins when both edit the same field.

Do custom Salesforce objects or fields sync with Marketo?

Custom fields on synced objects do, as long as the Marketo sync user can see them. Custom objects can be added in Salesforce Objects Sync if they link to a lead, contact or account one or two levels deep. They arrive read-only, usable in smart lists and campaigns but not editable from Marketo.

Why is our Marketo Salesforce sync running so slowly?

Usually a backlog. Open the Salesforce page in Marketo's Admin area and look at the backlog per object and its status. Big imports, records updated over and over, and fields the sync doesn't need all add to the queue.

Who builds what the native Marketo sync leaves out?

n-frames does. Typical jobs are alerting the right rep when a score crosses a line, writing changes back to Salesforce custom objects, and reporting failed records before Marketo's five-day error list drops them.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.