# Handoff links: UTM tags for the agent era

> When an AI agent builds a cart or a quote on your site, the person it works for is invisible. A handoff link gives the agent something to pass on, and connects its work to the person who opens it.

Punchline Analytics · 2026-11-04

Here's a journey that's getting more common. A person asks an assistant to find a plumber who can come on Saturday, or a laptop under a budget, or quotes for software for 50 people. An agent visits your site, builds the cart or fills in the quote, and reports back. Later, the person shows up and buys. Or doesn't.

From your side, two unrelated things happened: a visit from a cloud agent (whose user agent names its operator, never its person) and, separately, a visit from a person. Nothing connects them, so the agent's work gets no credit and you can't tell which agents bring you business.

## Put the context in the link

Marketers solved a version of this long ago. A UTM tag carries "this click came from the October newsletter" inside the link itself, so the context survives the jump from one system to another. Mobile apps did the same with deferred deep links: the link carries what the person was looking at through the app store and into the app.

A handoff link does that for agents:

1. **The agent builds something on your site:** a cart, a quote, a configuration, a booking.
2. **Your server gives it a link to pass on:** "send this to your user". The link is your page with a short random token added, like `https://shop.example/cart/8431?pl_ho=…`.
3. **The person opens it.** The open is recorded against their visit, and if that visit goes on to convert, the handoff counts as converted.

Now you can answer questions that were invisible before: how many agent-built carts reach a person, which agents' handoffs convert, and what the value of agent-built quotes was this month.

## Privacy, by construction

A handoff link identifies a cart, not a person:

- **The token is random and opaque.** It carries no personal data, and only a fingerprint of it is stored.
- **It expires,** after 30 days by default.
- **The agent's request is used in memory only** to tie the link to the agent's session; its IP address and user agent are never stored.
- **Nobody is named.** You learn that the person who opened the link converted, not who they are.

## Try it

In Punchline, it's one API call from your server when an agent builds something:

```bash
curl https://app.punchlineanalytics.com/v1/handoffs \
  -H "Authorization: Bearer $PUNCHLINE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id": "…", "kind": "cart", "value": 249, "currency": "USD", "url": "/cart/8431"}'
```

Return the `url` in the response to the agent, and the report shows links created, opened by a person or an agent, and converted. The [handoff links guide](https://punchlineanalytics.com/docs/handoffs) has the details.

## Do agents actually pass them on?

We tested it. When an agent built a quote and got a link back, it passed the link on unchanged every time it finished the task (Claude: 18 of 18). Links merely offered on ordinary pages almost never made it to the person. So make handoff links for things agents build. [The full results](https://punchlineanalytics.com/blog/do-ai-agents-pass-links-on).

## An open convention

We'd like handoff links to become a convention any agent and any site can use, the way UTM tags did. The [spec is on GitHub](https://github.com/opsscale/handoff-links) under CC BY 4.0, with a minimal example under MIT: implement it, copy it, adapt it. If you build agents or run a site agents shop on, open an issue there and tell us what you'd need.
