Connect Salesforce to Fibbler
Here's how you connect Salesforce, the permissions your Salesforce admin gives the user who connects, and the fields we add if you turn on CRM sync or Ad signals. We read your Accounts and Opportunities to see which of your deals are at companies your ads reached and engaged. Salesforce needs the Unlimited or Agency plan, and it works during the free trial. You connect it on the Data sources page.
- In Fibbler, go to Data sources
- Click "Connect CRM" and pick Salesforce from the list. Until LinkedIn Ads is connected, the page shows "Connect LinkedIn Ads first." instead of the button
- Type your Salesforce My Domain URL, like
MyDomainName.my.salesforce.com(for a sandbox it'sMyDomainName--SandboxName.sandbox.my.salesforce.com), then click "Connect Salesforce" - Sign in to Salesforce and allow the connection
What your Salesforce admin needs to set up
We ask Salesforce for API access. Salesforce has no read-only version of that, so the user who connects decides what Fibbler can actually do. We recommend a dedicated integration user, with only the permissions below in a permission set. That way the connection doesn't stop when a colleague leaves.
Always needed
| Permission | What Fibbler does with it |
|---|---|
| API Enabled | Lets the connection use the Salesforce API at all |
| Read on Account | We read the Account name and website, to match your ad data to your companies |
| Read on Opportunity | We read the name, amount (or the amount field you pick), stage, type, created date, close date and Account, for influenced pipeline and revenue. The user also needs to see the Account Name field on Opportunities, or we can't tell which company a deal belongs to |
| View All Records on Account and Opportunity | Lets us see every deal, not only the ones shared with the user. Without it, your sharing rules hide deals and influenced pipeline comes out too low. You can skip it if your sharing settings already give the user read access to all Accounts and Opportunities |
That's all reporting needs, and a user with only these four can't change anything. Your Salesforce edition needs API access. Enterprise, Unlimited and Performance have it, and Professional only has it with Salesforce's API add-on. You don't need the org-wide "View All Data" permission.
Only for CRM sync and Ad signals
| Permission | What Fibbler does with it |
|---|---|
| Modify Metadata Through Metadata API Functions, with Customize Application | We use these to create our own fields on Account, and to rename a field when you rename an ad set group. You can skip them and create the fields yourself |
| Edit on Account | We write values into those Fibbler fields. Edit only covers the Accounts this user can edit through your sharing rules. To update every Account, give them Modify All Records on Account, or set Account sharing to Public Read/Write. Otherwise CRM sync skips Accounts owned by others |
| Create on Account | Lets a signal create an Account your org is missing |
| Manage Public List Views | We create one public Account list view per signal, so your whole team sees it |
| Chatter turned on in your org (it is by default) | We post the note on the Account that says why a signal sent it |
Leaving any of these out doesn't break anything else. Without the field permissions, you create the fields yourself from the tables below, and we pick them up on the next run. Without the list view or Chatter permission, a signal still writes its fields and skips the list view or the note. When we create a field, we also give the permission sets in your org read and edit access to that field only, so your team can see the values.
Configure your CRM settings
Once Salesforce is connected, finish the setup on the Salesforce card on Data sources:
- Opportunity Types (optional): if you use Opportunity Types to tell New Business and Upsells apart, tick "We use 'opportunity types' and want to customize them in the Fibbler platform" and pick one type. If you don't, leave the box unticked, or keep "All types (default)".
- Set Closed Won and Closed Lost stages: tell us which opportunity stages count as Closed Won and Closed Lost. You can pick more than one stage for each.
- Amount: pick the opportunity field we should read deal value from, then click "Save stages".
Turning on CRM sync
CRM sync writes your LinkedIn ad data onto your Salesforce Accounts. You don't need it for anything else in Fibbler. You turn it on under LinkedIn Ads → Activation → CRM sync, and if the user has the field permissions above, we create the fields for you. CRM sync never creates an Account.
Custom fields for LinkedIn data
These are the fields CRM sync uses. If you create them yourself, go to Salesforce Setup → Object Manager → Account → Fields & Relationships → New, and use exactly these API names. In the Field Name box, leave out the __c at the end, because Salesforce adds it:
| Field Label | API Name | Data Type |
|---|---|---|
| LinkedIn Ad Clicks (90 days) | fibbler_linkedin_clicks_90_days__c | Number(18, 0) |
| LinkedIn Ad Clicks (30 days) | fibbler_linkedin_clicks_30_days__c | Number(18, 0) |
| LinkedIn Ad Clicks (7 days) | fibbler_linkedin_clicks_7_days__c | Number(18, 0) |
| LinkedIn Ad Impressions (90 days) | fibbler_linkedin_impressions_90_days__c | Number(18, 0) |
| LinkedIn Ad Impressions (30 days) | fibbler_linkedin_impressions_30_days__c | Number(18, 0) |
| LinkedIn Ad Impressions (7 days) | fibbler_linkedin_impressions_7_days__c | Number(18, 0) |
| LinkedIn Ad Engagements (90 days) | fibbler_linkedin_engagements_90_days__c | Number(18, 0) |
| LinkedIn Ad Engagements (30 days) | fibbler_linkedin_engagements_30_days__c | Number(18, 0) |
| LinkedIn Ad Engagements (7 days) | fibbler_linkedin_engagements_7_days__c | Number(18, 0) |
| LinkedIn Paid Video Views (90 days) | fibbler_linkedin_vid_views_90_days__c | Number(18, 0) |
| LinkedIn Paid Video Views (30 days) | fibbler_linkedin_vid_views_30_days__c | Number(18, 0) |
| LinkedIn Paid Video Views (7 days) | fibbler_linkedin_vid_views_7_days__c | Number(18, 0) |
| LinkedIn Organic Engagements (90 days) | fibbler_linkedin_org_engage_90_days__c | Number(18, 0) |
| LinkedIn Organic Engagements (30 days) | fibbler_linkedin_org_engage_30_days__c | Number(18, 0) |
| LinkedIn Organic Engagements (7 days) | fibbler_linkedin_org_engage_7_days__c | Number(18, 0) |
| LinkedIn Organic Impressions (90 days) | fibbler_linkedin_org_impres_90_days__c | Number(18, 0) |
| LinkedIn Organic Impressions (30 days) | fibbler_linkedin_org_impres_30_days__c | Number(18, 0) |
| LinkedIn Organic Impressions (7 days) | fibbler_linkedin_org_impres_7_days__c | Number(18, 0) |
| LinkedIn Engagement Level (90 days) | fibbler_linkedin_eng_level_90_days__c | Text(50) |
| LinkedIn Engagement Level (30 days) | fibbler_linkedin_eng_level_30_days__c | Text(50) |
| LinkedIn Engagement Level (7 days) | fibbler_linkedin_eng_level_7_days__c | Text(50) |
When you create a field yourself, set its Field-Level Security to visible for the profile of the user who connected Fibbler, and for anyone else who should see the data. If the field is hidden from that user, we can't write to it, and we report it as skipped even though it exists.
Custom fields for Google Ads and Meta Ads visits
With the Google Ads or Meta Ads add-on, CRM sync can also write website visits from those channels onto the same Accounts. You set up each channel on its own, and each one creates its own Number fields:
| Field Label | API Name |
|---|---|
| Google Ads Visits (7 days) | fibbler_gads_visits_7_days__c |
| Google Ads Visits (30 days) | fibbler_gads_visits_30_days__c |
| Google Ads Visits (90 days) | fibbler_gads_visits_90_days__c |
| Meta Ads Visits (7 days) | fibbler_meta_visits_7_days__c |
| Meta Ads Visits (30 days) | fibbler_meta_visits_30_days__c |
| Meta Ads Visits (90 days) | fibbler_meta_visits_90_days__c |
You can also sync a named group of campaigns instead of the whole account. That creates one field per group and window, with a label like "Google Ads Visits 7 days - Brand", cut short to fit Salesforce's 40-character limit. We go through the details in Google Ads CRM sync and Meta Ads CRM sync.
Custom fields for Ad signals
Ad signals use these six fields. We create them on Account the first time a signal writes to Salesforce, and it's the same six however many signals you run:
| Field Label | API Name | Data Type |
|---|---|---|
| Fibbler Signal Type | Fibbler_Signal_Type__c | Text(255) |
| Fibbler Signal Date | Fibbler_Signal_Date__c | Date/Time |
| Fibbler Signal Name | Fibbler_Signal_Name__c | Text(255) |
| Fibbler Signal Channels | Fibbler_Signal_Channels__c | Text(255) |
| Fibbler Signal Why | Fibbler_Signal_Why__c | Text(255) |
| Created by Fibbler | Fibbler_Created__c | Checkbox |
Make these visible to the connecting user too, like the ones above. If the user can't create fields, we email you this list instead of failing quietly, and the next run picks the fields up once they exist.
What Ad signals write to Salesforce
Besides the fields above, a signal that sends to Salesforce does three things. We explain how a signal picks companies in Ad signals.
It keeps an Account list view, one per signal, labelled Fibbler: followed by the signal's name. An Account stays in it for 30 days. If you can't find the list view, search your Account list views for the signal's name.
It leaves a note on the Account, with a one-line reason for your rep to read.
It creates an Account that is missing, if you chose that when you set up the signal. Each one has Created by Fibbler ticked, so you can find them later.
If the connection stops working
We read Salesforce as the user who connected it, with that user's access. So connect with someone who can see all your Accounts and Opportunities, and who will keep that access.
If Salesforce stops accepting our access, you'll see "This connection needs to be renewed" at the top of Data sources. Press Reconnect Salesforce and sign in again, as the same user or a teammate with the same access. Your settings stay as they were. If you sign in to a different Salesforce org, we treat it as a new CRM and remove the data from the old one.
Errors when you connect
- "That does not look like a Salesforce URL. It should look like myDomainName.my.salesforce.com." or the sign-in fails: use your My Domain URL, the one ending in
.my.salesforce.com, not the Lightning address from your browser bar that ends in.lightning.force.com. You find it in Salesforce under Setup → My Domain. - "That Salesforce connection attempt has expired. Please open the Sources page and press Connect Salesforce again." the sign-in didn't finish in time. Start again from Data sources and finish the sign-in in one go, in the same browser.
- OAUTH_APPROVAL_ERROR_GENERIC or OAUTH_APP_BLOCKED: see the two sections below.
Troubleshooting: OAUTH_APPROVAL_ERROR_GENERIC
If you get this error when you connect, a Salesforce admin needs to turn on the "Approve Uninstalled Connected Apps" permission for the user who connects:
- Go to Setup → Permission Sets
- Create or edit a permission set
- In System Permissions, enable "Approve Uninstalled Connected Apps"
- Assign it to the user and try connecting again
You can turn it off again once you're connected.
Troubleshooting: OAUTH_APP_BLOCKED
A Salesforce admin has blocked the Fibbler connected app for your org, so Salesforce refuses the connection before it reaches us. The permission above won't fix this. The app needs to be unblocked:
- Go to Setup → Connected Apps OAuth Usage
- Find the Fibbler app in the list
- Click Unblock
- Try connecting again
If Fibbler isn't listed under Connected Apps OAuth Usage, an admin may need to pre-authorize it in a permission set first.
Disconnecting Salesforce
Go to Data sources, open the Salesforce card and click Disconnect. We remove our access at Salesforce and stop syncing, and the CRM data we stored is deleted within 30 days. The fields, list views and notes we made stay in Salesforce until you remove them. If you're moving to another CRM, email support@fibbler.co and we'll help you switch.