> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/how-do-i-add-an-unsubscribe-link-to-my-emails.md).

# How do I add an unsubscribe link to my emails?

Mechanic doesn't permit bulk email messages, in which the same content is sent to many customers at once. As a rule of thumb: if an email requires an unsubscribe link, it shouldn't be sent using Mechanic. ([Learn more about this.](/core/actions/email.md#restrictions))

In the rare case that an email *does* warrant an unsubscribe link, use `{{ customer.unsubscribe_url }}` to add a link, like this:

```
<a href="{{ customer.unsubscribe_url }}">Unsubscribe</a>
```

This property of [the customer object](/platform/liquid/objects/shopify/customer-object.md) points to a Mechanic-powered URL that...

1. Turns off the "Accepts marketing" property of the related customer, in their Shopify records
2. Gives the customer a link to return them to the Shopify store's online storefront

{% hint style="info" %}
If your task code doesn't have a customer object, you might have to write some different Liquid code to achieve the same ends. The idea is to call the `unsubscribe_url` attribute of the appropriate customer object, regardless of what specific variable holds the customer object.
{% endhint %}


---

# 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://learn.mechanic.dev/faq/how-do-i-add-an-unsubscribe-link-to-my-emails.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.