Keren Analytics Documentation

Connect Your Application

Keren Analytics works with your existing Azure Application Insights telemetry. There's nothing to install in your app to get started.

What you need

• An Azure account with at least one Application Insights resource
• The App Insights resource must be workspace-based (not classic)
• Reader access on the subscription + Log Analytics Reader on the workspace

Your First Dashboard

Once connected, your dashboard has three tabs:

The dashboard auto-refreshes when you change the time range (Today, 7 days, 30 days). All data comes directly from your Azure Log Analytics workspace — nothing is stored on our side.

Marketing Metrics

The Marketing tab gives you a Google Analytics-like view of your application's traffic. Here's what each metric means and where the data comes from.

KPIs

Each KPI card shows a sparkline (mini trend chart) and an anomaly badge if the latest value is significantly different from the average. Green = good change, red = concerning change.

Visualizations

Technical Metrics

The Technical tab helps dev teams monitor application health without writing KQL queries.

KPIs

Session Timelines

See exactly what a user experienced — page by page, click by click, including errors. No screen recording needed. Keren Analytics reconstructs the journey from your telemetry events.

Each timeline shows: pages visited with time on page, clicks, conversions, errors, and exit points. Useful for debugging user-reported issues or understanding conversion paths.

Readiness Score

Your Readiness Score (0-100) measures how complete your telemetry coverage is. A higher score means more insights available in your dashboards.

Improve Your Telemetry

Keren Analytics detects what's missing and generates implementation prompts tailored to your detected tech stack. Here's the process:

Common improvements

Track Campaigns (UTM Parameters)

Keren Analytics automatically detects UTM parameters in your URLs. No setup needed — just add standard UTM parameters to your marketing links and the dashboard picks them up.

How to add UTM parameters

Append these query parameters to any link pointing to your application:

https://yourapp.com/pricing?utm_source=google&utm_medium=cpc&utm_campaign=spring_launch

What you get

• A campaign breakdown table showing visitors, sessions, and conversion rate per source/medium/campaign
• Conversion rates are color-coded: green (>8%), default (4-8%), red (<4%)
• Click any campaign row to filter the entire dashboard by that campaign

Set Up A/B Tests

Keren Analytics can detect A/B test variants from URL parameters. Add a parameter like ab_test to your experiment URLs and the URL Parameters panel will track variant distribution.

How it works today

// Control group
https://yourapp.com/pricing?ab_test=control

// Variant
https://yourapp.com/pricing?ab_test=new_pricing_v2

Track Conversions

Conversions are detected from navigation paths. Pages like /signup, /checkout, and /signup/confirm are recognized as funnel pages.

For better conversion tracking, ensure your application's conversion pages have distinct URL paths. The Conversion Funnel visualizes the drop-off at each step of your funnel (e.g., Homepage → Pricing → Signup).

Custom conversion events

For more granular tracking (button clicks, form submissions), add custom events using the Application Insights SDK:

// Track a conversion event
appInsights.trackEvent({
  name: "SignupCompleted",
  properties: { plan: "enterprise", source: "pricing_page" }
});

These custom events will appear in your telemetry and contribute to richer analytics.

Custom URL Parameters

Beyond UTM parameters, Keren Analytics auto-detects any query parameter in your URLs. Common use cases:

Detected parameters appear as interactive chips in the Parameters view. Click any chip to see its top values, and use the Pin button to keep it permanently visible on your dashboard.

Click Filter on any value to filter the entire dashboard by that parameter — for example, see all metrics for visitors who came with promo=SPRING20.

API Reference

Access your analytics data programmatically. All endpoints return JSON and require authentication via session cookie (set by the login flow).

Use the API to build custom integrations: Slack bots, weekly reports, CI/CD quality gates, or embedded dashboards in your internal tools.

Dashboard Data

// Example: fetch dashboard data
const response = await fetch('/dashboard/overview?range=7d', {
  credentials: 'same-origin'
});
const data = await response.json();

console.log(data.dashboard.kpis);
// { uniqueVisitors: 1523, sessions: 1844, avgResponseTimeMs: 248, ... }

console.log(data.readinessScore);
// { score: 85, grade: "B", breakdown: [...] }

Prompts & Recommendations

// Response
{
  "prompts": [
    {
      "signal": "pageViews",
      "label": "Page View Tracking",
      "detectedStack": "React (SPA)",
      "prompt": "I need to add page view tracking to my React app..."
    }
  ]
}

Integrate in Your Tools

Use the API to embed Keren Analytics data in your existing workflows:

Slack weekly digest

// Fetch KPIs and post to Slack
const data = await fetch('/dashboard/overview?range=7d').then(r => r.json());
const { uniqueVisitors, sessions, errorRate } = data.dashboard.kpis;

await fetch(SLACK_WEBHOOK_URL, {
  method: 'POST',
  body: JSON.stringify({
    text: `Weekly report: ${uniqueVisitors} visitors, ${sessions} sessions, ${(errorRate*100).toFixed(1)}% errors`
  })
});

CI/CD quality gate

// Check error rate before deploying
const data = await fetch('/dashboard/overview?range=today').then(r => r.json());
if (data.dashboard.kpis.errorRate > 0.05) {
  console.error('Error rate too high, aborting deploy');
  process.exit(1);
}

Notion / Confluence embed

Use the /preview/dashboard endpoint (no auth required) to build simple embed widgets that display current metrics.

Security & Privacy

Troubleshooting