CRM sync puts what ZenABM knows about an account where your sales team already works. Engagement data, account scores, ABM stages and intent signals are written onto the company record in HubSpot, Salesforce or Attio, and your deals flow back into ZenABM for revenue attribution. You do not create a single custom property: ZenABM creates them for you, and you choose which ones.
What gets synced
ZenABM writes to the company (HubSpot), account (Salesforce) or company record (Attio):
Engagement data
Impressions, clicks, engagements and spend: lifetime, for active ABM campaigns, and over 7, 14, 30 and 90-day windows, plus the campaigns and ad sets behind them.
Account scores
The engagement score that ranks how warm an account is.
ABM stages
The account's current ABM stage and the furthest stage it ever reached, written as a select property so you can filter and build workflows on it.
Intent signals
The intents detected from ad engagement, ready for personalizing outreach.
In the other direction, ZenABM reads your deals, pipelines and (in HubSpot) lifecycle stages and contacts, which power the Deal Dashboard, influenced revenue on the Dashboard and the CRM-based conditions in your ABM stage rules.
No custom properties to build
Connecting is an OAuth approval; there is no property mapping to do by hand. Turn on the analytics sync and tick the fields you want. ZenABM creates each one in your CRM (in HubSpot under a ZenABM LinkedIn Metrics property group, in Attio with a [ZenABM] prefix) and keeps it updated on every sync.
- You choose the properties. Every field is opt-in. Start with the core ones (ABM stage, active ABM campaigns, intents) and add metric windows once sales tells you what they use.
- You choose the data. Pick which pipelines and deal stages ZenABM reads, and set the influence threshold and window used for attribution.
- ZenABM owns what it creates. Its properties are rewritten on every sync, so keep your own fields for anything you edit by hand. Properties you already had are never changed.
Use it in workflows
Because the data lands as ordinary CRM properties, it works with everything your CRM already does:
- Trigger workflows. "ABM stage changed to Interested" or "intent contains Pricing" becomes a HubSpot workflow, a Salesforce flow or an Attio automation that creates a task, alerts a rep or enrolls a sequence.
- Inform outreach. Reps see which campaigns an account engaged with and what it is interested in, on the record, before they write the first line.
- Report in your CRM. Build lists and dashboards on ABM stage or engagement score without exporting anything.
Company matching
Attribution is only as good as the link between a ZenABM company and its CRM record. Matching runs automatically after every sync, and each integration has a Matching page that shows the matches, the duplicates and the records ZenABM could not place, so you can fix them by hand.
Set it up
HubSpot
The deepest integration: deals, pipelines, lifecycle stages, contacts and property write-back.
Salesforce
Opportunities in, engagement fields out onto the Account object.
Attio
Company attributes and deal stages both ways, with webhooks keeping deals fresh.
Webhooks
Send the same signals to Clay and any other tool.