Competitor Pricing & Offer Change Monitor — Price Diffs

Watch pricing and offer pages and get told only what changed: prices added or removed, monthly/annual prices, calls to action and product schema. The first run saves a baseline; later runs report the diff, so a schedule turns it into a change feed. Built by PAOE.

Each item is processed individually and charged as its own event, so you pay only for what the run actually delivers. Results are written to the run's dataset as one JSON object per item, ready to download as JSON, CSV or Excel, or to pull through the Apify API.

What it checks

For each page: the prices shown, any monthly or annual (period) prices, the calls to action present, the page title and whether the page carries product structured data. A first run saves a baseline; later runs report only what actually changed against it.

Pricing

Event	What it covers	Price
page-checked	page checked (primary)	$0.01 per event
change-detected	change detected	$0.08 per event

Volume tiers reduce the price automatically on higher Apify plans: Bronze 15% off, Silver 25% off and Gold or above 40% off the listed free-tier price. The charge is per item processed, not per run.

Input

Field	Type	Required	Default	Description
urls	array	yes	["https://example.com/pricing"]	Pages to snapshot and watch for changes.
previous	object	no	—	Advanced: supply prior snapshots to diff against instead of the stored baseline.

Example input:

{
  "urls": [
    "https://example.com/pricing"
  ]
}

Output

One JSON object per item in the run's dataset. Every result carries the input it came from plus the fields this Actor measures, so the output can be joined back to your own data without guessing which row is which. The final dataset entry is a summary object with the run's totals.

Typical use cases

• Track what competitors charge and when they change it.
• Feed pricing changes into alerts, dashboards or spreadsheets.
• Keep a dated record of competitor offers for later comparison.

Limitations

A first sighting is reported as first_seen and charged the page-checked event only, never the change-detected event. The change event is charged once per page that genuinely moved against a previous snapshot; the number of changes is reported as data, not used as a multiplier, so a busy page cannot inflate the bill. The baseline lives in the Actor's key-value store, and you can pass previous explicitly instead.

Am I charged for a run with no baseline yet?

Every limitation above is reported per item in a findings entry with a level of fail, warn, info or ok, a machine-readable code and a concrete action. If something cannot be checked it is reported as such rather than assumed to be fine.

Can it run on a schedule?

Yes. Save a task from this Actor with your inputs, then set a schedule on the task. Scheduled runs recur with the same inputs, which is the intended way to use it for ongoing monitoring.

What if the page is JavaScript-rendered?

Prices and calls to action embedded in the served HTML are detected. Values that only appear after client-side JavaScript runs are not visible to this Actor, and that shows up as an empty prices list rather than a false change.

Notes

If a site returns something unexpected, open an issue on the Actor's page with the URL and the input used, and it will be looked at.

Related Actors

• AI Agent Readiness Audit

Keywords

competitor pricing, price monitoring, price change alerts, competitor tracking, ecommerce, price scraping, pricing intelligence.