PRODUCT ANALYTICS · GETTING STARTED

One command.
Real analytics.

tigr tells you what your users actually do. You install it in one line, then an AI skill reads your code and writes the tracking for you. No dashboards to wire, no event names to invent.

installnpm install tigr-reactVue · React · React Native · plain HTML
Free the moment you install, zero code:
  • pageview
  • session_start
  • rage_click
  • scroll_depth
  • error
  • page_leave
Watch it run
THE SKILL, LIVE

Watch a skill
instrument your app.

You point a skill at a page. It walks the whole file tree, decides which actions actually deserve an event, and writes the calls into the right files. This is a real run, so pick your stack and press play.

app/checkout/page.tsx
1 Traverse2 Propose3 Write
/tigr-react app/checkout/page.tsx

Press Run skill to watch it work →

Every event ships with human-readable props, never a bare id, so the dashboard reads like a sentence, not a lookup table. See the full event reference

WHY TRACK EVENTS

Data you never read
is data you don't have.

  • 01

    You're sitting on a goldmine.

    Every tap, submit and drop-off is a signal about what your product is really doing. Most teams collect all of it and read none of it.

  • 02

    Problems show up late.

    By the time a number looks bad, the users already churned. Events catch the drop the day it starts, not the month you finally notice.

  • 03

    Guessing is expensive.

    Shipped a new flow? Without events you are guessing whether it worked. With them, you know exactly where people fall off.

  • 04

    It's the fuel for the AI.

    tigr turns the raw stream into a plain-language briefing. No events, nothing to explain. The better you track, the sharper the insight.

Raw events
checkout_started  { plan: "pro", total: 49 }
cart_item_removed { product_name: "Annual" }
page_leave        { path: "/checkout" }
checkout_started  { plan: "pro", total: 49 }
page_leave        { path: "/checkout" }
What tigr says

“Checkout got more traffic this week, but nobody finished. Every session that dropped did it on the same step, right after an item was removed, and mostly on the pro plan.”

plain-language digest · no charts to decode
THE SKILLS

One per stack.
Point, run, review.

Each skill is a markdown file you drop into Claude Code, Cursor, or any agent that reads skills. It knows what tigr captures automatically, so it never double-tracks, and it always shows you the plan before it writes a line.

  • React / Next.js

    Walks the component tree, stores, hooks and mutations, then writes the events where the handlers actually live.

    Read skill
  • Vue / Nuxt

    Resolves auto-imported components to their files, follows composables, and keeps SSR safe while it instruments.

    Read skill
  • React Native

    Depth-first through screens and zustand stores, and wires the one navigator listener that gives you screen views.

    Read skill
  • Plain JS / HTML

    No build step, no components. Follows every linked script to the real handlers and instruments through window.tigr.

    Read skill
START HERE IF YOU HAVE NOTHING

The setup agent

Not sure which SDK you need? Hand your agent the setup file instead. It detects your stack, wires the API key into the right env file with the right prefix, installs the SDK, and initializes it once, then hands off to the skill above.

tigr-setup-agent.md

Want the whole picture? The docs cover setup for every stack, the reference lists every method and auto-captured event, and why tigr explains what we do with the data once it arrives.

Five minutes from now,
your app can tell you things.

One line to install. One command to add the events. Then tigr reads the stream and writes you the briefing, in plain language, no analyst required.

No credit card · works with Vue, React, React Native and plain HTML