> For the complete documentation index, see [llms.txt](https://docs.nosto.com/shopware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/shopware/features/marketing-permission-and-gdpr-compatibility.md).

# Marketing permission and GDPR compatibility

As of version [2.0.0](https://github.com/Nosto/nosto-shopware/releases/tag/2.0.0) Nosto's extension will be automatically adding the `marketing_permission` field to the customer tagging and to the buyer ("customer") object in the conversion tracking i.e. the order-confirmation page. The marketing permission field tells Nosto whether the customer has given [GDPR](https://www.eugdpr.org/) compliant consent of receiving marketing via email or not.

![2.0.0](https://img.shields.io/badge/nosto-2.0.0-green.svg)

By default Nosto's extension uses Shopware's newsletter subscription as a source of information for populating this field. In other words, if a customer is also a newsletter subscriber `marketing_permission` field will be set to `true` and Nosto considers that the customer has given GDPR compliant marketing permission consent. If a customer is not a newsletter subscriber `marketing_permission` field will be set to `false` and Nosto considers that the customer has not given GDPR compliant marketing permission.

![customer\_account\_\_\_english](https://user-images.githubusercontent.com/2778820/38422547-d0a19c38-39b3-11e8-9acc-c832fd0be302.png)

If your store has a custom process for gathering marketing permissions or the default logic explained above doesn't fit for your store, you can override Nosto's extension to amend the behaviour. Please read more detailed instructions in our guide on [overriding the customer data](/shopware/guides/overriding-or-extending-functionalities/overriding-customer-data.md).

## Disabling customer tagging completely

See [Nosto settings](/shopware/configuring.md#customer-tagging)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nosto.com/shopware/features/marketing-permission-and-gdpr-compatibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.