What actually syncs

The properties Sillage creates in your portal, the fields it fills by default, and how to remap them.

The Sillage property group

When you connect, Sillage creates a property group called Sillage Properties on your contacts (and one field on companies). These are the fields Sillage owns and keeps up to date — they never overwrite your own properties.

Property in HubSpotTypeWhat it holds
Sillage Intent ScoreNumberHow strong the buying intent is on this person right now.
Sillage Signal CountNumberHow many signals Sillage has detected on them.
Sillage Detected SignalsCheckboxesWhich kinds of signal fired — one option per agent type you run.
Sillage Last Detected SignalSingle selectThe most recent one.
Sillage Last Signal DateDateWhen it happened.
Sillage Lead StatusDropdownThe status the lead carries in Sillage (Pending, Contacted, Meeting booked, Customer, Not ICP…).
Sillage Last ImportDateThe last time Sillage wrote to this record.
Sillage Lead ID / Sillage Company IDTextJoin keys back to Sillage. Leave them alone — they are what keeps the two systems in step.

The signal options (Detected Signals, Last Detected Signal) are filled in from the agents in your workspace. Create a new agent, and its signal type appears as a new option the first time it fires.

These are the properties to build your HubSpot views, lists and workflows on. "Contacts where Sillage Intent Score is greater than 80" is a working prioritisation list on day one.

Fields filled by default

Beyond the Sillage properties, Sillage fills standard HubSpot fields so a newly created contact isn't empty.

On the contact

From SillageInto HubSpotWhen
First namefirstnameOn creation
Last namelastnameOn creation
EmailemailAlways
PhonephoneAlways
Job titlejobtitleAlways
LinkedIn URLhs_linkedin_urlAlways
LocationcityAlways
Company namecompanyOn creation

On the company (only when Create missing companies & associate is on)

From SillageInto HubSpotWhen
Company namenameOn creation
DomaindomainAlways
Number of employeesnumberofemployeesAlways

A few more mappings exist but ship switched off — industry, employee range, company location, the LinkedIn handle fields. Turn them on from the field mapping page if you want them.

Editing the mapping

Click Edit Field Mapping on the HubSpot card (admins only — contributors see a read-only View Field Mapping).

There you can:

  • Switch between Accounts and Contacts to map each object separately.
  • Point a Sillage property at a different HubSpot field, including your own custom properties.
  • Turn individual mappings on and off.
  • Choose when a field syncs: only when the record is created, only on later updates, or always. Use only on creation for fields your team edits by hand afterwards — that way Sillage sets a starting value and never overwrites their work.
  • Refresh the HubSpot property list if you just created a new custom field and it doesn't show up yet.

HubSpot's built-in Industry field only accepts values from its own fixed list, so Sillage cannot write to it — it appears in the picker but stays disabled. If you want industry in HubSpot, create a plain text custom property and map it there.

What Sillage does not do

  • It does not delete contacts, companies or properties in HubSpot.
  • It does not turn your HubSpot contacts into Sillage leads. The contact sync is one-way: Sillage → HubSpot.
  • It does not write to deals.
  • It does not touch contacts marked as customers, when that option is on.

The one thing that goes the other way

Everything on this page describes Sillage writing to HubSpot. One separate feature reads from it: Sync Companies, on the Settings → Segments page. It pulls your HubSpot companies into Sillage so you can build account lists out of your own CRM and carry the HubSpot owner across.

Different button, different purpose — and it is not affected by the pause switch or by any of the contact push settings.

On this page