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

# Redirect modes

> Choose how a domain resolves incoming URLs: Simple pass-through, Structured tracking, Custom redirects, or Hosted landing pages.

Each domain runs in exactly one mode. The mode decides how an incoming URL is matched, what attribution is recorded, and where the visitor ends up. You pick a mode when adding the domain and can change it later from the domain's **Configuration** tab.

## The four modes

### Mode A — Simple pass-through

True passthrough: swaps the subdomain, keeps the full path and all query parameters unchanged.

```
lp.mybrand.com/any/path?utm_source=fb  →  destination.com/any/path?utm_source=fb
```

* **Attribution** comes from UTM parameters (`utm_source`, `utm_medium`, `utm_campaign`, …). If a URL has no UTMs, the visit is logged with your configured default attribution, or as uncategorised.
* **Configuration:** a destination host, plus optional default attribution values.
* **Best for** SMS and email links where the URL already carries UTMs.

### Mode B — Structured tracking

Parses path segments into attribution fields by position, then rewrites the URL onto a destination template.

```
ref.mybrand.com/ref/youtube/paid/spring-sale  →  quote.mybrand.com/step-1/...
                    │       │        │
                  source  medium  campaign
```

* **Attribution** comes from the path, based on an ordered schema you define (segment 1 = source, segment 2 = medium, and so on). When both path values and UTM parameters are present, the path wins.
* **Configuration:** a destination URL template, the inbound path prefix to match, your attribution schema, and a fallback for URLs that don't fit the schema.
* **Best for** teams with a strict URL naming convention.

### Mode C — Custom redirects

You define each tracked URL individually in a table — exact paths or glob patterns — each with its own destination and attribution labels. See [URL mappings](/domains/url-mappings) for pattern syntax and precedence.

* **Attribution** is whatever you type on each mapping. No automatic parsing.
* **Configuration:** a default destination host (for unmapped traffic) plus the mappings table.
* **Best for** one-off campaigns and URLs that don't follow a pattern.

### Mode D — Hosted landing pages

Instead of redirecting, Dava serves static pages you upload, and tracking fires client-side in the visitor's browser. Because email scanners don't execute JavaScript, scanner and bot fetches never register as visits. See [Hosted pages](/domains/hosted-pages).

* **Best for** email and SMS campaigns where accurate, bot-resistant click counts matter.

## Choosing a mode

| You have                                                 | Choose |
| -------------------------------------------------------- | ------ |
| Links that already carry UTM parameters                  | Mode A |
| A strict path convention encoding source/medium/campaign | Mode B |
| A hand-picked list of campaign URLs                      | Mode C |
| Email campaigns plagued by scanner clicks                | Mode D |

## Switching modes

On the domain's **Configuration** tab, the mode picker shows all four modes; click a different card to switch.

<Warning>
  Switching modes resets the configuration of the current mode. When leaving Mode C, the dialog offers a CSV export of your mappings first.
</Warning>

Mode changes go live within seconds. Use [Test a URL](/domains/test-a-url) to confirm behavior after switching.