CentralCSP
Reporting APIReport types

Intervention

The intervention report fires when the browser refuses something the page asked for, to protect the user or performance.

Last update:

An intervention report tells you the browser declined to do something the page requested because it would harm the user experience, performance, or battery. A common example is blocking a navigator.vibrate() call made before the user interacted with the page. The report names what was intervened on and where in the code it came from.

Experimental

Intervention reporting is a draft, implemented mainly in Chromium. Behavior and the set of interventions can change.

When the browser sends it

When the browser applies an intervention, refusing an action the page asked for in the user's interest (blocking vibration without a gesture, throttling a heavy operation). Autoplay blocking, by contrast, does not generate an intervention report in current Chromium. It is delivered to the default reporting endpoint and is also observable in the page through ReportingObserver.

Payload example

{
  "type": "intervention",
  "age": 18,
  "url": "https://example.com/",
  "user_agent": "Mozilla/5.0 ...",
  "body": {
    "id": "NavigatorVibrate",
    "message": "Blocked call to navigator.vibrate because user hasn't tapped on the frame or any embedded frame yet: https://www.chromestatus.com/feature/5644273861001216.",
    "sourceFile": "https://example.com/feedback.js",
    "lineNumber": 1234,
    "columnNumber": 42
  }
}

Every intervention report body carries these fields inside the shared report envelope.

Field reference

FieldMeaning
idA machine-readable identifier for the intervention, the stable key to group by.
messageA human-readable description of what was refused and why.
sourceFileThe file that triggered the intervention.
lineNumber / columnNumberThe location in that file.

How to receive it

Declare a default endpoint in Reporting-Endpoints; interventions have no per-policy directive. CentralCSP collects them with the rest of the report stream.

What it tells you about security

Interventions are mostly user-experience and performance signals rather than direct security findings. They are still worth watching: a surge of interventions from a script you did not write can be the first sign of unexpected or abusive third-party behavior on the page.

Gotchas

The id is the stable key to track an intervention; the message wording can change between browser versions, so group by id, not by text.

Browser support

Chromium-based browsers only; experimental. Other engines do not emit intervention reports.

See also

Sources

On this page