Consent

Nothing loads before consent. Until the visitor has agreed, Pixelonce does not load the pixel, set cookies or send a server copy.

Where consent is read from

Pixelonce reads the visitor's choice from whichever of these the site uses:

  • the WP Consent API
  • the IAB TCF API
  • Cookiebot, Complianz, CookieYes and Borlabs Cookie

Consent plugins active on the site are detected in WordPress, so the runtime waits for an answer even if the consent tool's script loads after Pixelonce's. The stepcount_consent_tools filter can add others.

For a consent tool Pixelonce does not read itself, tell it the visitor's choice from your own code with StepCount.consent({ marketing: true }). The plugin's JavaScript API and filters keep their original name, StepCount / stepcount_.

Modes

ModeBehaviour
auto (default)Follow the consent tool if the page has one; send if it has none.
requireNever send without an explicit grant, even with no consent tool on the page.
offIgnore consent tools — for sites outside consent rules, or handling consent another way.

Events before the visitor decides

With queue on (the default), events that happen before the visitor answers are held and sent if they grant consent, and dropped if they refuse. The fire-once decision is still made at the moment the event happened, so queued events never double up.

Google Consent Mode

If your site uses Google tags and your consent tool does not set Google Consent Mode v2 itself, Pixelonce can set the defaults and updates for you.

Global Privacy Control

When a visitor's browser sends Global Privacy Control (a browser-level “do not sell or share my data”), Pixelonce treats it as an opt-out of ad tracking: marketing consent is not granted, whatever a consent tool reports. Only an explicit StepCount.consent() call from your own site overrides it. This is on by default and can be switched off in the consent settings.