Ad signals
We send the companies engaging with your LinkedIn, Google and Meta ads to Slack, Teams, Clay or your CRM, along with what they did on each channel. We only send companies with no deal in your CRM yet, and each one once. Ad signals is on every plan and in the free trial. Growth has up to 3 signals, and Unlimited and Agency have as many as you like.
How it works
- Pick where the companies go: your CRM, a Slack or Teams channel, Clay, or an automation tool.
- Pick which ad channels feed it, and who counts as a fit.
- It runs on your schedule and only sends what's new since last time.
Companies come from LinkedIn Ads, Google Ads and Meta Ads, depending on which ones you tick and which ones are on your plan. A company engaging on two channels arrives once, with both named.
To set one up, go to Ad signals and press + Create new signal. With only LinkedIn Ads connected, Ad signals is under LinkedIn Ads → Activation. With Google Ads connected, it has its own place in the menu.
Warm accounts

The Warm accounts tab on the Ad signals page lists the companies with no deal in your CRM yet, where in the last 30 days:
- LinkedIn: people engaged with your paid ads at least 5 times.
- Google Ads and Meta Ads: someone visited your website from your ads at least once. One visit is enough, since a visit is already a click on an ad.
It's the same list as Warm accounts on Company insights. A company whose deals were all lost more than 6 months ago counts as warm again. New means no paid engagements (or visits) in the 30 days before, and Rising means more than in the 30 days before. You can filter the list and export it as a CSV.
Google Ads and Meta Ads in a signal
There's no separate Google Ads or Meta Ads signal. You tick the channels a signal pulls from. If a channel is listed but you can't tick it, we show why next to it.
- Google Ads adds the website visits from your ads and the keywords behind them, which often tells your rep what the company was looking for.
- Meta Ads adds the website visits from your Facebook and Instagram ads.
Who gets sent
We send a company when all of these are true:
- It's a warm account, or it matches your own rule.
- It has no deal in your CRM. The one exception is a company whose deals were all lost, with the latest loss more than six months ago.
- It matches your ideal customer profile, if you set one.
- This signal hasn't sent it before, unless one of the reasons under Sending a company again applies.
When you set up a signal you pick which companies it draws from. Warm accounts (Recommended) is the list above. Or set your own rule: pick paid engagements, paid clicks or paid video views on LinkedIn, or visits from your Google Ads or Meta ads, and how many in the last 30 days. You can combine up to 3 conditions. Your own rule can also include organic engagement on your LinkedIn company page posts.
LinkedIn reports engagement about two days late, so a daily signal sends a company about two days after it engaged. A weekly one can take up to a week longer.
Ideal customer profile
This is the Who counts as a fit? step in the setup. Pick the industries, company sizes and headquarters countries you actually sell to, and anything outside that never gets sent. If you leave one empty, anything counts. To help you start, we pick them from the companies behind your deals in the last 12 months. Click Clear them to send every warm company if you don't want that. Use Skip companies we have no data on to decide what happens to companies with no industry or country on file.

Sending a company again
Each company is sent once. To be sent again, it needs one of these, and you pick which ones count:
- It starts rising: it was sent as new before, and now it engages more than in the 30 days before.
- It turns up on a new channel: it was warm on LinkedIn before, and now it visits from Google Ads too.
- It comes back after going quiet: it was gone from the list for 30 days or more, and then came back.
Whatever the reason, nothing is sent twice within 30 days.
The first run
At the end of the setup you pick what the first run does. Start fresh from today sends only companies that go warm from now on, so nothing goes out on the first run. Send the backlog first sends the best ones you already have, up to your limit, and each one still only once.
One signal or several?
Start with one signal that covers all your channels. A company that engages with your LinkedIn ads and visits from Google Ads then arrives once, with both channels named, and it goes to the top of the list. Make a second signal only when companies should go to a different team, to a different place, or in a different volume, for example the biggest accounts to your CRM and everything else to a Slack channel.
Each signal keeps its own record of who it has sent, so two signals can each send the same company once.
Where signals can go
A signal can go to your CRM, and to any of these:
- Slack (hooks.slack.com). One message a run, not one per company. How to create a Slack webhook.
- Microsoft Teams (logic.azure.com or powerplatform.com). Use a Power Automate Workflows URL. Microsoft switched off the old Office 365 connector in May 2026, so a webhook.office.com address won't work.
- Clay (api.clay.com). One row per company, ready to enrich.
- Zapier (hooks.zapier.com). One call a run, so it costs one task instead of one per company.
- n8n (your instance). Use the Production URL, not the Test one.
- Make (hook.eu1.make.com or your region).
One signal can send to several places at once, and each CRM you have connected can be picked separately. When you pick a CRM, you also pick what the signal may do there: Add and update companies adds companies that aren't in your CRM yet and updates the ones that are, and Only update companies never adds new ones.

What lands in your CRM
We write six fields on the company record. They sit in their own field group, apart from the fields CRM sync writes:
- Signal type: New or Rising, and empty when a company is warm but neither.
- Signal date: when Fibbler last sent the company.
- Signal name: which signal found it.
- Signal channels: LinkedIn, Google Ads or Meta Ads.
- Signal why: the lines from the note, on one line. A long one gets cut to fit the field, but the note always has all of it. How much fits
- Created by Fibbler: set only on records we created, so you can find and remove them without touching your own.
Before Fibbler 2.0, Signal type said Rising fast. What to change in your CRM
The exact field names for each CRM are on its connect page. If you'd rather create the Salesforce fields yourself, here's how.
The list in your CRM
Each signal also keeps a list, named after the signal. A company keeps its place in it for 30 days, then drops out. The record, the fields and the history stay.
- HubSpot: a static list, under Segments.
- Attio: a list, with an entry per company. You pick its view once. How
- Pipedrive: a saved filter on organizations.
- Salesforce: an Account list view.
- Zoho CRM: a tag on the Account, named after the signal, that you filter Accounts on. The tag comes off 30 days after the Account was last sent. More in Connect Zoho CRM.
- Microsoft Dynamics 365: a static marketing list of accounts, named "Fibbler: " and the signal's name. More in Connect Microsoft Dynamics 365.
The note on the company
Every signal also leaves a note on the company, so whoever opens the record sees why it's there. What it says is the same in every CRM, and Slack, Microsoft Teams and the weekly email use the same lines. Where it goes, and how much of it fits in the Signal why field:
| CRM | Where the note goes | Signal why fits |
|---|---|---|
| HubSpot | A note on the company | 500 characters |
| Attio | A note on the company | 500 characters |
| Microsoft Dynamics 365 | A note on the account | 500 characters |
| Pipedrive | A note on the organization | 255 characters |
| Zoho CRM | A note on the Account | 255 characters |
| Salesforce | A Chatter post on the Account | 255 characters |
It looks like this:
Example Ltd is newly warm on LinkedIn Ads and Google Ads.
Software Development · 201-500 employees · Sweden
LinkedIn Ads: 49 engagements in the last 30 days, up 122% from the 30 days before. Engaged most with EOR Mid-market (31 engagements) and Retargeting Q4 (12 engagements).
Google Ads: 12 website visits in the last 30 days from Non-brand search, after searching "employer of record".
Surfaced by the "Warm accounts" signal in Fibbler.
Which ad sets and campaigns we name
Your rules decide which companies a signal sends. The ad sets and campaigns in the note show what each company did, so we pick them by what it engaged with, not by your rules.
- LinkedIn Ads: up to 3 ad sets the company engaged with in the last 30 days, the one with the most engagements first. If it engaged with none in the last 30 days, we look at the last two full months instead (in November, that's September and October), and the note says "in the two months before", without counts. An ad set that only showed the company your ads, with no engagement, is never named. If we can't tie the engagement to an ad set at all, the note says No ad set identified.
- Google Ads and Meta Ads: up to 2 campaigns with the most website visits from the company in the last 30 days, and for Google Ads up to 2 keywords it searched. A campaign we only know by its ID number is left out of the note.
What a message looks like
You get one message per run, with all the companies in it. For each one you see its name, what we know about it, why it was sent, a link to its LinkedIn page and a link to its record in your CRM.
Automation tools get the whole run as one call, with the companies nested inside it, so a run costs one task instead of one per company. Each company looks like this:
{
"dedupeKey": "example.com",
"dedupeKeyType": "domain",
"changeType": "new",
"company": {
"name": "Example Ltd",
"linkedinUrl": "https://www.linkedin.com/company/example",
"domain": "example.com",
"industry": "Software Development",
"employeeBand": "201-500",
"country": "SE"
},
"signal": {
"type": "new",
"channels": ["linkedin", "google_ads"],
"crmUrl": "https://app.hubspot.com/contacts/1234567/record/0-2/8901234"
},
"evidence": {
"linkedin": {
"engagements": 49,
"impressions": 900,
"clicks": 7,
"trendPct": 122,
"topCampaigns": ["EOR Mid-market", "Retargeting Q4"],
"campaigns": [
{ "name": "EOR Mid-market", "value": 31, "unit": "engagements", "clicks": 5 },
{ "name": "Retargeting Q4", "value": 12, "unit": "engagements", "clicks": null }
]
},
"google": {
"visits": 12,
"topKeywords": ["employer of record"],
"topCampaigns": ["Non-brand search"],
"campaigns": [
{ "name": "Non-brand search", "value": 12, "unit": "visits" }
]
},
"meta": null
}
}campaigns has up to 3 ad sets or campaigns per channel, each with its count, and unit says what the count is. A campaign we only know by its ID number is still in there, as that number, so a workflow can match on it. Clay also gets them as one text column you can filter on.
What was sent, and why
Each signal shows its recent runs: how many companies matched, how many were new and how many were updated, with a note when something went wrong. Below that is every company the signal has ever sent, when it first went out, how many times, and whether we created the CRM record. You can export the whole thing as a spreadsheet.
Pause, edit or delete a signal
Go to Ad signals, open the Signals tab and pick the signal. The buttons are at the top:
- Run now runs it straight away instead of waiting for the schedule. It works once a day, and after a run that went through it says "Already ran today. It runs again on its own schedule."
- Edit opens the setup again, so you can change where it goes, the channels, who counts as a fit, the schedule and the limit.
- Pause stops the signal until you press Resume. Nothing is sent while it's paused.
- Delete removes the signal for good, together with its record of which companies it sent and what each run did. The list it filled in your CRM stays where it is, and nothing new is added to it.
To stop one company without touching the rest, find it in the list of companies the signal has sent and click Stop sending this one. It only applies to that signal. Send this one again undoes it.
Getting too many? Lower Never send more than, switch to Every Monday morning, or narrow down Who counts as a fit?. Owners, admins and managers can change signals. Signals from the old version of Fibbler are linked at the bottom of the Ad signals page.
When a destination refuses a signal
If Slack, Teams, Clay or your automation tool turns a run away, the run shows as failed on the signal's page, and those companies go out on the next run instead. The signal stays on.
- The destination is full, for example a Clay table at its limit. Make room there, and sending starts again by itself.
- The webhook is gone, for example a deleted Slack webhook or Zap, or a Teams workflow that was switched off. We email the workspace owner and admins once. Create a new webhook, click Edit on the signal and paste the new URL.
Schedule and limits
- Every morning runs early each day.
- Every Monday morning runs once a week.
- Never send more than: 10, 25, 50, 100 or 250 companies per run, or your own number, across all the signal's channels. The warmest go first, and the rest go out first on the next run.
- How many signals: 3 on the Growth plan and during the free trial, paused ones included, and as many as you like on Unlimited and Agency. Delete one to make room for a new one.