Monitor only
Monitor only is the When to ask for approval: Never — monitor only setting on a product. Every checkout is checked and recorded, but nothing pauses. New products start this way.
What happens
- Checks are recorded. Each use of the protected step creates a check, which appears under Checks and Agent detections in the portal. A check that would have paused shows as “Would have paused”.
- No purchases pause. Every check returns
continue, so no review is created and no quote or mobile number is sent. - Nothing is held. The embed loads the product’s setting when
protectis called, before anyone presses. In monitor only it doesn’t hold the press at all: your own handlers run immediately, as if the step weren’t protected, and the check is sent in the background. The check is delivered even if the page navigates away immediately. onResultis called afterwards, withmonitored: true:continueonce the check returns, orfail_openwith a reason if it fails. See Handling the outcome.
Use it to measure before you switch on approval
Add the embed with the product on monitor only
Add the embed as you would for approval. Nothing changes for your customers.
Watch your agent traffic
Review Agent detections in the portal over a representative period. Include runs with the AI agents you expect your customers to use, and check they show as “Would have paused”.
Turn on approval
Set When to ask for approval to Only when an agent is detected and publish. See Approval methods.
A new setting applies when a page next loads, and can take up to two minutes to reach every page. Until then, a page still on monitor only doesn’t pause. If a check then asks for a review, there’s no pause (the step has already proceeded), onResult receives fail_open, and the next press waits for its check. Allow two minutes after publishing before relying on a setting that pauses.
Related
- Agent detection: what’s checked, and using your own signal.
- Test and go live: show the pause panel for testing with Every purchase.