CRM sync issues
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. Below you'll also find the warnings Fibbler shows when a connection needs attention, and how to switch to another CRM.
Numbers in CRM don't match Fibbler
We sync to your CRM once a week, on Sundays. What we send is a snapshot of the numbers at that moment.
During the week, the numbers in the app keep updating as new LinkedIn data comes in, while the CRM numbers stay at the Sunday snapshot. This is the most common reason the two don't match.
Companies not syncing to CRM
If a company shows engagement in Fibbler but has no data in your CRM, it's almost always because the domains don't match. We match companies to your CRM by website domain, and the domain we have comes from the company's LinkedIn page.
Here's how to check:
- 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 website (domain) field
- Compare the two. They need to match for the sync to work
These are the usual reasons they don't match:
- 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 (for example "acme.co.uk" on LinkedIn and "acme.com" in your CRM, or a subsidiary listing its parent company's domain)
- The company doesn't exist in your CRM. The CRM sync only updates companies and accounts that are already there. It doesn't create new ones
Fibbler says the CRM connection needs attention
When Fibbler can't read from or write to your CRM, it shows a warning on the Data sources page, 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 workspace owner and admins each get their own email about it, once per problem, with a link straight to the right workspace. Each warning asks for something different:
- This connection needs to be renewed. Your CRM has signed Fibbler out, so we stopped updating your companies. Reconnect the CRM and it starts again. The email is called "Reconnect [your CRM] in Fibbler".
- Fibbler cannot write to this workspace. The connection can read your data but not write to it, which happens when someone gave it read-only access. 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 we can't write your ad engagement data or your signals onto your companies. Ask an admin to give that user permission to manage custom fields, or reconnect signed in as an admin. On Dynamics 365, the user needs the System Customizer role.
- The connected user cannot see your deals' accounts (Salesforce). The user Fibbler connects as can't see the Account on your Opportunities, so we can't import your deals. Ask a Salesforce admin to give that user read access to Accounts and to the Account Name field on Opportunities, or reconnect as a user who has it. On Dynamics 365 the same problem reads The connected user cannot read your deals, and the user needs read access to Opportunities and Accounts.
- No room for more custom fields (Zoho CRM). Your Zoho CRM edition has no room for more custom fields on Accounts. Remove fields you don't use in Zoho or upgrade your Zoho CRM edition, then turn the sync on again. Reconnecting doesn't help here.
Salesforce: fields and rejected records
Two Salesforce problems get their own email, because only someone in your org can fix 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.
- Records your org refused. A validation rule or a before-save flow can reject every record Fibbler sends. That leaves the fields empty, and you don't see an error anywhere in Fibbler. So you get one email a day that names the records and quotes what Salesforce said, because your admin needs the flow name and error id. If Salesforce keeps refusing, we stop for that week and try again on the next sync. The numbers show up once the rule is changed.
When you create the field yourself, leave __c out of the Field Name box. Salesforce adds it. You'll find the full field list in Connect Salesforce.
When it's the LinkedIn or Google Ads connection, not the CRM
A broken LinkedIn connection stops the numbers at the source, so nothing new reaches your CRM either. Fibbler checks the LinkedIn connection every night and shows one of two warnings in the LinkedIn section of the Data sources page:
- LinkedIn connection needs to be renewed. Press Reconnect. The email is called "Reconnect LinkedIn in Fibbler". More
- LinkedIn ad account access lost. Have a teammate with access to the ad account reconnect LinkedIn. The email is called "Action required: LinkedIn ad account access lost". More
Each workspace has its own LinkedIn connection, and the email links to the workspace that has the problem, which matters if you're in several. If a colleague has already reconnected, LinkedIn shows as connected on Data sources and you can ignore the email.
Google Ads has two emails of its own. If you get "Action required: reconnect your Google Ads account", Fibbler's access to Google Ads is no longer valid, so press Reconnect under Google Ads on Data sources. The email "Google Ads account not syncing in Fibbler" lists the Google Ads accounts we lost access to. We explain what to do in An ad account says it was switched off.
Switching to another CRM
A workspace has one CRM at a time. To switch, open your current CRM on the Data sources page, click Disconnect and confirm. Then connect the new CRM and pick its pipelines, deal types and won and lost stages, the same way you did the first time. Your numbers then come from the new CRM's deals. We delete the CRM data we stored from the old one within 30 days of disconnecting.
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.