> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/reports-and-analytics/analytics/funnel/create-a-funnel.md). # Create a Funnel Use this page to build a new funnel from scratch. After following these steps, you will be able to define the funnel structure, add steps, refine the audience, configure measurement settings, and save the funnel for analysis. ### Step 1: Open the Create Funnel page Go to **Analytics > Funnel**. Click **Create Funnel**.

Funnel creation page with configuration and visualization panels.

The funnel creation page opens. ### Step 2: Configure the basic funnel settings #### Step 2.1: Select the date range Choose the period you want to analyze. You can select **Today**, **Yesterday**, **7D**, **30D**, **3M**, **6M**, or **12M**. You can also define a custom range.

Date range selector with preset and custom range options.

{% hint style="info" %} If events were created recently, wide date ranges may still return no data. {% endhint %} #### Step 2.2: Enter the funnel details Enter a funnel name. Add a description if you need more context for teammates.

Fields for the funnel name and optional description.

#### Step 2.3: Select the funnel structure Choose how users must complete the funnel.

Funnel structure selector with ordering options.

Option	Description	When to use
In this order	Users complete steps in the selected order. Other events may happen between steps.	Use for standard journeys such as Product View > Add to Cart > Purchase.
In strict order	Users complete steps in the selected order with no other events between steps.	Use for linear flows such as checkout.
Any order	Users can complete the selected steps in any order.	Use when sequence is not important.

{% hint style="info" %} For most standard user journeys, **In this order** is the best starting option. {% endhint %} ### Step 3: Add and refine funnel steps #### Step 3.1: Add the funnel steps Click **+ Add Your First Step**. Select the events that represent each stage in the journey. A funnel must include at least two steps before the visualization appears. For example, a purchase funnel might use **Product Viewed**, **Added to Cart**, **Checkout Started**, and **Purchase Completed**.

Add the first funnel step from the configuration panel.

Select an event to use as a funnel step.

#### Step 3.2: Reorder the steps Drag a step from the handle on the left side. Move it to the correct position in the journey.

Drag a funnel step to reorder the journey sequence.

#### Step 3.3: Add an event property Use **Add event attribute** when a step should only count events with a specific property. Select the attribute, choose an operator, enter the required value, and click **OK**.

Add an event property to narrow a funnel step.

#### Step 3.4: Exclude users by event Use **Exclude Users by Event** to remove users who perform an event that breaks the intended flow. For example, if the funnel is **Open App → Get Started → Register**, you might exclude **Sign Out**.

Exclude Users by Event configuration for removing users from the funnel.

### Step 4: Apply audience filters Click **Apply Filter** to open the **Filter Audience** window. Use filters when you want to analyze a specific user group.

Filter Audience window with rule builder, rule description, and target audience count.

#### Step 4.1: Add filter rules 1. Click **Add Filter Rule**. 2. Select a rule type such as **Segment**, **Tag**, **Platform**, **Response**, **App Installation**, **App Version**, or **Operator**. 3. Select the attribute or condition. 4. Choose an operator. 5. Enter or select the value. 6. If needed, choose **AND** or **OR** between rules. {% hint style="success" %} The **Rule Description** panel summarizes the selected logic. The **Target Audience** section shows how many users match it. {% endhint %} #### Step 4.2: Add a filter group Click **Add Filter Group** when you need a separate rule group. Use groups to combine advanced conditions. For example, you can create a group for **Segment equals New users last 7 days** and **Platform equals iOS**.

Filter group configuration for combining multiple audience rules.

### Step 5: Configure measurement settings Choose how the funnel counts users and how long users have to complete it. #### Step 5.1: Select the counting method * **Unique Users** counts each user once. * **Total Events** counts every matching event occurrence.

Measurement settings for counting method and conversion window.

#### Step 5.2: Set the conversion window The conversion window defines the maximum time allowed between the first and final steps. Choose one of these options. **Option A: Use a time-based conversion window** Select **Minutes**, **Hours**, or **Days**. For example, if you set the conversion window to **7 days**, users must complete the funnel within 7 days after the first step. The default conversion window is **30 days**.

**Option B: Use a session-based conversion window** Select **Sessions** when users can complete the funnel across multiple app sessions. When **Sessions** is selected, the conversion window is calculated from the sessions after the session where Step 1 is triggered. For example, if the conversion window is set to **3 Sessions**, Step 1 can happen in Session 1. The user is counted as converted if the remaining steps are completed in Sessions 2, 3, or 4. If the user completes the funnel in Session 5 or later, the user is not counted as converted.

{% hint style="info" %} Use a shorter window for fast flows such as payment completion. Use a longer window for journeys that can span several days. {% endhint %} ### Step 6: Configure anomaly detection Use **Anomaly Detection** when you need alerts for unusual changes in funnel performance. 1. Select an **Alert type**. 2. Select the **Step to monitor**. 3. Select the **Check Frequency**. 4. Set the **Sensitivity** percentage. 5. Enter one or more **Delivery Emails**. 6. Click **Save**.

Anomaly Detection settings for alert type, monitored step, and check frequency.

Sensitivity and delivery email fields for anomaly alerts.

Saved anomaly detection settings in the funnel configuration.

### Step 7: Save the funnel Click **Save Funnel**. The funnel is saved and opens with its report view. Next, continue with [Analyze a Funnel Report](/netmera-user-guide/reports-and-analytics/analytics/funnel/analyze-a-funnel-report.md). --- # 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://user.netmera.com/netmera-user-guide/reports-and-analytics/analytics/funnel/create-a-funnel.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.