Google Ads Signals

Signals lets you send Google Ads company visit data to external tools via webhooks. Get notified in Slack when a target account clicks your ads, or feed visit data into Clay, Zapier, or custom workflows.

How it works

1. Get the webhook URL from your destination tool (Slack, Clay, Zapier, etc.)
2. Create a signal in Fibbler with your desired configuration
3. Fibbler will send company visit data on your chosen schedule (daily or weekly)

Configuring a signal

Each signal has the following settings:

• Signal Name: A label to identify this signal
• Webhook URL: The HTTPS endpoint from your destination tool
• Destination: The tool you're sending data to (Slack, Clay, Zapier, custom webhook, etc.)
• Include Past Days: How far back to look (7, 30, 60, or 90 days)
• Interval: How often the signal sends: Daily (every night) or Weekly (Sundays)
• Campaigns: Optionally filter to specific Google Ads campaigns (leave empty for all campaigns)

Webhook payload

Each webhook request sends a JSON payload with the following fields:

{
  "domain": "example.com",
  "linkedinUrl": "https://www.linkedin.com/company/example",
  "companyName": "Example Inc.",
  "websiteVisits": 5,
  "campaign": "Brand Campaign",
  "keyword": "b2b analytics",
  "timestamp": "2026-03-08T12:00:00.000Z"
}

Supported destinations

• Slack: Send notifications to a Slack channel
• Clay: Feed company data into Clay tables
• Zapier: Trigger Zapier automations
• Make: Trigger Make (Integromat) scenarios
• n8n: Trigger n8n workflows

Limits

The number of signals you can create depends on your Fibbler subscription plan. Only account Owners and Admins can create and manage signals.