Competitor Pricing Page Change Monitor
Pricing
Pay per usage
Competitor Pricing Page Change Monitor
Monitor public pricing pages and emit structured price, plan, copy, and change signals for competitor intelligence and sales/product teams.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Stephen Coulson
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
What does Competitor Pricing Page Change Monitor do?
Competitor Pricing Page Change Monitor watches public pricing pages and turns them into structured pricing intelligence. Give it a list of URLs and it records price mentions, plan-language, page hashes, and whether each page is new, unchanged, changed, or errored compared with the previous run.
Use it for competitor intelligence, product marketing, sales enablement, investor monitoring, and pricing research. Schedule it daily or weekly on Apify and export the dataset to CSV, Excel, JSON, Google Sheets, Zapier, Make, or your CRM.
Why use it?
Pricing pages change when companies test packaging, increase prices, introduce enterprise tiers, remove free plans, or shift go-to-market strategy. Most teams notice these changes late. This Actor gives you a simple recurring monitor for public pricing pages.
Input
{"pages": [{ "name": "Slack", "url": "https://slack.com/pricing", "category": "team_software" },{ "name": "Notion", "url": "https://www.notion.com/pricing", "category": "productivity" }],"keywords": ["free", "pro", "business", "enterprise", "monthly", "annual", "seat", "user", "contact sales"],"enableDelta": true,"persistSnapshot": true}
Output
The Actor outputs one row per monitored page, including:
- page name and URL
- fetch status
- page title and meta description
- content hash and previous hash
change_status:new,unchanged,changed, orerror- detected price mentions
- added and removed price mentions
- tracked pricing terms
- timestamp
Notes
This Actor uses public web pages only. It does not log in, use cookies, or scrape private/authenticated data. Dynamic pricing pages that require client-side rendering may produce limited text; for those, use the page's public static pricing URL where possible.