Most guides to Marketo and Salesforce focus on setup: create the sync user, map the fields, choose which records sync, and turn it on. That work matters. But it skips a question that becomes urgent as soon as an org gets busy: how much of the Salesforce API allocation does the sync consume, and what else is competing for it?
The answer is more than many teams expect. According to Adobe's own documentation, Marketo's sync checks Salesforce for changes every five minutes by default, and each check uses 25 API calls. That alone is 7,200 calls a day, before a single lead or contact is updated. Activities, flow steps, and campaign membership changes add more on top.
In orgs where sales tools, ERP connectors, data enrichment services, and AI agents all call Salesforce through the same daily limit, that consumption matters. A Marketo Salesforce integration should start with an API budget, not end with an unexpected outage.
How the Daily Salesforce API Allocation Works
Salesforce caps the number of API requests an org can make in any rolling 24-hour period. The Salesforce API limits cheatsheet gives the formula for Enterprise Edition as 100,000 requests plus 1,000 per user license. An org with 50 licenses therefore has about 150,000 requests per day. Additional capacity can be purchased.
The limit is measured on a rolling basis, not by calendar day. When an org exceeds it, Salesforce blocks further API calls with a REQUEST_LIMIT_EXCEEDED error until usage over the preceding 24 hours drops back below the cap. Every integration that uses the API is blocked at the same time.
That is the risk. A spike in one integration can stop all of them. The Marketo sync stops, but so does the ERP order feed, the data warehouse extract, and any external agent or tool reading Salesforce through the API.
What the Marketo to Salesforce Integration Consumes
The Adobe Marketo sync documentation breaks consumption into several parts.
Change checks. Each sync cycle makes 25 API calls to check whether objects have changed. At the default five-minute interval, that is 7,200 calls a day. At a 30-minute interval, it falls to about 1,000 a day.
Record updates. Leads, contacts, accounts, opportunities, campaigns, and activities sync in batches of up to 200 records per call. Adobe's example of 1,000 lead updates, 1,000 contact updates, and 100 updates each to accounts, opportunities, and campaigns totals 7,213 calls, including the checks.
Flow steps. Each "Sync Lead to SFDC" or "Add to Campaign" step in a trigger campaign uses at least one API call per lead when the lead reaches it. Batch campaigns can send up to 200 leads in one call.
Activities. Each synced activity, such as a form fill, uses one additional API call per event.
Initial sync. The first sync, or a resync after a pause, uses significantly more calls until Marketo catches up.
For a mid-size org, normal daily usage might sit comfortably within the limit. The trouble comes from peaks: a large webinar with thousands of registrations processed by trigger campaigns, a list import that fires sync steps lead by lead, or a resync after a field mapping change.
Why Shared Limits Matter More Than They Used To
Marketo is rarely the only integration. The 2025 MuleSoft Connectivity Benchmark found that the average enterprise manages 897 applications, and that 94% of IT decision-makers plan to implement autonomous agents within two years. Many of those applications and agents read from or write to the CRM.
A typical org now shares its allocation among the Marketo sync, ERP and billing integrations, a data warehouse or lakehouse extract, sales engagement and enrichment tools, document generation and e-signature apps, and external AI tools or agent frameworks that query Salesforce through APIs or connectors.
Each of these was usually set up by a different team, at a different time, with its own vendor. Few orgs have a single view of how much of the daily allocation each one uses.
Build an API Budget Before You Integrate Marketo with Salesforce
An API budget is a simple plan that assigns daily capacity to each integration, with headroom for peaks. Building one takes a few steps:
- Measure current usage. Check "API Requests, Last 24 Hours" in Salesforce Setup, and use event monitoring or API usage reports to break usage down by connected app or integration user.
- Estimate Marketo's share. Start with 7,200 calls a day for checks at the default interval. Add expected daily updates divided by 200, plus one call per synced activity and per trigger campaign sync step.
- Set allowances. Assign each integration a daily allowance, leaving at least 20% of the total limit unallocated for peaks and new tools.
- Plan for peaks. Identify events that cause spikes, such as large imports, webinars, and trade shows, and decide in advance how they will be processed.
- Assign an owner. One person or team should own the budget and approve new integrations against it.
A dedicated integration user for each system makes measurement much easier. When every tool logs in as the same admin user, attributing usage becomes guesswork.
A Sample Budget for a 50-License Org
Take a representative Enterprise Edition org with 50 licenses and a daily limit of about 150,000 requests.
The ERP integration processes orders and invoices and uses about 40,000 calls a day. A data warehouse extract runs every hour and uses about 25,000. Sales engagement and enrichment tools use about 15,000 between them. A document generation app uses about 5,000. A new external AI assistant that reads account and opportunity data for sellers is expected to use about 20,000.
That leaves roughly 45,000 calls before reaching the limit. Marketo's checks take 7,200. Normal record updates and activity syncs might add another 8,000 to 10,000. On an average day, total usage lands around 120,000, or 80% of the limit.
Now add a trade show. Marketing imports 6,000 badge scans and runs them through a trigger campaign with a "Sync Lead to SFDC" step and an "Add to Campaign" step. That is at least 12,000 calls, possibly more with activities. On the same day, sellers lean heavily on the AI assistant to prepare follow-ups. Usage crosses the limit in the afternoon, and every integration stops, including the ERP order feed.
With a budget in place, the same team would have processed the import through a batch campaign, cutting those steps to about 60 calls, and scheduled it overnight. The trade show would have passed without anyone outside marketing noticing.
Design Choices That Reduce Consumption
Several settings and habits keep the Marketo to Salesforce integration efficient.
- Adjust the sync interval. If marketing does not need five-minute freshness, ask Marketo Support for a longer interval. Moving to 30 minutes cuts check calls from 7,200 to about 1,000 a day.
- Sync only the activities sales uses. Every synced activity costs a call. Review which activity types sales teams look at in Salesforce and turn off the rest.
- Prefer batch campaigns for bulk work. Batch campaigns send up to 200 leads per call. Trigger campaigns send at least one call per lead. For imports and event follow-ups, a scheduled batch is far more efficient.
- Limit which records sync. Use a custom sync filter so that only qualified or relevant records sync to Salesforce. Fewer records means fewer updates.
- Avoid unnecessary field updates. Fields that change often, such as scores recalculated on every activity, generate update traffic. Sync the fields sales needs, at the frequency they need them.
- Schedule heavy jobs. Run large imports and data cleanup outside peak business hours, when other integrations are less active.
Monitoring a Marketo Salesforce Integration in Production
An API budget only works if someone watches it. Set alerts at thresholds such as 70% and 90% of the daily limit. Review usage by integration weekly. When a spike occurs, identify the source quickly and pause the job that caused it.
Plan for the day the limit is reached anyway. Decide in advance which integrations are critical, such as order processing, and which can wait, such as marketing activity sync. Document how to pause lower-priority syncs and how to resume them cleanly, including what happens to queued Marketo updates. Run the plan once as a drill, in a sandbox or during a quiet period, so the team knows how long recovery takes and which reports to check afterward. A recovery plan that has never been tested tends to fail on the details, such as a sync user whose password expired or a paused campaign nobody remembers to restart.
When the Native Sync Needs Help
The native connector suits most organizations, but some situations call for additional tools. Orgs with very high lead volumes, complex custom objects, or several Marketo instances sometimes add middleware to queue and batch updates, or to route specific data through bulk APIs that handle large volumes more efficiently. Others reduce the data Marketo needs from Salesforce by keeping certain attributes in a shared data platform and syncing only the fields that drive campaigns and routing.
Each option adds cost and another component to maintain. Make the decision with usage data in hand, after the settings described above have been tuned.
Data Quality and Compliance in the Sync
The sync also carries consent and personal data. Marketing teams collect opt-in status, unsubscribe requests, and preference choices, and those must reach Salesforce accurately so sales does not contact people who have opted out. Under GDPR, CAN-SPAM, and CASL, inconsistent consent data between systems is a compliance risk.
Map consent fields explicitly, test that changes flow in both directions, and decide which system is the source of truth for each field. Restrict the sync user's permissions to the objects and fields it needs, and review them when mappings change.
What a Good Salesforce Integration with Marketo Looks Like
A well-run integration has a few visible traits. Each system has a dedicated integration user. Field mappings are documented, with an owner for each. Sync filters, intervals, and activity settings are chosen deliberately. Usage is measured against a budget, alerts are in place, and a recovery plan exists. New integrations are reviewed for API impact before they go live.
Teams that set out to integrate Marketo with Salesforce for the first time can build these traits in from the start. Teams with an existing integration can add them through an audit, usually without disrupting marketing operations.
A Marketo Salesforce integration can use a significant share of an organization's daily Salesforce API allocation. The sync checks alone account for about 7,200 calls a day at the default interval. When other business tools and AI agents rely on the same API capacity, teams need to plan their usage carefully. Setting an API budget, optimizing sync settings, and monitoring usage can help prevent disruptions across integrations. As more AI tools connect to Salesforce, managing API capacity will become increasingly important. Planning for it early can help teams avoid unexpected outages and keep data flowing between systems.
Top comments (0)