Getting started
What is Signals
Signals watches your competitors and turns each change into an event you can read, forward or pull.
Add a competitor → Signals watches it → you get an event when something changes.
Signals checks the places where competitors show up and tells you what is new. It does not show you a dashboard of everything. It shows you what changed.
What it watches
- Ads
- New ads on Google, Meta and LinkedIn
- Reviews
- New reviews on G2, Trustpilot, Capterra and BOXIL
- Posts
- LinkedIn, X and Instagram posts
- News
- New articles that name the competitor
- Website
- Changes to pages you pick, such as pricing
- Job postings
- New, changed and closed jobs on the careers page and job boards
- Mentions
- LinkedIn and Reddit posts by others about the competitor
- LinkedIn engagement
- People who react to or comment on the company's newest posts
- New competitors
- New companies that appear in your market
How a change reaches you
Check
A tracker looks at one source on a schedule (hourly, daily or weekly).
Compare
Signals compares the result with what it saw last time. The first check saves a starting point. Three exceptions: Ads reports the ads that are running at the first check, Job postings reports every open job, and LinkedIn engagement lists people from its first check.
Judge
For news, LinkedIn and X posts, mentions and website changes, Signals scores whether the change matters to you. Ads, job postings, reviews, Instagram posts, LinkedIn engagement and new competitors are delivered as published.
Event
Each change that counts becomes one signal (an event).
Deliver
The event goes to the Feed, Slack, email, your webhooks and the pull API.
| Where | What you get | Set up |
|---|---|---|
| Feed | Every signal, with filters and CSV export | Nothing to set up |
| Slack | One message per competitor and source, in one channel per project | Slack |
| A daily signals email and a weekly summary | Settings and emails | |
| Webhooks | One signed POST per tracker run to your own URL, with the events 100 per page from the API | Set up a webhook |
| Pull API | The same events, read with an API key | Pull API and keys |
The Signals feed
Who it is for
- GTM engineers wire events into Clay, Zapier, n8n or their own code through webhooks and the pull API.
- Product marketers read the Feed, get Slack messages and open signals to see why they matter.
Signals reports changes from now on
It never loads past history. The first check of each source saves a starting point (Ads also reports the ads running today and Job postings every open job; LinkedIn engagement lists people from the first check).