Marketo Integration Troubleshooting Services: Failures and Fixes

Marketo integration troubleshooting services find and fix the connections that break around Adobe Marketo Engage. The usual suspects are CRM sync errors, field mapping, sync user permissions, API limits, failing webhooks, LaunchPoint credentials and missing Munchkin or form data. A good engagement starts from Marketo's own sync and usage screens, finds the root cause, fixes it and leaves monitoring behind.

This post covers common failure modes, how a fix engagement runs, what to prepare and when to call Adobe Support.

What do Marketo integration troubleshooting services cover?

They cover any data flow into or out of Marketo Engage that has stopped, slowed down or started writing bad data. The work is diagnosis first, then repair, then prevention.

Most engagements touch one or more of these areas:

• CRM sync. The native Salesforce and Microsoft Dynamics connectors, including the sync user, field mapping and sync filters.
• APIs. Custom or vendor integrations using the Marketo REST Application Programming Interface (API), and the quotas that limit them.
• Webhooks. Calls from smart campaigns to outside services for enrichment, validation or alerts.
• LaunchPoint services. Webinar, ad network and custom API connections set up under Admin.
• Tracking and forms. Munchkin tracking code, embedded forms and how visits link to known people.
• Adobe connectors. Links to Adobe Experience Platform and other Adobe tools, covered in our guide to Marketo and Adobe integration.

You can buy this as a one-off fix, as part of a managed support retainer, or as an audit followed by a fix. The quick table below shows where troubleshooting usually starts.

Symptom	Where to look first	Common cause
Leads not reaching Salesforce	Sync Errors tab	Validation rule or missing required field
New CRM field missing in Marketo	Sync user's field access	Field hidden from the sync user
Sync running hours behind	Sync backlog metrics	Bulk updates, too many synced fields
Dynamics sync stopped	Validate Sync tool	Sync user role or credentials changed
Integration fails late in the day	API usage report	Daily quota reached
Bursts of failed API calls	Integration logs	Rate or concurrency limit
Webhook values never update	Webhook is Called activity	Non-2xx response or batch campaign
Known people with no web visits	Munchkin setup	Script missing or no association event

Why does the Marketo Salesforce sync fail?

Most Salesforce sync failures come from three places: what the sync user can see, Salesforce validation rules, and changes made to fields after setup. Marketo's own screens usually point straight at the cause.

Adobe's documentation explains the basics. Marketo syncs with Salesforce all day, pausing five minutes between cycles. The sync is two-way for leads, contacts and Salesforce campaigns, and one-way from Salesforce for everything else. Only data the sync user's credentials can access is included.

Here's what typically goes wrong:

• Validation rules. Adobe says Marketo respects Salesforce validation rules, and the sync fails if data is in the wrong format or a required field is missing. The failure is logged in the person's Activity Log.
• Field visibility. A new Salesforce field only appears in Marketo if the sync user has permission to see it.
• Field type changes. If a field type changes in Salesforce, Marketo deletes values that no longer match, after a warning. Export the data first.
• API name changes. Renaming a field's API name in Salesforce creates a new field in Marketo.
• Formula and lookup fields. Formula fields don't update in Marketo until the record's system timestamp changes. Lookup fields sync the ID, not the name.
• Picklists. Removing a picklist value in Salesforce means removing it by hand from every Marketo form that uses it.

One newer cause is worth checking first. Adobe notes that since September 2025, Salesforce has restricted the use of Connected Apps. Existing setups can add the "Approve Uninstalled Connected Apps" permission to the sync user's profile, or switch to a new External Client App.

For evidence, go to Admin, then Salesforce. The Sync Errors tab lists errors from the last five days and exports to CSV. The backlog metrics show records waiting to sync and flag the status as "Growing" when the backlog is bigger than six hours earlier.

Adobe's own advice for backlogs is practical. Hide fields the sync user doesn't need, schedule bulk updates for quiet hours, and review custom objects you no longer use. Marketo Engage Support can also help set up a custom sync filter.

What goes wrong with the Marketo Microsoft Dynamics sync?

Dynamics problems usually come from the sync user, the authentication setup or the sync filter. Adobe's Validate Sync tool is the first place to look, because it checks each link in the chain.

The tool checks that the Dynamics URL is valid, the credentials work, and the sync user has the Marketo Sync User role. It also checks that the Marketo solution is installed and its steps are enabled. Adobe's guidance is to fix each failed step and rerun the validation until every check passes.

Other common causes include:

• Server-to-server setup. For this authentication type, the username in Marketo must match the email of the Application User in Dynamics. The client secret is only shown once when it's created, so record it safely.
• Changing authentication. You must disable the global sync first. Adobe says the system takes 15 minutes to accept the new method, so wait before re-enabling.
• Sync filter surprises. The filter uses a Two Options field named new_synctomkto. Only an explicit "No" stops a record from syncing. Blank values still sync.
• Sandbox refreshes. Adobe says Marketo doesn't support a sandbox refresh for the Dynamics sync. Refreshing your Dynamics sandbox needs a new Marketo sandbox.
• Deleted fields. Adobe recommends deleting a synced field in Dynamics with the sync disabled, then refreshing the field list in Marketo.

Know who wins a data collision, too. For Dynamics, Adobe says Marketo wins for leads and Dynamics wins for contacts. Teams often assume the CRM always wins, then wonder why a lead's field keeps changing back.

How do API limits break Marketo integrations?

Integrations fail when they hit Marketo's API limits, and the failure is easy to miss. Adobe's developer documentation sets three limits, and a busy instance can hit any of them.

• Daily quota. Each subscription gets 50,000 API calls a day, resetting at midnight Central Standard Time. Adobe's packaging page lists 20,000 a day for the Growth package.
• Rate limit. Each instance is limited to 100 calls per 20 seconds.
• Concurrency. Each instance allows up to ten calls at once.

The matching error codes are 606 for the rate limit, 607 for the daily quota and 615 for concurrency. Here's the trap: Adobe notes that a failed call usually still returns HTTP status 200, with success set to false in the response. Monitoring that only watches HTTP status will report everything as fine.

The fix is usually a mix of changes. Give each integration its own API-only user, because Adobe's usage report tracks each API user separately. Then batch calls and use bulk endpoints for large imports and exports.

Add backoff and retry logic, and spread scheduled jobs across the day. If you still need more, Adobe says your account manager can raise the daily quota.

Check older integrations too. Adobe's REST documentation says the SOAP API was deprecated and is no longer available as of 31 July 2026. Any connector still built on it needs rebuilding on the REST API.

Why do Marketo webhooks and LaunchPoint services fail?

Webhooks fail because of where they run, how long the other service takes and what it sends back. LaunchPoint services fail when the credentials or the user behind them change.

Adobe's developer documentation sets out the webhook rules:

• Trigger campaigns only. A Call Webhook step in a batch campaign returns error 1000. An empty response body returns error 1001.
• 30-second timeout. Marketo waits up to 30 seconds for a reply, then ends the call.
• 2xx responses only. Response mappings update a record only when the service returns a 2xx status code.
• No automatic retry. Adobe's knowledge base says a failed triggered webhook isn't retried. You need a separate smart campaign using the "Webhook is Called" trigger to catch failures.

Speed matters more than people expect. Adobe gives an example: even at 50 milliseconds per call, 100,000 calls take about 1.5 hours. A slow webhook in a high-volume trigger can hold up the whole campaign.

LaunchPoint custom services are tied to an API-only user and issue a client ID and secret. Access tokens are valid for one hour.

Common failures include an API role missing a permission or a deactivated API user. A secret may have been rotated without updating the connected tool. Or IP restrictions may block a vendor's new servers.

Why is Munchkin or form data missing in Marketo?

Usually the tracking script isn't loading, or the visitor was never linked to a known person on that domain. Both are fixable, but they need someone comfortable with JavaScript.

Adobe's Munchkin documentation explains the identity rules. Munchkin creates an anonymous record keyed to a cookie called _mkto_trk. That record becomes known only after one of three events. The person clicks a tracked Marketo email, fills out a Marketo form, or is matched by a REST Associate Lead call.

Cookies are set per domain. A person known on one domain is still anonymous on another until an association happens there too. Known status does carry across subdomains of the same domain.

Other common causes:

• The asynchronous code isn't in the page <head>, where Adobe recommends placing it.
• More than one Munchkin script for different workspaces sits on the same page, which Adobe says not to do.
• The site's consent or tag setup blocks the script. Adobe tags users can load it through the Marketo Munchkin extension.

There's one support boundary to know. Adobe's own setup page says Marketo Technical Support isn't set up to troubleshoot custom JavaScript. Custom form behavior and tracking code fixes are partner or developer work.

How does a Marketo integration troubleshooting engagement run?

A sound engagement moves through the same stages each time, so the fix is proven and doesn't come back. Expect the provider to explain each stage before starting.

• Triage. Agree the symptom, business impact and priority.
• Evidence. Collect sync error exports, usage reports, logs and example records.
• Reproduce. Recreate the failure with a test record, in a sandbox if you have one.
• Root cause. Confirm the actual cause, not just the first plausible one.
• Fix. Make the change with a written change log and your approval.
• Verify. Watch error exports and backlog for at least a week.
• Prevent. Add monitoring, update the runbook and hand over notes.

Timing varies with the problem. As an indicative guide, a single repeating sync error often takes a few days to clear. A failing custom integration can take one to three weeks, depending on access to the other system and its developers.

Pricing is often a fixed fee for diagnosis, then time and materials for the fix. Ask for the diagnosis to end with a written root cause, even if you fix it yourself.

What should you prepare before calling for help?

Prepare evidence, access and a change history. A partner who gets these on day one can often find the cause in hours rather than days.

• Your Munchkin ID and the data center and pod shown under Admin, then My Account.
• A Sync Errors export and a Sync Status export from the last five days.
• A screenshot of the sync backlog metrics.
• The API usage report from Admin, then Web Services.
• A list of LaunchPoint services, webhooks and API users, with an owner for each.
• An Audit Trail export covering recent changes, plus a note of CRM changes from your CRM admin.
• Three example records with their Marketo and CRM IDs. Clicking a record-level sync error shows both.
• A named login for the troubleshooter, and sandbox access if you have one.

When should you call Adobe Support instead of a partner?

Call Adobe Support for outages, suspected product defects and anything Adobe's documentation says Support handles. Call a partner for configuration, CRM-side changes, custom code and your own integrations.

Adobe Support is the right first call when:

• Marketo is down or badly degraded. Subscribe to status notifications for your data center and pod at status.adobe.com.
• Behavior doesn't match the documentation, and you suspect a product bug.
• You need a custom Salesforce sync filter, which Adobe says Marketo Engage Support can help set up.
• A backlog keeps growing after you've followed Adobe's best practices. Adobe's guidance is then to contact Support.

A partner is the better call for field mapping design, Salesforce or Dynamics configuration, middleware, custom JavaScript and webhooks to your own services. In practice, the two often work together. The partner gathers evidence and a named support contact opens the Adobe case. Our comparison of a Marketo support partner vs Adobe Support covers that split in detail.

What to do next

Work through these steps before the next failure, so any Marketo integration troubleshooting starts from good evidence.

• Give every integration its own API-only user and role.
• Add a weekly check of Sync Errors and backlog to someone's calendar.
• Make sure API monitoring reads the success field, not just HTTP status.
• Build a "Webhook is Called" campaign to catch failed webhook calls.
• List every LaunchPoint service and webhook with its owner and credential date.
• Subscribe to Adobe status notifications for your pod.

If you need outside help, our guide to Adobe Marketo Engage support services explains what ongoing cover looks like. Our guide on how to hire a Marketo support partner walks through the selection steps. To find firms with integration experience, start with the Adobe Marketo Engage partner list or the Marketo Engage partner shortlist. Then brief them with the Marketo Engage RFP template, or answer a few questions in our partner advisor.