Skip to content
Start free
Menu
TraceLog is waiting for consent

TraceLog is waiting for consent

Last updated Nov 13, 2026

TraceLog's code reported consent as pending or refused, so it captures nothing yet. Either analytics was not accepted in the check's tab, or the consent setup keeps TraceLog from running.

What was observed

TraceLog's code loaded and reported that the visitor has not decided on consent yet, or refused it (unknown or denied). Before consent it creates no identifier, writes no storage entry and sends no request, so nothing arrives.

The row reads two ways:

  • In the check's tab. You have not accepted analytics there yet. Accept, and events start arriving.
  • For real visitors. Your consent setup keeps TraceLog from running even after a visitor accepts. On Shopify, the row comes from the store's customer privacy signal. On WooCommerce, a cookie plugin such as Complianz reaches TraceLog only through the WP Consent API plugin, installed apart.

A visitor who declines is not a fault.

Check that your consent platform allows TraceLog for real visitors; during the check, grant consent first.

What to check

  1. In the check's tab, accept analytics on your own consent banner, or call TraceLog.consent.grant() from the browser console. Events should start arriving.
  2. If they do not start after you accept, check how your consent platform hands the decision to TraceLog: TraceLog has to be in a category the platform allows, and the platform has to call grant on acceptance and again on every page load while consent stands: a grant is not remembered. If your site shows no consent banner, call TraceLog.consent.grant() on every page load.
  3. Confirm the wiring with TraceLog.consent.state(). It returns unknown when neither grant nor deny has been called, which is not the same as denied.

Effect on verification

It reports. TraceLog does not show Conversion path verified for a page that captured nothing.