Trackers

Website pages tracker

Get a signal when a competitor changes a page you watch, such as pricing or integrations.

Add the pages to watch → get notified when they change.

What it watches: Changes to specific pages on the competitor's site
What you add: Page URLs, one per line, up to 100. Optionally, what to watch for
How often: Weekly only
Cost: 1 credit per page per check
Events: website.changed · website_change
Relevance: AI-scored. Signals include a summary of what changed

Set it up

Add the competitor

Go to Feed or Trackers and click Add competitor. Enter the website, for example pipedrive.com, and click Continue.

Tick Website pages

On What should we watch at …?, tick Website pages. Signals may guess a page for you. Check it, the row says our guess, check it.

Add the pages

In Pages, write one URL per line, like competitor.com/pricing. You can add up to 100. In the edit sheet, use Paste a page URL and Add page, and Remove under Selected pages.

Say what to watch for (optional)

In What to watch for, describe what matters, like Pricing changes or new integrations. Signals uses it to judge each change. Click an example chip to fill it in.

Start

Weekly is the only cadence. Click Start tracking.

Website pages row in the add competitor flow — The Website pages row for Pipedrive.

Edit Website pages for HubSpot — The edit sheet: selected pages and What to watch for.

What you get

The first check saves each page as a starting point. Each week, Signals compares every page with its last version. A page that changed becomes one signal. Pages that did not change send nothing.

A website change signal — A sample website change signal for HubSpot: Before and After, Why it matters, High confidence.

In the signal you see:

the changed page and a short title for the change
Before and After text
Why it matters and a confidence level
Open page to see the live page

In your webhook

Each change is one event with eventType: "website". websiteResponse.changes lists what changed, with the text before and after. The full key list is on Website change events. A webhook gets one POST per check (a run webhook) and reads these events from its pages.

json

1{
2  "eventType": "website",
3  "subEventType": "website_change",
4  "action": "updated",
5  "signalType": "website.changed",
6  "competitor": { "name": "HubSpot", "domain": "hubspot.com" },
7  "relevance": {
8    "status": "relevant",
9    "confidence": 1,
10    "shortSummary": "Breeze AI Credits Added"
11  },
12  "websiteResponse": {
13    "pageUrl": "https://www.hubspot.com/pricing",
14    "changes": [
15      {
16        "type": "major",
17        "title": "Breeze AI Credits Added",
18        "description": "Added HubSpot Credits for Breeze AI agents to the Professional plan feature list.",
19        "categories": ["feature_update", "pricing_strategy"]
20      }
21    ]
22  }
23}

Website change events

Every key and type, with a sample body.

All trackers

Compare cadence and cost.