Troubleshooting

Most Tiny Analytics setup issues fall into a small set of predictable categories: the snippet is not running, the origin is not allowed, the install is duplicated, or a rotated source key no longer matches the running code.

No events yet

If the debug screen never shows a request:

  • make sure Tiny is installed in a shared layout or bootstrap file
  • verify the browser can load https://your-tiny-api/sdk.js
  • confirm the page actually executes tinyAnalytics("init", ...) or initTinyAnalytics(...)
  • leave autoPageviews enabled during first-time verification

If bootstrap succeeds but no page event appears, refresh the page or trigger a real track() call from a user interaction.

403 errors

Tiny returns 403 for a few important protection checks:

  • Name
    tracking_source_origin_not_allowed
    Description

    The request reached Tiny, but the browser origin is not listed in the source's allowed origins.

  • Name
    tracking_source_inactive
    Description

    The source exists but is inactive.

  • Name
    invalid_session_for_source
    Description

    The supplied sessionId belongs to a different source or is otherwise not valid for the current source.

The most common cause is allowed-origin mismatch between localhost, 127.0.0.1, staging, or LAN preview URLs.

Duplicate installs

Duplicate pageviews usually mean Tiny was initialized more than once.

Check for:

  • the browser queue snippet being included twice
  • multiple initTinyAnalytics() calls in different components
  • Tiny being mounted in both a page shell and a nested component tree

The fix is usually simple: move Tiny to the earliest shared layout or bootstrap file and keep a single initialization path.

Key rotation and session mismatches

Regenerating a source key immediately invalidates older installs that still use the previous public key.

After key rotation:

  • update the running install with the new generated snippet
  • reload the tracked app
  • let Tiny bootstrap a new session for that source

If you see invalid_session_for_source, treat it as a hint that the current source and current session no longer line up.

Useful checks

When you get stuck, work through these in order:

  1. Open Analytics > Setup > Debug.
  2. Compare the running install with the generated snippet in Analytics > Setup.
  3. Check the origin verdict on the latest attempt.
  4. Inspect the raw and normalized payloads.
  5. Confirm the source is active and using the expected public key.
  6. Use Copy install brief if someone else needs to place the install for you.

Was this page helpful?