How to Use the INSPECT Tab to View Feature Analytics

The INSPECT tab gives you a live and historical view of how your features are performing in production. Whether you want to track user engagement, monitor error rates, or understand session patterns, INSPECT surfaces the data you need to make informed product decisions.

Setting Up Analytics Integration

All of the feature code generated by IMPLEMENT are built with the Agiloop Instrumentation system. This system automatically generates code for key user interaction areas of the feature being built. When you generate an INSPECT API key for the project and provide it as an environment variable in your app, data is automatically collected.

INSPECT API Key

1. Open your project and navigate to Settings.
2. Locate the INSPECT section.
3. Generate an API key.

Note: Without a valid API key configured in project settings, the INSPECT tab will show an empty state. If you have set up an integration but are not seeing data, double-check that your API key is correct and that your application is instrumented to send events.

Navigating to INSPECT

From any project, select the INSPECT tab in the main navigation. Analytics data in INSPECT is scoped depending on where you access it:

• Per project: Opening INSPECT from the project level shows aggregated analytics across all features and bundles in the project.
• Per bundle: Navigating to a bundle and opening INSPECT shows data for all features within that bundle.
• Per feature: Opening INSPECT from an individual feature shows analytics specific to that feature alone.

This scoping lets you zoom in on a single feature or zoom out to understand overall project health — all from the same interface.

Using the Date Range Selector

The date range selector at the top of the INSPECT tab controls the time window for all metrics displayed on the page.

Available Presets

• This week - Data from the start of the current calendar week
• This month - Data from the start of the current calendar month
• Last 7 days - A rolling 7-day window ending now
• Last 30 days - A rolling 30-day window ending now

Live Mode

Switching to Live mode updates the dashboard in real time, reflecting events as they are captured. Live mode is useful when you have just shipped a feature and want to watch adoption or error rates in the moments after release.

Note: Live mode may increase data refresh frequency. If you are reviewing trends over longer periods, a preset range will give a more stable view for analysis.

Understanding the Metrics Cards

The metrics cards give you an at-a-glance summary of the key signals for your selected scope and date range.

User Metrics

• Total Users - The distinct count of users who triggered at least one event in the selected period.
• Active Users - Users who engaged meaningfully (beyond a passive page view) within the window.
• DAU / WAU / MAU - Daily, weekly, and monthly active user counts. These help you understand retention patterns and whether engagement is growing, stable, or declining.

Session Metrics

• Sessions - The total number of user sessions recorded. A session typically represents a continuous period of activity by a single user.

Error Metrics

• Error Rate - The percentage of sessions or events that resulted in a tracked error. A rising error rate after a deployment is an early signal that something may need attention.

Performance Metrics

Performance data surfaces latency and response time information where available, helping you connect technical health to user experience.

Using Analytics to Drive Decisions

The INSPECT tab is designed to feed directly into your iteration workflow. A few ways teams use it effectively:

• After a feature launch: Switch to live mode and watch DAU climb or error rates stabilize as the rollout completes.
• Before an iteration cycle: Review last 30 days of active user data to identify which features are heavily used versus which are underperforming relative to expectations.
• Tracking goals: Analytics data in INSPECT provides context alongside the goals you manage in the ITERATE tab, helping you see whether product goals are translating into measurable engagement changes.
• Scoping investigations: If a support ticket references a specific feature, open INSPECT at the feature level and narrow the date range to the reported time window to quickly assess whether there was an error spike.

Tip: Use bundle-level scoping when features are tightly related and you want to understand how a group of capabilities performs together, rather than analyzing each feature in isolation.

Summary

INSPECT brings together user, session, error, and performance data in a single dashboard, scoped to the exact level of your project hierarchy you care about. Set up your analytics integration once in project settings, then use the date range selector and metrics cards to monitor feature health and inform your next product decisions.

Related Articles:

• How to Analyze User Journeys in the INSPECT Tab
• How to Create and Track Product Goals in Agiloop
• Tracking and Managing Technical Debt in the ITERATE Tab
• How to Use the Cross-Project Dashboard