Analytics for Linear

Analytics anomalies should become engineering work — not Slack threads that get lost. BetterMeter creates Linear issues automatically when it detects broken links, traffic regressions, or suspicious bot activity. The issue includes full context so engineers can act immediately.

Issues from anomalies

When BetterMeter detects an actionable pattern, it creates a Linear issue with a clear title, description, priority, and labels. Engineers pick it up in their next cycle without anyone needing to triage manually.

POST https://api.linear.app/graphql

{
  "query": "mutation($input: IssueCreateInput!) { issueCreate(input: $input) { issue { id url } } }",
  "variables": {
    "input": {
      "teamId": "TEAM_ID",
      "title": "404 spike: 127 broken links after deploy",
      "description": "BetterMeter detected a 404 spike starting at 14:32 UTC.\n\n**Affected URLs:**\n- /docs/old-api-reference (68 hits)\n- /blog/2025-roadmap (34 hits)\n- /pricing-legacy (25 hits)\n\n**Likely cause:** Deploy at 14:30 removed/renamed these pages.\n\n[View in BetterMeter →](https://bettermeter.com/dashboard)",
      "priority": 2,
      "labelIds": ["label_abc123", "label_def456"]  // Your Linear label UUIDs
    }
  }
}

Trigger scenarios

• 01 404 spike — Broken links after a deploy. Issue lists all affected URLs with hit counts.
• 02 Traffic regression — Key page loses 50%+ traffic. Possible SEO issue or broken redirect.
• 03 Bot surge — Unknown crawler hammering your site. Issue includes user agent and request pattern.
• 04 Performance degradation — Page load times spike, correlating with traffic drops.

Auto-close when resolved

When metrics return to normal — 404s stop, traffic recovers, bot activity subsides — BetterMeter updates the Linear issue status to Done with a resolution comment. No stale tickets cluttering your backlog.