# Create New Funnel

Use a funnel when you want to measure progression through a fixed event sequence.

Go to **Analytics > Funnel** and click **New Funnel**.

{% @arcade/embed url="<https://app.arcade.software/share/ZYFX4jyU24HnnsHokmmd>" flowId="ZYFX4jyU24HnnsHokmmd" %}

### Step 1: Configure the funnel

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FkhqSbkyN4FfwtHHiE2uG%2FScreenshot%202025-05-27%20at%2011.35.48.png?alt=media&#x26;token=6e374da9-9d6c-46c9-a249-0cd95ad83350" alt=""><figcaption></figcaption></figure>

#### Funnel name

Give the funnel a clear name that reflects the journey.

Examples:

* `Checkout Completion`
* `Onboarding Activation`
* `Campaign to Purchase`

#### Who: choose the audience

Scope the funnel to the users you want to analyze.

Available options:

* **All Users**
* **Push Receivers**
* **Segment**

**All Users**

Use this when you want the broadest view of overall behavior.

**Push Receivers**

Use this when you want to measure the impact of one or more push campaigns.

You can select specific push messages or campaigns from the list.

**Segment**

Use this when you want to analyze a predefined audience only.

This is useful for regional, lifecycle, or behavior-based comparisons.

{% hint style="info" %}
Use segments when the question is audience-specific. Example: “How does checkout perform for users active in the last 7 days?”
{% endhint %}

#### Events: define the funnel steps

Add the events that represent each step in the journey.

Only include events that clearly mean progress.

Common examples:

* **Product Viewed**
* **Added to Cart**
* **Checkout Started**
* **Purchase Completed**

#### Reorder funnel steps

You can drag and drop steps to match the real journey order.

The saved order becomes the funnel definition.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FwkU9ECJE94Vo4JcKT1xy%2Fimage.png?alt=media&#x26;token=618eb560-ae3a-4f57-85a6-265c25cad197" alt="" width="563"><figcaption><p>Reorder funnel steps</p></figcaption></figure>

#### Did Not: exclude events

Use **Did Not** to remove users who performed an event that breaks the intended flow.

Example:

For a funnel like **Open App → Get Started → Register**, you might exclude **Sign Out**.

If a user triggers **Sign Out** during the journey, that user is excluded from the funnel analysis.

This keeps the report focused on the path you actually want to measure.

#### Time period and scope

Choose a date range using:

* **Last Week**
* **Last Month**
* **Last Year**
* or a custom range

Then choose how the funnel should behave:

* **Within the period**: users can complete steps across the selected date range.
* **In a session**: users must complete steps within one session.

Use session scope for immediate flows. Use period scope for longer journeys.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fm9vCTs3DVHyxRTrnzwuZ%2Fimage.png?alt=media&#x26;token=20a795a9-5e5e-48bd-9766-b9ec2d9b2319" alt=""><figcaption></figcaption></figure>

#### Track anomalies (optional)

Enable anomaly tracking when the funnel monitors a critical business flow.

This helps you catch unusual drops or spikes in funnel performance.

Anomaly detection works by:

* tracking historical funnel performance,
* building an expected range,
* comparing current values against that range,
* and flagging unusual change.

{% hint style="info" %}
Example: if purchase completion suddenly drops because of a payment issue, anomaly tracking can surface it quickly.
{% endhint %}

**Configuration options**

* **Alert Type**: choose the anomaly types to watch.
* **Threshold**: define how sensitive detection should be.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FmdKt8qxQtX7mf3BBDkq3%2FScreenshot%202024-03-05%20at%2016.48.31.png?alt=media&#x26;token=a840933c-ad97-4be5-b99a-e8d9477abfb0" alt="" width="563"><figcaption></figcaption></figure>

When setup is complete, click **Save Funnel**.

### Step 2: Analyze the funnel report

The report shows how users progressed through the selected steps.

#### Summary area

Review the selected date range and the headline funnel metrics:

* users who entered the funnel,
* conversion,
* and drop-off by step.

#### Users

This shows the total number of users who started the journey.

That includes:

* users who completed the funnel,
* and users who dropped at intermediate steps.

#### Platforms

Platform breakdown helps you spot device-specific differences.

Available platform views include:

* **Mobile App Total**
* **iOS**
* **Android**
* **Web Total**

#### Event stages

Each column represents one funnel step.

Use it to see:

* how many users reached that step,
* where the largest drop happened,
* and whether the final step is healthy.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F723PsRc5Us64AjukRmwh%2FScreenshot%202025-05-27%20at%2011.59.54.png?alt=media&#x26;token=21cd8258-c071-4ff1-a0de-7ce44855ebb4" alt="" width="563"><figcaption></figcaption></figure>

### Data discrepancies

Small UI-level variations can happen because Netmera optimizes large-scale data processing for speed.

Typical ranges:

* funnels with over **1,000,000 users**: usually **0.08% to 0.4%**
* funnels with around **500,000 users**: usually **0.006% to 0.05%**

Adding or removing steps can also slightly change visible counts.

{% hint style="success" %}
Use **Export** when you need the most precise output for offline analysis.
{% endhint %}

### Export considerations

Exported values can differ slightly from on-screen values because of display optimization.

Also note:

* deleted users do not appear in exports,
* and exports based on identifiers depend on current user availability.

### Tag users from the report

You can tag users directly from the funnel report for follow-up actions.

To tag:

1. Click the **tag icon** next to a number in the report.
2. Enter a new tag name or pick an existing one.
3. Save.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FHdTMjsKCcIoGcZ3RLmWC%2FScreenshot%202024-03-05%20at%2017.05.36.png?alt=media&#x26;token=a4d15174-54f9-40d1-b858-f33573bd598b" alt="" width="375"><figcaption></figcaption></figure>