Verify live events

The debug view is where Tiny proves the install is real. It shows what Tiny received, what it normalized, whether the origin was allowed, and why a request was accepted, duplicated, or rejected.

Open debug view

Open Analytics > Setup > Debug, choose the source you want to inspect, then load the tracked app from one of that source's allowed origins.

The debug screen refreshes automatically and gives you:

  • the public key and allowed origins for the selected source
  • the last accepted event time
  • the generated browser snippet for quick re-checks
  • recent bootstrap and event attempts
  • raw payloads, normalized payloads, and per-event results

Read the verdict

Tiny summarizes the recent traffic for the selected source with a verification verdict.

  • Name
    Installation verified
    Description

    Tiny accepted recent event traffic for this source. Expand the latest attempt to inspect payloads and per-event outcomes.

  • Name
    Snippet connected, waiting for first event
    Description

    Bootstrap is succeeding, so the public key and origin look valid. Tiny is still waiting for a pageview or a real track() call.

  • Name
    Requests are being rejected
    Description

    Tiny is receiving traffic but refusing it. Check the origin verdict, the rejection reason, and the normalized payload for the latest attempt.

  • Name
    Waiting for first request
    Description

    Tiny has not seen a bootstrap or events request for this source yet.

Inspect payloads

Expand an attempt when you need to answer any of these questions:

  • Did the request come from an allowed origin?
  • Did it hit the source you expected?
  • Was the payload well-formed?
  • Did Tiny accept, reject, or dedupe the event?

The debug page shows:

  • raw payload exactly as Tiny received it
  • normalized payload after validation and normalization
  • request kind (bootstrap or events)
  • SDK version, ingest version, and HTTP status
  • per-event result rows with event name, event type, status, and rejection code

identify(userId) only affects future events. If you identify a user after the first pageview, older events remain anonymous.

Common verification wins

These are the fastest ways to close the loop:

  • If bootstrap succeeds but events do not appear, refresh the page and let autoPageviews fire.
  • If the request is rejected, compare the source's allowed origins with the exact browser origin in the attempt record.
  • If Tiny says the session does not belong to the source, reload the page and let the source bootstrap a fresh session.
  • If the install looks right but nothing arrives, compare the live snippet against the generated snippet in Analytics > Setup.

Was this page helpful?