CRM Data Sync

CRM Sync pushes LinkedIn Ads data (impressions, clicks, engagements, video views) and LinkedIn organic data (organic impressions and engagements) directly into your CRM at the company level.

How it works

You connect LinkedIn and your CRM
Choose a sync duration: 7, 30, or 90 days
Fibbler fetches LinkedIn data via API
Fibbler searches for matching accounts in your CRM based on domain
If the account exists, Fibbler pushes the data to custom fields on that account

Sync timing

LinkedIn ad data inside Fibbler refreshes nightly.
CRM Sync writes that data to your CRM weekly, every Sunday, until you turn it off.
When you first toggle CRM Sync on, Fibbler runs an initial sync immediately for the last 7, 30, and 90 day windows (for whichever of those you selected), then continues writing weekly on Sundays.
Each window is written in its own pass inside that one weekly run, in the order 7, then 90, then 30 days. The passes are hours apart, so if you look at field history you will see the three windows carrying different timestamps from the same run. They all read the same nightly data.

There is no self-serve manual sync button in the app. If you need an off-schedule sync, contact support@fibbler.co and we can trigger one for you.

Important: The sync only writes to companies or accounts that are already in your CRM. Fibbler never creates new records during the sync process.

How values are updated each week

The fields are rolling windows, so what they hold depends on whether the company was active in that window during the week that just ended:

Active in the window: every field is rewritten with the current total. A metric the company had no activity on is written as 0, so a company with ad impressions but no organic activity gets 0 in the organic fields.
No longer in the window: the fields are emptied, not set to 0. The company drops out of both a "greater than 0" filter and a "is known" filter. This applies on HubSpot, Salesforce, Attio and Pipedrive.
Clearing needs a previous week to compare against, so the first weekly run after you turn CRM Sync on only writes values. Companies start dropping out from the second run onwards.
Records are only ever updated. Nothing is deleted, and no new company records are created.

Clearing companies that leave the window started with the weekly run of 16 August 2026 on HubSpot, and with the weekly run of 30 August 2026 on Salesforce, Attio and Pipedrive. Values written before those dates on companies that have since left the window are not cleared automatically, so a field can still be holding an old figure from an earlier week. If you see that on your records, contact support@fibbler.co and we will sort out a one-time cleanup.

Why the lowest value you ever see is 3

LinkedIn does not report a company below 3 on the endpoint that feeds these rolling windows, so the fields go from 0 straight to 3 and never hold a 1 or a 2. Fibbler does not round, floor or suppress anything. The monthly figures you see inside Fibbler come from a different LinkedIn endpoint without that limit, which is why they can show smaller numbers than the synced fields for the same company.

What you can do with synced data

Build attribution reports in your CRM
Create automated workflows (e.g., notify BDRs when an account crosses an engagement threshold)
Build account scoring models using LinkedIn engagement data
Track trends over time with weekly snapshots

For step-by-step guides on building these workflows, check out our Playbooks.

Custom fields created

Fibbler automatically creates custom fields/attributes on your CRM company object for LinkedIn Impressions, Clicks, Engagements, Paid Video Views, Organic Impressions, Organic Engagements, and Engagement Level, each for 7, 30, and 90-day windows.

Paid Video Views is written as LinkedIn Paid Video Views (7 days) and the same for 30 and 90 days. See what counts as a video view. If your sync was set up before this field existed, it is added automatically on the next weekly run and filled with your current 7, 30, and 90 day totals. Your existing fields are not renamed or moved.

On HubSpot, these are standard company properties, so HubSpot Enterprise is not required.

For CRM-specific details on the fields created:

HubSpot custom fields
Salesforce custom fields (includes full API name reference table)

Supported CRMs

CRM Sync writes to all supported CRMs: HubSpot, Salesforce, Attio, and Pipedrive. The fields are created on the company or organization object in each.

Multiple pipelines

On the Data Sources page you can select multiple pipelines and define deal types and Closed Won and Closed Lost stages for each. See Defining won and lost deals.

Why is the CRM Sync toggle greyed out or not clickable?

CRM Sync is available on all plans (limited on Growth, unlimited on Unlimited and Agency), so it is usually not a hard plan block. The most common causes are:

Your CRM is not connected, or LinkedIn is not connected
Missing CRM permissions or scopes
A trial or billing state that needs resolving

Try reconnecting the CRM and granting all requested scopes. If the toggle is still not clickable, contact support@fibbler.co.

Data access

Two Fibbler features write to your CRM: CRM Data Sync and Ad Engagement Signals. Signals write their own six fields, build a CRM list for each signal, add a note on the company in Attio, Salesforce and Pipedrive, and can create company records. All other features (Company Insights, Campaign Analytics, Customer Journeys, etc.) only read CRM data to match it with LinkedIn activity.

When the sync runs, it only updates Fibbler-created custom fields on existing company records. It never modifies your existing CRM fields, creates new records, or deletes anything. You can turn off the sync at any time, and the custom fields will simply stop updating.

If the numbers in your CRM don't match what you see in Fibbler, it is usually due to sync timing or domain matching. See CRM Sync Discrepancies for troubleshooting steps.