Skip to content
Start free
Menu
TraceLog is waiting for consent

TraceLog is waiting for consent

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

What was observed

TraceLog's code loaded and reported consent as 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 your test 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.

A visitor who declines is not a fault.

Grant consent for this test, or check that your consent platform allows TraceLog for real visitors.

What to check

  1. In the test 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, not only on 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 mark an install verified from a page that captured nothing.