Filters and options
Record supported clicks, dropdown choices and checkbox changes to make a useful view repeatable.
Some pages only show the useful content after a click or a filter selection. Record supported interactions, review the steps and test the prepared state before PageFluxer starts scheduled captures.
Tested page preparation · Supported Cloud Browser and Local workflows
Illustrative workflow. Recording acts on the real website; use public, non-sensitive steps.
Record supported clicks, dropdown choices and checkbox changes to make a useful view repeatable.
Use supported non-sensitive text entry for a public search or list filter, then confirm the resulting page state.
Prepare a stable Cloud Browser view before a screenshot capture. Test loading and noise controls along with the recorded steps.
Start recording through the extension and perform only the supported interactions needed to reach your target.
For Cloud Browser, adjust supported steps on PageFluxer and test Cloud replay. For Local, test its supported subset in a fresh Chrome tab.
Select the content or visual region after preparation. Verify the preview, rule and quiet baseline before saving.
Cloud preparation runs with Cloud Browser and uses one Browser check per attempt, rather than one per step. Free uses its one-time Browser trial; paid plans provide ongoing Browser allowances.
Step limits are 5 / 10 / 20 / 20 on Free / Starter / Pro / Business. Local preparation follows Local allowances and supported actions. A Cloud site connection is separate from your Chrome login.
Compare plan allowances →No. Do not record passwords or other credentials. Supported authenticated Cloud pages require a separately configured workspace site connection; Local uses the existing Chrome session without exporting it.
A failed replay becomes a capture issue and preserves the last successful baseline. Review and retest the steps before relying on later captures.
Not always. Local supports a subset of preparation actions, and the two environments can see different page states. Test using the method that will run the monitor.
Explore a related workflow or the controls behind the capture.
Confirm the capture where your monitor will run, then choose the settings that match your goal.