Test Website Change Alert Rules
Test price, text, availability and new-item rules with before and after examples. Understand threshold crossings and combined conditions before relying on an alert.
Open PageFluxer →Try a rule before waiting for a change
Open a monitor and expand “Would this trigger an alert?”. The tester is also available after a Cloud setup preview. Enter before and after examples for every target, then choose Test these examples. Your configured rules are used. Nothing is saved, no page is fetched, and no notification is sent.
For a CAD price threshold of 100, try 120 → 95. The below-price rule matches. Now try 95 → 90: it does not match, because the price was already below your threshold. A Price drops rule would match both decreases. A price exactly equal to the threshold is not below it.
Test all supported target rules
Price examples use the target’s currency and decimal format. Thresholds use a dot. Text rules compare normalized text and match the configured literal phrase without case sensitivity. Contains and not-contains trigger when their condition changes from false to true. Any change compares normalized values; whitespace-only differences may be ignored.
For availability, enter the visible stock wording rather than a true/false value. The configured available and unavailable phrases determine the result. Ambiguous or unknown stock wording needs correction. For new items, enter one URL per line and optionally append | item title. The tester compares new URLs and phrase matches; rearranging existing entries does not make them new. Add any earlier URLs to Previously seen URLs to simulate the monitor’s longer-lived item memory. A returning item is not newly discovered.
Understand Any rule, All conditions and baselines
Any rule lets each target trigger independently. All conditions supports price below, availability, and text phrase conditions: the combined result must move from false to true in one capture. One condition can remain true while another becomes true. Remaining true does not trigger repeatedly.
Select Test the first capture to see baseline behavior. A first successful capture establishes the starting state and does not create a change alert. The tester uses the same extraction and rule semantics as monitoring, but examples do not validate a selector, product identity, page access or automatic list extraction.
Confirm the delivery path separately
A matching rule is only one part of a working alert. Check the monitor’s delivery settings, snooze, email schedule, plan allowances and any AI relevance filter. Use a delivery test for the channel and the controlled practice workflow for an end-to-end check.
Existing Local monitors can use this dashboard tester without an extension update. The examples never change the extension’s rules or its capture baseline.