> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/funnels.md). # Funnels Funnels let Mobile teams measure where users drop off and why. Customers can Build a funnel directly from the dashboard using any combination of user events, screens, or network calls. Because Luciq already captures this data continuously, funnels work retroactively, you don’t need to ship a new release or wait days to collect data, just define the funnel and see results immediately. For every step in the funnel, Luciq surfaces the technical issues that affected users who dropped at that step (crashes, network errors, slow screens, frustration signals) alongside session replays of the dropped users themselves. The result is a clear understanding your user journeys and what to fix exactly to enhance funnel conversion rate *** ### Creating a Funnel #### 1. Open the Funnels page Navigate to **Funnels** from the left sidebar. You'll see a list of all existing funnels with their key metrics at a glance: user count, conversion rate, drop-off rate, and median completion time. #### 2. Click "Create funnel" Click the **Create funnel** button in the top-right corner to open the funnel builder. #### 3. Name your funnel Give your funnel a descriptive name that reflects the user journey you're analyzing, for example: `Checkout Flow` or `Onboarding – New Users`. #### 4. Define your funnel steps Each step represents a point in the user journey. For every step, choose a **step type** and then select the specific event: | Step type | What it tracks | | ----------- | ------------------------------------------------- | | **Events** | Custom user events you can send using an API | | **Screens** | Screen visits, identified by screen/activity name | | **Network** | Network endpoints fired | You can mix step types within the same funnel. For example, a checkout funnel might combine a screen visit (`HomepageActivity`) with a network call (`POST /api/checkout`) and a custom event (`purchase_confirmed`). #### 5. Create Click **Create** to save your funnel. Luciq will immediately process historical session data and display results. *** ### Understanding the Funnel Details Page Clicking on any funnel opens its details page, which is organized into three sections. #### Summary The summary card gives you an at-a-glance health check of the funnel: * **Count:** total number of users who entered the funnel * **Conversion:** percentage who completed all steps * **Drop-off:** percentage who did not complete the funnel * **Sessions breakdown:** a segmented bar showing how drop-off sessions are classified: * πŸ”΄ **Crashing sessions:** user experienced a crash * 🟠 **Frustrating sessions:** session was slow or encountered errors * πŸ”΅ **Tolerable sessions:** some friction but within acceptable thresholds * 🟒 **Satisfying sessions:** smooth experience, might be voluntary abandonment * **Median completion time:** p50 time to complete the funnel end-to-end #### Trends Two charts give you a time-series view of funnel health over your selected date range: * **Conversion rate:** how your conversion rate has moved over time, useful for spotting regressions after a release * **Funnel volume:** the number of users entering the funnel over time #### Funnel Steps A bar chart showing the number of users at each step. The drop-off percentage between consecutive steps is shown between each bar, making it immediately clear which step is the biggest source of abandonment. Clicking on any step bar opens the **Step details panel**. #### Issues A list of all issues that happened from the first step till the last step. This includes all the issues captured by our SDK like crashes, hangs, force restarts, visual issues, bugs, networks.. #### Session Replay A list of all session replays that happened throught the funnel, you can filter the page by frustrating sessions and look at the replays #### Dimensions Table The **Dimensions** table breaks down funnel performance by segment, helping you spot whether a drop-off is widespread or isolated to a specific slice of your users. Switch between three tabs (App version, Device or OS Version) *** ### Debugging Drop-offs in a specific step When you click on a specific step in the funnel chart, a **Step details panel** slides in from the right. This panel surfaces the all the issues that occurred during that step, the performance and stability problems most likely responsible for the drop-off. The Panel also surfaces the session replays for the users that dropped off before this step in the funnel *** ### Using Funnels with the Luciq MCP The Luciq MCP gives your AI assistant full read and write access to Funnels, so you can analyze and manage them through natural language without opening the dashboard. #### What you can ask **Understanding drop-offs:** > "Where are users dropping off in the Checkout funnel?" > "Why are users dropping off at Step 2?" > "What issues are impacting conversion in the Onboarding funnel?" **Getting fix recommendations:** > "What should I fix to improve conversion in the Checkout funnel?" The MCP will pull the relevant issues, session data, and performance signals automatically, and surface the highest-impact problems to address. **Managing funnels:** > "Create a funnel called Booking Flow with these three steps: BookingScreen, POST /api/booking, booking\_confirmed event" > "Update the Checkout funnel to add a step for the payment screen" > "Delete the test funnel" #### Why this matters Traditional funnel tools require you to open the dashboard, navigate to the funnel, identify the drop-off step, and then separately search for related issues. With the Luciq MCP, your AI assistant can complete this entire investigation in a single conversation, from spotting the problem to surfacing the fix, giving your team faster time-to-resolution on conversion issues. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/funnels.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.