> ## Documentation Index
> Fetch the complete documentation index at: https://docs-v2.adscrush.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Funnels

> Create and manage funnels with landing pages

Funnels group landing pages together and control traffic distribution.

## Fields

| Field | Description |
| - | - |
| **Name** | Funnel display name |
| **Product** | Linked product |
| **Language** | Target language |
| **Status** | Active / Inactive / Marked for Deletion |

## Funnel lifecycle

1. **Active / Inactive** — normal operational states.
2. **Marked for Deletion** — a dev TODO: the funnel must be removed from its
   external hosting (e.g. Hostinger). The funnel stays visible in the main
   list with a "Marked for Deletion" badge so the dev team knows what to
   clean up. Marking is blocked while a live campaign still references the
   funnel.
3. **Deleted** — once the hosting is actually removed, the funnel is moved to
   the **Deleted** section (soft delete via `deletedAt`). The record is kept
   so historical reports keep resolving the funnel name.

From the **Deleted** section (sidebar → Funnels → Deleted) a funnel can be
**restored** to the main list, or **permanently deleted** when the record has
no reporting value left.

> **Why soft delete?** Hard-deleting a funnel breaks historical reporting
> (click/conversion joins against the funnel name) and nulls `campaigns.funnel_id`.
> Soft delete preserves both. Permanent delete is an explicit, audited action
> only available from the Deleted section.

## Landing Pages

Each funnel contains one or more landing pages:

| Field | Description |
| - | - |
| **URL** | Landing page URL (supports [URL macros](/tracking/url-macros)) |
| **Name** | Optional name for MO-parameter targeting |
| **Weight** | Traffic distribution weight (higher = more traffic) |
| **Status** | Active / Inactive |

## Selection Priority

1. `lp` parameter → specific landing page
2. `mo` parameter → match by name
3. Weighted random from active pages


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.