Quickstart

This guide takes you from zero to a verified Tiny Analytics install using the same workflow the app promotes: create a source, install Tiny once, verify live events, then inspect sessions and events.

Create a source

Open Analytics > Setup and click Create source.

When you create the source:

• Give it a stable name and slug.
• Add every browser origin where the app will run.
• Keep the public key private to the install snippet and source settings screen.
• Copy the generated install code from the tab that matches your app: Browser, Next.js, or React.

Tiny creates the public key, source-specific install examples, and debug link for you.

Install Tiny

Install Tiny once in your app shell or top-level bootstrap.

<script>
  window.tinyAnalytics = window.tinyAnalytics || function () {
    ;(window.tinyAnalytics.q = window.tinyAnalytics.q || []).push(arguments)
  }
</script>
<script src="https://your-tiny-api/sdk.js" async></script>
<script>
  tinyAnalytics("init", {
    publicKey: "pk_your_source_key",
    apiBaseUrl: "https://your-tiny-api",
    autoPageviews: true
  })
</script>

Verify live events

Open Analytics > Setup > Debug, load the app from an allowed origin, and refresh the page.

What you should expect:

• A successful bootstrap request appears first.
• A page event follows if autoPageviews is enabled.
• The debug view eventually shows Installation verified after accepted event traffic.
• If Tiny says Snippet connected, waiting for first event, the snippet is loaded but Tiny is still waiting for a pageview or track() call.

If the request is rejected, the debug view shows the origin verdict, rejection reason, raw payload, and normalized payload.

Inspect sessions and events

Once setup is verified, open Analytics > Sessions & events.

That screen gives you:

• high-level counts for event rows, sessions, pageviews, and track events
• filters for source, event type, event name, path, and date range
• an events explorer with expandable event payloads
• a recent sessions table with visitor, browser, device, and landing path data

Use Debug to confirm the install. Use Sessions & events to understand traffic.

Next steps

• Read Install Tiny for placement details and allowed-origin guidance.
• Use Verify live events to understand debug verdicts.
• Review the Browser SDK and Tracking API if you need to instrument more events.
• Keep Troubleshooting handy for 403s, duplicate installs, and key rotation issues.