# Optional Attribution Parameters (UTM)

UAS links support standard UTM parameters for execution attribution.

These parameters allow ONCHAIN and integrators to understand where execution intent originates across wallets, bots, launchpads, explorers, and other distribution surfaces — without introducing custody, tracking scripts, or platform control.

UTM parameters are optional, but strongly recommended for integrators distributing UAS links across multiple environments.

UTM parameters do not affect execution routing, pricing, access guarantees, or settlement.

***

#### Supported UTM Parameters

<table><thead><tr><th width="166.83203125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>utm_source</td><td>The specific surface where the link appears</td></tr><tr><td>utm_medium</td><td>The class of surface</td></tr><tr><td>utm_campaign</td><td>Logical grouping or distribution phase</td></tr><tr><td>utm_content</td><td><em>(Optional)</em> Placement or variant identifier</td></tr></tbody></table>

UTM parameters follow standard conventions and are passed through execution unchanged.

***

#### Recommended utm\_medium Values

To ensure consistency across the UAS ecosystem, integrators are encouraged to select utm\_medium values from the list below.<br>

These values describe the type of surface, not the implementation details.

<table><thead><tr><th width="167.01171875">utm_medium</th><th>Definition</th></tr></thead><tbody><tr><td>wallet</td><td>Embedded inside a wallet UI</td></tr><tr><td>bot</td><td>Automated or chat-based agents (Telegram, Discord, Farcaster, etc.)</td></tr><tr><td>explorer</td><td>Block explorers and discovery tools</td></tr><tr><td>launchpad</td><td>Token launch and distribution platforms</td></tr><tr><td>social</td><td>Social feeds and profile links</td></tr><tr><td>web</td><td>General-purpose websites or web applications</td></tr><tr><td>api</td><td>Programmatic or server-generated execution</td></tr><tr><td>email</td><td>Email-based distribution</td></tr><tr><td>qr</td><td>Physical or scanned QR placements</td></tr></tbody></table>

Integrators may use custom values if necessary, but doing so may reduce comparability across surfaces.

***

#### Example: UAS Link with Attribution

```
https://onchain.money/u/USDC
?utm_source=telegram
&utm_medium=bot
&utm_campaign=uas_links
&utm_content=inline_cta
```

* utm\_source=telegram **identifies the exact surface**
* utm\_medium=bot **classifies the execution environment**
* utm\_campaign=uas\_links **groups related distribution**
* utm\_content=inline\_cta **identifies placement (optional)**

If your UAS link already includes query parameters, append UTM parameters using &.

***

#### Recommended Naming Conventions

To maintain clean attribution data:

* Use lowercase
* Use underscores instead of spaces
* Keep utm\_source specific and utm\_medium generic
* Avoid user-identifiable or sensitive data

<mark style="color:$success;">**Good**</mark>

```
utm_source=pinksale
utm_medium=launchpad
```

<mark style="color:red;">**Avoid**</mark>

```
utm_source=launchpad_pinksale_v2_ios
utm_medium=token_sale_campaign
```

***

#### Why Attribution Matters

Because UAS links are permissionless and portable, execution may originate far from the destination application.

UTM parameters allow ONCHAIN and integrators to:

* Measure execution completion by surface type
* Compare execution quality across environments
* Understand repeat execution behavior
* Improve distribution without restricting access

Attribution is informational only and does not influence execution behavior.