> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/sms/writing-messages/utm-parameters-on-recart-links.md).

# UTM Parameters on Recart Links

Explains the UTM parameters Recart automatically adds to message links so SMS traffic is attributed correctly.

Recart tags every link it sends with UTM parameters, so your SMS traffic and revenue show up correctly in Google Analytics and attribution tools.

Recart adds UTM parameters to every link in your messages automatically, so traffic and revenue from SMS are attributed correctly in Google Analytics and any other analytics or attribution platform you use. You don't need to build tracking links yourself.

This article covers which parameters Recart adds, what each one contains, the other parameters you may see in a Recart link, and whether any of them can be changed.

### What Recart adds to every link

Every link you add to a Recart message is shortened, and the destination it points to carries three UTM parameters:

| Parameter      | Value                                                      |
| -------------- | ---------------------------------------------------------- |
| `utm_source`   | `recart`                                                   |
| `utm_medium`   | `recart-sms`                                               |
| `utm_campaign` | the name of the campaign or flow the message was sent from |

This happens on every link type you can add to a message — custom links, site links, product and cart links, and order status and fulfilment tracking links. It also applies when you use a Branded URL: the short link is branded, and the page it opens carries the parameters.

A Recart link resolves to something like `https://yourstore.com/products/example-product?utm_campaign=05.12-summer-sale&utm_medium=recart-sms&utm_source=recart`

**Note:** These parameters are added for you. You don't need to append UTMs to a link before pasting it into a message.

For more on the links you can add to a message, see [Add Links to SMS Flows](https://help.recart.com/en/articles/add-links-to-sms-flows) and [Add Branded URLs to SMS Messages](https://help.recart.com/en/articles/add-branded-urls-to-sms-messages). To see how Recart attributes revenue inside the app, see [Recart Reports](https://help.recart.com/en/articles/recart-reports).

### What the campaign parameter contains

`utm_campaign` is generated from the name you gave the campaign or flow, converted into a URL-friendly format — lowercase, spaces replaced with dashes, and special characters removed. Letters, digits, full stops, underscores and hyphens are kept; anything else is stripped out.

A campaign named **04.17. Summer Sale (A and B)** arrives in your analytics as `04.17.-summer-sale-a-and-b`.

Because the value comes from the name you set in Recart, clear and consistent campaign naming gives you cleaner reporting downstream.

**Note:** The value always comes from the campaign or flow name, never from the name of an individual message inside it. Campaigns and automated flows work the same way.

### Other parameters you may see

Alongside the UTM parameters, Recart links carry a few of their own. These are used by Recart and need no action from you:

* `r_sub_id` — identifies the subscriber who clicked
* `recart_mid` — identifies the message
* `sequence_item_id` — identifies the individual message within a flow or campaign
* `ghostmonitor_session_id` — used for session tracking
* `disable_cart_recovery` — tells Recart's on-site script not to run its cart-restore behaviour on that visit

### Changing the parameters

The three UTM parameters are set by Recart and can't be edited in the app. There's no UTM section in **SMS Settings**, and the values can't be overridden on an individual campaign or flow.

If you're standardising UTMs across your marketing platforms, or your attribution tool expects a different format, get in touch and tell us what you're trying to match — we'll let you know what's possible.

### Frequently asked questions

**Can I turn the UTM parameters off?**

No. They're added automatically to every Recart link and can't be disabled.

**Will they work with Google Analytics 4?**

Yes. They're standard UTM parameters, so GA4 and other analytics tools pick them up with no extra setup. Recart traffic appears under the source `recart` and the medium `recart-sms`.

**Why doesn't my campaign name match what I see in analytics?**

The name is converted into a URL-friendly format — lowercase, dashes instead of spaces, and special characters removed. It's the same campaign, just reformatted. If you see encoded characters like %28 in a campaign value, that name was set before 19 August 2026 — it picks up the current format the next time the campaign or flow is renamed.

**Do campaigns and automated flows use the same parameters?**

Yes. The source and medium are the same across both; only the campaign value changes.

**Can I use these to build segments or audiences in another tool?**

Yes. Any platform that reads UTM parameters can filter on `utm_source=recart` to isolate traffic that came from your Recart messages.

If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md)  We'd be happy to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.recart.com/sms/writing-messages/utm-parameters-on-recart-links.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
