Your agent sets it up.
You see what’s working.

You bring the app. Your agent handles setup.

The instructions cover the whole job, from reading your codebase to checking the first events. Your agent continues in the same conversation.

1. 01

   Connect your project

   Your agent reads the repo, runs the CLI and creates the configuration. You approve sign-in in your browser.

2. 02

   Track what matters

   It adds the tracker and instruments real actions in your app: a signup, a published page, a purchase. You review the changes.

3. 03

   Verify the first events

   It checks the tracking plan, runs your checks and exercises real flows. Setup ends with evidence of received events, or a clear next step.

Your tracking plan belongs with your code.

Events and properties live in analytics.yaml. Review them alongside each feature. Generate typed helpers and use CI checks to catch mismatches as your app changes.

Push the plan to generate event charts and property breakdowns. Define conversion funnels in the same file to see where people drop off, from a browser action to a server-side purchase.

# the source of truth, reviewed in a PR
version: 1
project: liinks

events:
  page_published:
    description: User published their page
    tags: [activation]
    props:
      template:
        type: string
        enum: [minimal, grid, stacked]
      link_count:
        type: number

  subscription_started:
    revenue: true
    tags: [conversion]

dashboards:
  funnels:
    - [page_published, subscription_started]

// generated — names and props are checked at build time
import { track } from "@/analytics.gen";

track.pagePublished({
  template: "grid",
  link_count: 12,
});

// ✗ Type error: "carousel" is not assignable to
// "minimal" | "grid" | "stacked"
track.pagePublished({ template: "carousel" });

Useful numbers. Thoughtful defaults.

Explore any date range

Choose presets from today to the last 12 months, or set a custom date range in your project’s timezone. Compare key metrics with the previous period.

Follow a question deeper

Click a source, campaign, page, location or device to filter your traffic. Stack filters, remove them one by one and share the view by URL.

Share the moment

Turn published stats and ranked lists into share cards with a link and a downloadable PNG. Owners can celebrate pageview milestones, too. Snapshot numbers stay fixed as traffic grows.

Connect visits to revenue

Connect Stripe with a restricted read key to import payments, refunds and renewals. Link customers to their visits for source attribution, or send revenue through the server SDK. Currencies stay separate.

Meet the people behind events

Explore recent customers and their event timelines in People. Identify users in your app to connect activity across visits and devices. Anonymous journeys cover today; all journeys are visible only to you.

Choose what you share

Keep your dashboard private, or publish selected widgets at one URL. Product events, funnels and revenue stay private until you choose to share them.

Measure without cookies

Anonymous traffic uses a daily rotating identifier. No tracking cookies or persistent anonymous profile.

The icons are ours too. Browse the collection or explore real traffic on a public dashboard.