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

# Feature requests

> Tell us what to build next.

## How to submit

Email [hello@linkutm.com](mailto:hello@linkutm.com) with:

1. **What you're trying to do** - the underlying goal, not the proposed solution.
2. **Why** - the workflow or constraint you're hitting today.
3. **Workaround in use** - what you do today (or what's blocking you entirely).
4. **Volume** - how often this comes up, how many links/users affected.

That's enough to evaluate. Don't worry about formatting or wireframes.

## What gets prioritized

In rough order:

<Steps>
  <Step title="Volume × frequency">
    A request blocking 200 users daily beats one blocking 5 users monthly.
  </Step>

  <Step title="Workflow gap">
    Can't accomplish the task at all (high) vs accomplishable but awkward (medium) vs nice-to-have (low).
  </Step>

  <Step title="Strategic fit">
    Aligned with the product direction (link tracking + analytics + team) - fast track. Adjacent (general URL shortener features) - depends. Out-of-scope (CRM, email sending) - usually not.
  </Step>

  <Step title="Build cost">
    Small + high-impact wins prioritization. Large platform changes ship in cycles.
  </Step>
</Steps>

## What we won't build

To set expectations:

* **Email sending / outreach tools** - out of scope.
* **A/B testing of full pages** - UTM differentiation is supported, full page-level testing isn't.
* **CRM features** - out of scope.
* **Anonymous-tracking-evading workarounds** - we honor user privacy laws (GDPR, etc.) and won't add features that fingerprint visitors covertly.

## Track existing requests

We don't currently expose a public roadmap or voting board. If your request matches something in flight, you'll get a heads-up reply.