This page explains what happens behind the scenes when a change in Conversion is pushed to Salesforce. For controls over what syncs (objects, fields, sync modes), see Object Sync Preferences and Field Sync Preferences.Documentation Index
Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
Use this file to discover all available pages before exploring further.
What Gets Synced to Salesforce
When you change a record in Conversion (through the UI, a form submission, an import, an API call, or a workflow), Conversion can push that change to Salesforce as one of the following objects:| Conversion change | Salesforce object |
|---|---|
| Contact created or updated | Lead or Contact |
| Company created or updated | Account |
| Contact added to, removed from, or updated in a campaign | CampaignMember |
| Campaign created | Campaign |
| Workflow Salesforce node | Task, CampaignMember, or Lead queue assignment |
Outbound syncing only happens when Write to Salesforce is enabled for that object type. If outbound is disabled, changes still happen in Conversion — they just aren’t pushed to Salesforce.
Batching and Latency
Conversion does not push every individual change to Salesforce immediately. Instead, changes are batched and processed on a fixed schedule. This keeps your Salesforce API usage predictable and avoids hammering your API limits. What this means for you:- On average, a change made in Conversion appears in Salesforce within about 10 seconds.
- During periods of high activity (large imports, bulk workflow runs), changes are still grouped into bulk requests, so Salesforce sees fewer, larger updates rather than a flood of small ones.
Latency can be longer if you’re near your Salesforce API limit (see API Rate Limits below) or if a large backlog has built up. The queue always drains in the order changes were made.
When Both Systems Change at Once
It’s common for the same record to be edited in both systems around the same time — for example, a sales rep updates a contact in Salesforce while a form submission is processing in Conversion. Conversion is designed not to overwrite a fresher Salesforce value with a stale Conversion one. Right before sending an update, Conversion checks Salesforce for the current version of the record and decides what to send based on each field’s sync mode:| Field sync mode | What Conversion sends |
|---|---|
| Two-Way Sync | Sent only if Conversion’s value is newer than Salesforce’s. Otherwise dropped. |
| Prefer Salesforce Unless Empty | Sent only if the Salesforce field is currently blank. |
| Always Prefer Conversion | Always sent, regardless of what Salesforce currently has. |
| Always Prefer Salesforce | Never sent. |
| Do Not Sync | Never sent. |
API Rate Limits
Salesforce enforces a daily API request limit on every org. Conversion respects this limit and adds an optional second layer of protection so you can reserve API capacity for other tools.How limits are enforced
Before each batch is sent, Conversion checks current Salesforce API usage. If usage is at or above any configured limit:- The batch is not sent.
- The items stay in the queue — nothing is dropped or lost.
- The next time the queue is checked (about every 10 seconds), Conversion checks usage again. As soon as you’re back under the limit, the queue starts draining automatically.
Inbound sync (Salesforce → Conversion) is also subject to the same limits — when you’re over the threshold, Conversion stops pulling new data from Salesforce until usage drops.
Configuring your own limit
In addition to your overall Salesforce daily limit, you can set a Conversion daily limit to cap how many of those API calls Conversion is allowed to use. This is useful when other tools (data warehouse syncs, integrations, custom scripts) share the same Salesforce API budget. To configure it, go to Settings → Syncing → Overview, find the Conversion daily limit card, and click Add limit (or edit an existing one).Monitoring the Queue
You can see the current state of outbound syncing on Settings → Syncing → Overview:| Metric | What it shows |
|---|---|
| Conversion daily limit | Your current Salesforce API usage for the day, as a fraction of your configured Conversion limit (if set). |
| Salesforce daily limit | Your org’s total daily Salesforce API limit. |
| Queued batch items | The number of items currently waiting to be pushed to Salesforce. In normal operation this should hover near zero. |
- A large import or bulk workflow run is in progress and the queue is steadily draining.
- You’re at or above an API limit and the queue is paused.
- An upstream issue (e.g. an expired Salesforce connection) is preventing batches from completing — check Settings → Syncing → Sync Logs for failed batches.
Frequently Asked Questions
How long until my changes appear in Salesforce?
How long until my changes appear in Salesforce?
On average, about 10 seconds. Changes are batched and each outbound queue is checked roughly every 10 seconds. If you’re near an API limit or have a large backlog, it can take longer, but changes are processed in order and never dropped.
What happens if I hit my Salesforce API limit?
What happens if I hit my Salesforce API limit?
Outbound syncs pause. Pending changes stay in the queue and resume automatically once usage drops back under the limit. You won’t lose any data.
Will Conversion overwrite changes a sales rep just made in Salesforce?
Will Conversion overwrite changes a sales rep just made in Salesforce?
For fields in Two-Way Sync mode, no — Conversion only sends fields whose Conversion-side timestamp is newer than Salesforce’s
LastModifiedDate. For fields set to Always Prefer Conversion, Conversion will overwrite Salesforce’s value by design. See Field Sync Preferences for the full conflict-resolution rules.Can I see exactly what Conversion sent to Salesforce?
Can I see exactly what Conversion sent to Salesforce?
Yes. Settings → Syncing → Sync Logs lists every outbound (and inbound) sync batch, including which records were updated, which were skipped (and why), and which failed. Use this view to investigate if a change you expected isn’t showing up in Salesforce.
Why is the 'Queued batch items' count high?
Why is the 'Queued batch items' count high?
Some growth is normal during bulk operations (large imports, broad workflow triggers) — the queue will drain on its own. Sustained growth usually indicates an API limit being hit or a connection problem. Check the API usage metrics on the same page and review Sync Logs for failed batches.
Related Documentation
Object Sync Preferences
Control which objects sync and how new contacts are created in Salesforce.
Field Sync Preferences
Configure conflict resolution per field with five sync modes.