Connect Attio to Fibbler
- In Fibbler, go to Data Sources
- Click "Connect CRM" and pick Attio from the list. The button says "Connect LinkedIn First" and can't be clicked until LinkedIn Ads is connected
- Authorize the connection with your Attio workspace
Permissions Fibbler needs
- Read access to Company records: to match ad engagement with the companies in your workspace
- Read access to Deal records: to calculate influenced pipeline and revenue
- Read access to object configuration
object_configuration:read: to read the names of the attributes on your Companies object, so Fibbler can see which of its own attributes already exist - Write access to records
record_permission:read-write: only used by CRM Data Sync and Ad Engagement Signals, to write Fibbler's own attributes, keep the signal list, and leave a note
Configure your CRM settings
After connecting Attio, make sure to complete the CRM configuration in Fibbler:
- Pick your won and lost stages: Under "How do you define a won deal?" and "How do you define a lost deal?", pick the Attio deal stage for each. It's one stage for won and one for lost. Then click "Save Stages"
- Filter deals by attribute (optional): If you only want to count some of your deals, open "Advanced" and add a filter. Fibbler then only counts deals where the attributes you choose match the values you pick
What Fibbler writes to Attio
Nothing, until you turn a feature on. Two features write to Attio, and both are off by default. On a company that already exists they only ever write Fibbler's own attributes: your name, domains, owner and everything else your team maintains are never changed by us.
CRM Data Sync attributes (optional)
CRM Data Sync is optional. If you enable it, Fibbler creates attributes on your Companies object for LinkedIn impressions, clicks, engagements, paid video views, organic impressions, organic engagements and engagement level, each over a 7, 30 and 90-day window.
With the Google Ads or Meta Ads add-on, it also creates one visit attribute per channel and window:
- Google Ads:
fibbler_google_ads_visits_7_days,fibbler_google_ads_visits_30_days,fibbler_google_ads_visits_90_days, titled "Google Ads Visits (7 days)" and so on - Meta Ads:
fibbler_meta_ads_visits_7_days,fibbler_meta_ads_visits_30_days,fibbler_meta_ads_visits_90_days, titled "Meta Ads Visits (7 days)" and so on
The sync runs weekly on Sundays and only updates company records that already exist. The details are in the Google Ads CRM Sync and Meta Ads CRM Sync docs.
Ad Engagement Signals in Attio (optional)
Ad Engagement Signals sends the companies engaging with your ads to the place your team already works. With Attio as a destination, a signal does four things in your workspace.
It creates six attributes on the Companies object, the first time a signal writes to Attio. There is one set however many signals you run:
- Fibbler Signal Type
fibbler_signal_type— why the company was surfaced: New, or Rising fast - Fibbler Signal Date
fibbler_signal_date— when Fibbler last surfaced it - Fibbler Signal Name
fibbler_signal_name— which signal surfaced it - Fibbler Signal Channels
fibbler_signal_channels— which ad channels it engaged with - Fibbler Signal Why
fibbler_signal_why— the evidence, in one line - Created by Fibbler
fibbler_created— a checkbox, set only on a company record a signal created
It keeps a list, one per signal, with Companies as its parent object and named Fibbler: followed by the signal's name. A company keeps its entry for 30 days and then drops out; the record, the attributes and the history stay.
It leaves a note on the company record, with the one-line reason a rep reads.
It creates a company that is missing.Signals are optional and only run once you set one up and turn it on. When a signal sends to Attio and the company isn't there yet, we create it. Each record created this way is stamped with Created by Fibbler, so you can find them all again.