pagefluxer.
FEWER DISTRACTIONS. KEEP THE EVIDENCE.

Tell PageFluxer which captured changes matter to you.

Add an optional relevance criterion after your ordinary alert rules. For eligible public text and new-item captures, PageFluxer can help distinguish a meaningful update from a matching change you would rather review quietly in history.

Separate consent · Test before enabling · Captured evidence stays available

AN EXAMPLE

Watch a competitor’s plan page

Your criterion
Tell me about plan prices, included limits or plan availability.
Captured change
A footer copyright year changed.
Illustrative assessment
Not relevant to the criterion; an enabled eligible filter can suppress the normal alert.

Illustrative AI assessment, not a live result. AI can be wrong. Observation mode records assessments without filtering alerts.

Keep the criterion specific.

Pricing-page wording

Focus a text monitor on plan terms and limits. Use ordinary numeric price rules when you need a deterministic product-price threshold.

Public notices

Describe the subject you care about and test against retained changes. Keep human review for decisions with material consequences.

New entries

Evaluate the captured entry title, description and URL on supported sources. Linked articles are not fetched to fill in missing detail.

FROM QUESTION TO CAPTURED CONTEXT

A practical way to start.

  1. Choose an eligible monitor

    Start with a working public text or supported new-item monitor. Ordinary rules are evaluated first.

  2. Write and test the criterion

    Give a short, concrete instruction and review a retained change. A manual test does not enable filtering or send a notification.

  3. Enable deliberately

    Where your plan and service settings permit automatic filtering, review the assessment and retained evidence. Keep the criterion current as your goal changes.

FIT IT TO YOUR WATCH LIST

Shared AI Credits, with separate feature access.

Manual relevance testing is available across plans when AI is enabled and consent is given. Automatic relevance evaluation requires Pro or Business; service observation mode may evaluate without suppressing alerts.

Each completed evaluation uses 2 shared AI Credits. Reopening the same cached result with unchanged criteria uses no additional credits. Spending controls and ordinary monitoring limits still apply.

Compare plan allowances →

Common questions

Does this replace my normal alert rule?

No. It is an optional evaluation after a normal rule matches. Your capture and deterministic rule still need to work first.

What happens when AI cannot decide?

An uncertain, failed or unsupported evaluation keeps the ordinary alert path available. It is not treated as a reliable not-relevant result.

Can I still see a filtered change?

Yes. The retained change and available assessment stay in history under normal retention limits. Filtering a notification does not erase the captured event.

Explore a related workflow or the controls behind the capture.

A LITTLE MORE CONTEXT

Put the idea into practice.

All practical guides

Start with one criterion you can verify.

Open an eligible retained change, test your criterion and compare the assessment with the evidence.

Review relevance settings

PAGEFLUXER · LET’S SORT THIS OUT

Something needs your attention