Analytics and funnels
Use Analytics to inspect events and behavioral activity. Funnel analysis measures progression through the event sequence you configure.
Before you start
Initialize the SDK with your own app's key and send named events. Use consistent event names and avoid sensitive properties. Select the intended app and reporting window.
Step by step: events and attribution
- Open Analytics. Choose the available date-range control.
- Review Behavioral Activity Velocity, High Velocity Events, platform distribution and OS versions.
- Compare event counts with users or conversions only when the metric definitions match.
- Open the Referrers or Locations view when you need those breakdowns.
- For campaign analysis, use links with explicit source, medium and campaign values. Read Shortlinks and UTM tracking for examples.
- Use the cross-app Analytics view for portfolio comparisons, selecting the relevant apps. If a report offers CSV/export, set filters first and keep exported user data private.
Step by step: conversion funnels
- Find Conversion Pipeline Analysis and open Launch Funnel Builder.
- Load a template or choose the events for your own funnel.
- Use Add Step to place events in their intended journey order, such as opening a paywall followed by completing a purchase.
- Use Apply Analysis. If you want to reuse the setup, use Save Configuration and give it a meaningful name.
- Inspect each stage and drop-off. Confirm the SDK actually sends every chosen event.
Confirm it worked
A known test journey contributes to the expected event sequence and reporting period. A funnel label cannot create missing events; purchase events are not automatically verified financial transactions.
Troubleshooting
A zero stage often means an event-name mismatch or no eligible activity. Attribution can be absent when tags/referrers were never supplied or were stripped; do not invent an origin. Compare like-for-like windows and avoid summing overlapping reports.