Every setting explained
What each control on the HubSpot card does, what it changes in your CRM, and the mistakes it protects you from.
All of these live on the HubSpot card in Settings → Integrations. Only workspace admins can change them; everyone else sees them greyed out.
Changes save immediately — there is no "Save" button.
1. Contact sync — the master switch
The green (or amber) band at the top of the card. It has exactly two states.
| State | What it means |
|---|---|
| Paused | Sillage writes nothing to HubSpot on its own. |
| Active | Sillage pushes contacts according to the settings below. |
A freshly connected portal always starts Paused. So does an existing connection the first time it sees this new settings panel. That is on purpose: connecting HubSpot gives Sillage permission to write, it does not give it instructions. You give the instructions below, then press Launch sync.
Pausing later stops future writes. It does not roll anything back — contacts and properties already written to HubSpot stay exactly as they are.
One thing keeps working while paused: the HubSpot button on a lead in your Sillage leads table. That is you clicking, deliberately, on one lead (or a selection of them) — so Sillage does it. The pause switch only governs what Sillage does automatically.
2. Contact Push — when a contact gets pushed
Two triggers exist in Sillage. This choice decides which ones are live.
On new intent only
A lead is pushed to HubSpot when a buying signal is detected on it. No signal, no push. This is the default and the conservative choice: HubSpot only ever receives people who did something worth reacting to.
Whether a lead who is not yet in HubSpot gets created is decided by Contact Creation Mode below — not here.
Choose this when: your CRM is the source of truth for "real" contacts and you don't want it filling up with people nobody has engaged.
Full mapped roster
Every contact matching your persona is pushed as soon as the account mapping for their company completes — signal or no signal. Intent data then arrives on those records automatically as signals get detected.
Two behaviours worth knowing:
- Newcomers only. Each mapping cycle pushes the people it has never pushed before. It does not re-push your whole roster every time. Contacts already in HubSpot keep getting their intent data updated through the signal path.
- It forces creation on. A roster push exists to put people in HubSpot who aren't there yet, so Sillage locks Contact Creation Mode to Create and update while this option is selected. You will see a note saying so, and the creation options become read-only.
Choose this when: you want your reps to see the whole buying committee of a target account in HubSpot from day one, and use intent to prioritise inside it.
Full mapped roster writes considerably more contacts than intent-only. On a large target account list this can be thousands of records. Try it on a small account list first if your portal is close to its contact limit.
Only create contacts with an email
This toggle appears only when Full mapped roster is selected. It is on by default, and should usually stay on.
HubSpot deduplicates contacts by email address. A contact pushed without one cannot be matched against what already exists, so you risk a duplicate of a person your portal already has. With this on, Sillage skips contacts whose email it hasn't found yet — and picks them up on a later mapping cycle, once the email is available.
Turn it off only if you knowingly want LinkedIn-only records in HubSpot and accept the duplicate risk.
3. Contact Creation Mode — whether a missing person can be created
Update existing contacts only
Sillage only writes to contacts that already exist in your portal. It will enrich them with intent data, signals and status — but it never creates anyone.
There is one exception, and it is intentional: if someone on your team manually acts on a lead in Sillage — changes its status, edits it, pushes it from the leads table or the Chrome extension — that lead is created in HubSpot even under this mode. A human asked for it explicitly.
Create and update contacts
Sillage creates contacts that don't exist yet, and updates the ones that do.
Before creating, it looks for a match in your portal, in this order: the HubSpot id it already stored for that person, then their LinkedIn, then their email, then their name. So re-running a sync does not produce duplicates of the same person.
The one combination that silently does nothing: On new intent only + Update existing contacts only. A brand-new prospect who just showed a buying signal is not in HubSpot, so there is nothing to update — the signal is dropped and no record appears. Sillage shows a warning under the section when you select this pair. It is a valid setup if your CRM only tracks known contacts, but know that this is what it does.
4. Sync options
Create missing companies & associate
Off by default.
When Sillage pushes a contact whose company has no record in your portal, it creates the company and associates the contact to it.
To avoid duplicating companies you already track, it matches on domain first, then the LinkedIn page, then the name. Within a single sync run, several contacts from the same company resolve to exactly one company record — not one per contact.
Leave it off if company records in your portal are created by another process (an import, a data provider, another integration) and you don't want a second source writing them.
Never touch customer contacts
On by default, and worth keeping on.
Any contact whose HubSpot lifecycle stage is Customer is left completely alone: no property updates, no re-creation, nothing. This protects your closed accounts from automated writes that could confuse a CSM or trigger a marketing workflow aimed at prospects.
Two details:
- It matches HubSpot's standard Customer lifecycle stage. If your portal added its own custom stages further down the funnel, those are not covered.
- If Sillage cannot read the lifecycle stage of a contact for some reason, it does not skip it. The protection only applies when the customer status is confirmed.
Quick reference
| Setting | Default | Safest for a first launch |
|---|---|---|
| Contact sync | Paused | Launch once the rest is set |
| Contact Push | On new intent only | On new intent only |
| Only create contacts with an email | On | On |
| Contact Creation Mode | Update existing only | Create and update |
| Create missing companies & associate | Off | Off |
| Never touch customer contacts | On | On |
These defaults apply to connections made since each option shipped. If your workspace connected HubSpot earlier, some toggles may sit in a different position — what the card shows is always the truth, so check it before your first launch rather than trusting the column above.
Ready to pick a setup? See Scenarios.