Two questions come up repeatedly once a Salesforce integration is live, usually from operations teams rather than reps: what happens when several Salesforce accounts share a domain, and can we sync only some accounts rather than all of them.
Both are worth understanding before a large rollout, because both are easier to set up correctly than to correct afterwards.
If you have not connected Salesforce yet, start with Salesforce integration setup.
How matching works
Salesmotion links each tracked account to Salesforce in two steps. First it uses any Salesforce record ID already stored on the account. Then it compares the account's domain with the domain in the Website field of each Salesforce account. On each sync it writes the fields you have mapped, such as the Salesmotion Score or Top News, to the linked records. Syncs run every 12 hours, and an admin can start one with the Sync button on the Salesforce settings page.
This is reliable when each company maps to one Salesforce account. It needs attention when it does not.
When several Salesforce accounts share a domain
This is common in larger organizations, and it happens for legitimate reasons:
- Regional records for one global company, such as separate EMEA and North America accounts
- Divisional records for different business units
- Duplicate records created over time by different teams
- Parent and subsidiary records where the subsidiary uses the parent's domain
Because the match is on domain, Salesmotion links all of these records to the one Salesmotion account. One becomes the primary record and the others are linked as additional records:
- Fields Salesmotion writes go to every linked record.
- Fields Salesmotion reads from Salesforce, and the account owner, come from the primary record.
- If the linked records disagree on a field Salesmotion reads, Salesmotion skips that field for the account and shows an error in the sync log.
If you have duplicate domains in Salesforce, confirm the behavior for your instance before rolling out widely. Contact support@salesmotion.io with an example, and we will confirm which record is primary in your configuration and, if needed, adjust the mapping.
Diagnosing it yourself: pick one company where you know several Salesforce records share the domain, run a sync, and check which records received the mapped fields. That answers the question definitively for your setup in one observation.
Reducing the problem
Whatever the matching behavior, fewer duplicates is better:
- Deduplicate where you can. Records that exist only because two teams created the same account should be merged. This improves reporting well beyond Salesmotion.
- Use distinct domains where they exist. Subsidiaries with their own domain should carry it, which lets each match independently.
- Decide on a primary record for genuinely distinct regional or divisional records that must share a domain, and tell us which it is.
Scoping which accounts sync
Teams frequently want to sync a subset rather than everything: only tier 1 accounts, only accounts owned by a particular team, only a named target list. Two things are worth separating.
Which accounts receive fields. The sync writes mapped fields to the Salesforce records of the accounts you track in Salesmotion. The control point is which accounts you track. If your Salesmotion account list is already your target list, no configuration is needed. See Managing accounts. If you need to track accounts in Salesmotion that should not write to Salesforce, contact support@salesmotion.io.
Which Salesforce Accounts are imported. An admin chooses this in the Accounts section of the Salesforce settings, under Import from:
- Synced owners: the Accounts owned by the Salesmotion users you pick.
- Salesforce list view: the Accounts in a list view, with no row limit. Good for "Tier equals 1 and Owner is in this team".
- Salesforce report: the Accounts in a report with an Account ID column. Salesforce returns at most 2,000 rows per report, so use a list view for more.
- Salesforce checkbox field: the Accounts where a checkbox, for example one your team ticks for tier 1 accounts, is ticked.
Click Preview to see how many Accounts are in scope and how many would be imported before you save. Accounts without a Website are skipped. Each imported account uses a slot in your plan.
Removing accounts again is a separate switch, off by default. When an admin turns it on, only accounts the sync imported are removed, never accounts your team added, and Salesmotion never deletes anything in Salesforce. See Importing accounts from your CRM.
Worth deciding early. Retrofitting a filter after signals have written to hundreds of records means cleaning up records that should not have received them.
Before a large rollout
A short checklist that prevents the common problems:
- Check for duplicate domains in your Salesforce account records, and note whether they are genuine distinct entities or true duplicates
- Decide the scope of which accounts should receive signals
- Test with a small set of accounts and confirm signals land on the records you expect
- Confirm field mapping so signals appear where your reps look, rather than on a tab nobody opens
That last point matters more than it sounds. A correctly working integration that writes to a field nobody has on their page layout is indistinguishable from a broken one.
Frequently asked questions
Does the sync write back to Salesmotion?
Yes, for the fields you choose. Each field mapping has a direction: Salesmotion to CRM or CRM to Salesmotion. Country, Account Type, Priority, and your own custom fields can be read from Salesforce, and account owners sync from Salesforce, matched to Salesmotion users by email.
Will syncing overwrite fields our reps maintain?
Salesmotion writes only to the Salesforce fields you map. Map its data to dedicated fields so it never overwrites fields your team maintains, and confirm the mapping during setup so everyone knows which fields are managed by the integration.
Can we sync to HubSpot instead?
Yes. See the HubSpot integration guide. The Salesforce integration is the more mature of the two.
An account is not receiving signals in Salesforce
Check in order: the account is tracked in Salesmotion, it has generated signals in the platform, the domain matches the Website field on the Salesforce record, and the fields are on the page layout. Most reports of this resolve at step two (no signals generated yet, usually a keyword configuration issue) or step four (signals present but not visible).