CRM Sync Discrepancies

If the numbers in your CRM don't match what you see in Fibbler, it almost always comes down to one of two things: sync timing or domain matching.

Numbers in CRM don't match Fibbler

Fibbler pulls the latest data from LinkedIn on Saturdays and then runs the weekly CRM sync on Sundays. The data pushed to your CRM is a snapshot of what was available at that moment.

When you check Fibbler during the week after a sync, the numbers in the app will have continued to update with new LinkedIn data, while the CRM numbers stay frozen at the Sunday snapshot. This is the most common reason the two don't match.

The CRM sync is always a weekly snapshot. The numbers will align most closely right after a Sunday sync, then gradually drift apart during the week as new LinkedIn data comes in.

Companies not syncing to CRM

If a company shows engagement in Fibbler but has no data in your CRM, it is almost always a domain mismatch. Fibbler matches companies to your CRM based on website domain, and the domain we have comes from the company's LinkedIn page.

To troubleshoot:

Find the company in Fibbler and check the website domain shown on the company card
Open the same company in your CRM and check the domain/website field
Compare the two. They need to match for the sync to work

Common reasons for a mismatch:

The domain field in your CRM is empty
The root domain doesn't match. The company may use a different domain on their LinkedIn page than what you have in your CRM (e.g., "acme.co.uk" on LinkedIn vs "acme.com" in your CRM, or a subsidiary listing its parent company's domain)
The CRM record does not exist. Fibbler only updates existing companies/accounts, it does not create new records

If you notice a pattern of missing companies, check that your CRM company records have clean, populated domain fields. The more complete your CRM data is, the more companies Fibbler can match.

Fibbler says the CRM connection needs attention

When the weekly sync cannot write to your CRM, Fibbler shows what it found on the Data Sourcespage, on the CRM's own card next to the Reconnect button (or at the top of the page if the connection no longer has a card). The account owner also gets one email about it, and that email links straight to the same page. There are three messages, because there are three different things to do:

This connection needs to be renewed. Fibbler has been signed out of your CRM, so it stopped updating your companies. Reconnect the CRM and it starts again.
Fibbler cannot write to this workspace. The connection can read your data but not write to it, which happens when read-only access was granted. Reconnect and choose read and write access when your CRM asks what to allow.
The connected user needs more permissions. Fibbler is connected as a user who is not allowed to add custom fields, so there is nowhere to put the LinkedIn numbers. Either ask an admin to let that user manage custom fields, or reconnect signed in as an admin.

Waiting for the next sync won't fix these. Once you've done what the message asks, it clears. If the same thing happens again later you will be told again, rather than it going quiet because you were told once.

Salesforce: fields and rejected records

Two Salesforce cases have their own emails, because only someone in your org can resolve them:

A field Fibbler could not create. The email lists the field label, API name and data type so you can create it by hand. If the field already exists but is hidden from the user Fibbler connects as, the email says so and tells you not to create a duplicate. Fibbler tries to grant itself visibility on a hidden field first, and only writes to you about the ones it could not unhide.
Records your org refused. A validation rule or a before-save flow can reject every record Fibbler sends, which leaves the fields empty with no error anywhere in Fibbler. You get one email per day naming the records and quoting what Salesforce said, since the flow name and error id are what your admin needs. Fibbler also stops pushing for that run after three batches in a row come back refused, rather than spending your API quota on a guaranteed rejection. The next weekly sync tries again on its own, so the numbers appear once the rule is changed.

When Fibbler creates the field itself, leave the __c suffix out of the Field Name box: Salesforce adds it. The full field list is in Connect Salesforce.

The LinkedIn connection, not the CRM one

A dead LinkedIn connection stops the numbers at the source, so nothing new reaches your CRM either. Fibbler checks the LinkedIn connection nightly and flags it on Data Sources when it has stopped working, and the LinkedIn section opens on that state when you arrive. The email about it links to the workspace the broken connection belongs to, which matters if you have several: each workspace has its own LinkedIn connection, and the one you are looking at may be fine. If a colleague has already reconnected, the email can be ignored.

Still not working?

Email support@fibbler.co with an example company domain and a screenshot from both Fibbler and your CRM so we can look into it.