How to Setup Price Monitoring?

Price monitoring automatically tracks product or service prices on any web page and alerts you the moment the number changes — no coding required. This guide shows you exactly how to set up price monitoring in MonitoringDaddy using the built-in keyword and content-check function.

What Is Price Monitoring?

Price monitoring is the automated process of watching a specific URL for a known price string and triggering an alert whenever that string disappears or changes. Instead of manually revisiting a competitor's product page or a supplier's catalogue every day, a monitor checks the page for you on a chosen schedule — every 15 minutes, every hour, or once a day — and notifies you instantly when the price moves.

In MonitoringDaddy, price monitoring is built on top of the same keyword monitoring engine used for content checks. You supply the expected price text (for example, $199.99), set the trigger to URL does NOT contain, and the platform fires an alert as soon as that text is no longer found in the page response — meaning the price has changed.

Why Price Monitoring Matters

Price is one of the most volatile elements on any e-commerce or SaaS page. Even a small shift can affect your margins, conversion rates, or competitive positioning. Automated price monitoring removes the manual effort and gives you a real-time edge in several ways:

• Competitor repricing: Know the moment a rival drops or raises their price so you can respond immediately.
• Flash sale detection: Catch time-limited discounts on products you buy or resell before they expire.
• Price-drop alerts: Get notified when a supplier reduces cost so you can update your own pricing or pass savings to customers.
• Stock and price updates on marketplaces: Track third-party sellers on marketplaces where prices fluctuate frequently throughout the day.
• Price rollback verification: Confirm that a promotional price has reverted to standard after a campaign ends.
• Internal QA: Verify that your own product pages always display the correct price after a CMS or deployment change.

How Price Monitoring Works in MonitoringDaddy

MonitoringDaddy fetches the raw HTML of a target URL at your chosen interval, then scans the response body for the price text you specified. The logic is straightforward:

1. The crawler makes an HTTP GET request to the product page with the cache buster enabled so it never reads a stale cached copy.
2. It searches the response body for the exact string you entered (for example, $199.99).
3. If the string is found and you chose URL does NOT contain, the monitor stays green — the price has not changed.
4. If the string is absent, the monitor fires an alert to all configured channels.

This is identical in principle to keyword monitoring. The difference is intent: instead of verifying that a content word is present, you are verifying that a precise price value is still present.

Before You Begin

• Open the target product page in your browser and use View Page Source (not the inspector) to confirm the price string appears in the raw HTML — not injected by JavaScript.
• Note the exact format including currency symbol, thousands separator, and decimal: $1,299.00 is different from $1299.
• Decide the check frequency: high-volatility pages (flash sales, live auctions) warrant a 15-minute interval; stable B2B pricing can be checked daily.
• Have at least one alert channel ready — an email address or a webhook URL for Slack, Discord, or another tool.
• Check the site's robots.txt and terms of service to confirm automated requests are permitted.

Step-by-Step Price Monitoring Setup

Step 1: Name Your Monitor

Choose a name that clearly identifies the product and site so you can recognise it at a glance in your dashboard.

Step 2: Enter the Product Page URL

Paste the full URL of the page where the price appears, including the https:// protocol and any product-specific path.

Step 3: Choose a Monitoring Interval

Select how often MonitoringDaddy should check the page:

• 15 minutes — fast-moving prices, flash sales, live auction pages
• 1 hour — standard e-commerce product pages updated throughout the day
• Daily — slow-moving B2B or wholesale catalogues

Step 4: Set the Alert Condition

From the alert condition dropdown, select:

This activates the text-lookup engine and exposes the keyword field where you will enter your price string.

Step 5: Enter the Price String

Type the exact price text that currently appears on the page. Copy it directly from the page source to avoid any spacing or encoding differences.

Other valid examples:

Step 6: Choose Contains or Does Not Contain

This setting controls when the alert fires:

• URL contains keyword — alert fires when that price appears (useful for waiting for a target price to be reached)
• URL does NOT contain keyword — alert fires when that price disappears (most common — detects any price change)

Step 7: SSL and Domain Monitoring

For a pure price monitor, set both SSL monitoring and domain monitoring to OFF. These are separate concerns — you only need them if you want combined expiry alerts on the same check.

Step 8: Add Alert Channels

Add at least one channel so you receive notifications immediately when a price change is detected:

• Email alerts — simple to configure and reliable
• Webhook alerts — forward alerts to Slack, Discord, Microsoft Teams, or any custom endpoint

Step 9: Request Method

Leave the request method set to GET. This is the correct method for fetching a standard HTML product page.

Step 10: Enable the Cache Buster

Set the cache buster to enabled. This appends a unique parameter to every request so the server always returns a fresh response — critical for price monitoring where you must never read a stale cached value.

Recommended Price Monitoring Configuration

Best Practices for Accurate Price Monitoring

Target a Stable Price Element

Some pages show the price in multiple places (hero section, add-to-cart widget, structured data). Use View Page Source to find the most stable occurrence — ideally inside a consistent HTML element like a <span> with a fixed class. Copy the price exactly as it appears in the source, not as rendered by the browser.

Match the Exact Format

Currency symbol position, space between symbol and number, thousands separators, and decimal notation all vary by locale. $1,299.00, $ 1299, and USD 1,299 are three different strings. An incorrect format means the keyword is never matched and alerts never fire.

Anti-Bot and Rate-Limit Considerations

Some e-commerce sites use bot-detection middleware (Cloudflare, PerimeterX, Akamai Bot Manager) that may block automated requests or serve a challenge page instead of the product HTML. If your monitor consistently shows the keyword as missing even though the price has not changed, the page may be blocking the crawler. In that case, check whether the site exposes a public REST API or a JSON-LD structured data block that includes the price — these are often less protected.

Check Frequency vs. Server Load

Avoid setting an unnecessarily short interval on sites where prices change only a few times a day. A 1-hour or 6-hour interval is usually more than sufficient for standard retail pages and reduces the load on the target server.

Update the Keyword After Each Change

Once a price change alert fires and you have confirmed the new price, update the keyword in your monitor to the new value. If you leave the old price string in place, the monitor will continue alerting on every subsequent check because the old text is still absent.

Limitations

• JavaScript-rendered prices: If the price is injected by a front-end framework (React, Vue, Angular) after the initial HTML is served, it will not appear in the raw response and the text lookup will fail. Use REST API monitoring against a backend endpoint instead.
• Dynamic price formats: Pages that display prices with live currency conversion or personalised discounts may show a different value on each request, causing false alerts.
• Bot-protection pages: Sites that serve a CAPTCHA or access-denied page to automated crawlers will prevent the monitor from reading the real price.
• Login-gated prices: Pages that require authentication before displaying a price are not accessible to an unauthenticated HTTP GET request. Consider whether the site provides a logged-in API endpoint.
• Complex price layouts: Pages that display price ranges, bundles, or multi-variant pricing may need a more specific substring to target the correct value.

Troubleshooting

Alert fires immediately after setup even though price has not changed

The keyword does not match what appears in the raw HTML. Open the page source and copy the exact price string, including the currency symbol and every character. Check for non-breaking spaces ( ) between the symbol and number, or for HTML entities encoding the currency symbol.

No alerts when the price clearly changed

Verify the monitor is in an active state. Also confirm the cache buster is enabled — if it is disabled, the server may be returning a cached response that still contains the old price. Finally, check that the page is not behind a bot-protection layer that serves a different HTML to the crawler.

Repeated alerts every check cycle

The price has changed and the old keyword is no longer on the page. Acknowledge the alert, visit the page, confirm the new price, and update the keyword field in your monitor settings to the new price string.

Next Steps

Once your price monitor is running, consider pairing it with a keyword monitor on the same URL to also watch for "Out of Stock" or "Discontinued" text. For sites that expose pricing through an API, REST API monitoring lets you parse structured JSON responses for precise value comparisons. Review the full list of monitor types and plan limits on the pricing page.

Frequently Asked Questions