Skip to content

[00] Subset Opt-Out, User guide

Perfmatters

Last updated

How Subset Opt-Out keeps its scripts out of Perfmatters' Delay JavaScript and Defer JavaScript, what to check after setup, and the limits.

Subset Opt-Out works with Perfmatters’ JavaScript settings, with no exclusions for you to add. It keeps its own scripts out of delay and deferral, so they still run first and in order.

What works

Subset Opt-Out relies on two inline scripts in <head> and one script file. They have to run unchanged, in order, before any tracker. On Perfmatters’ JavaScript settings, it adds them to the exclusions for:

The exclusions match the script file’s folder and the ids of the inline scripts.

Held trackers are printed as type="text/plain", which the browser doesn’t run. Subset Opt-Out turns them back into scripts, in order, once the visitor’s choice allows them.

What needs a setting

Nothing in Perfmatters. If you use a page cache alongside it, clear that cache after you install Subset Opt-Out, and again after you switch a service on or off or add a custom rule.

Then test a page as an opted-out visitor, or with Global Privacy Control turned on in your browser. Global Privacy Control shows how to check what’s held.

Known limits

  • A tracker no service matches isn’t held. Perfmatters delays or defers it like any other script, and it runs for everyone. Add a custom rule under Subset → Opt-Out for it.
  • Scripts above wp_head run first. A tracker printed before wp_head(), or moved above it, runs before Subset Opt-Out can hold it.
  • Your own exclusions stay. What you’ve entered under Excluded from Delay or Exclude from Deferral is kept.