> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/tracking-and-data-protection.md).

# Tracking and data protection

Which data Cross Selling Pro processes for recommendations and statistics, which cookies it sets and which switches you have for it.

So that Cross Selling Pro can show personalised recommendations and attribute revenue, the plugin reports events from your shop to InsightSearch. This page describes which data that is, which cookies end up in the browser and how you control the scope with the switches of the card "Tracking". It also helps you with your privacy policy and with setting up your cookie notice.

{% hint style="warning" %}
This page describes the technical behaviour of the plugin. It is not legal advice. Please agree the settings and your privacy policy with your data protection officer.
{% endhint %}

## What tracking is for

Tracking has three tasks:

* **Personalisation:** Types such as "Recently viewed", "You may also like", "Continue where you left off" or "Buy again" need to know what a visitor has viewed, added to the cart or bought.
* **Purchase data for recommendations:** Orders show which products are often bought together. "Goes well with" and "Bestsellers", for example, depend on this.
* **Statistics:** Impressions, clicks and revenue from recommendations appear in the plugin dashboard under "Statistics".

Without tracking, Cross Selling Pro still shows recommendations based on product data, for example "Similar products (alternatives)". Personalised recommendations and statistics, however, become thinner or disappear.

## Which data is transferred

The product data from your feed contains no customer data. Customer related information only arises from the following events.

### Cart

When a visitor adds a product to the cart, the shop reports to InsightSearch: product, quantity, price, a session identifier and, for logged-in customers, the customer ID and the customer number. Customer ID and customer number can be switched off with "Send customer reference".

### Orders

With an order, InsightSearch receives: order ID, the line items with product, unit price and quantity, the amounts (including order total, net total, shipping costs, currency), payment and order status, a session identifier and, for logged-in customers, the customer ID and the customer number. For each line item, the plugin also notes whether it was added to the cart from a recommendation. Device type and the browser identification are added.

Name, address, email address, phone number and payment data are not transferred with orders.

### Events from the browser

Page views, recommendation impressions and clicks on recommendations come from the browser. Among other things, the page address, the page title, the page type (such as home page, category, product, search, cart), the search term on the search results page, the device type (mobile, tablet, desktop), the browser identification, the session identifier and, for logged-in customers, the customer ID if "Send customer reference" is on, are sent along.

The page address is cleaned beforehand: credentials, password and confirmation links and the code in order links for guests are removed. Campaign, search and filter parameters are kept.

These events run through your shop. The shop checks them and passes them on to InsightSearch in the background.

### Loading the recommendations

The visitor's browser loads the recommendations themselves directly from InsightSearch. For technical reasons, InsightSearch receives the visitor's IP address in the process.

### Login

When a customer logs in, an event with the session identifier is sent to InsightSearch. If "Send customer reference" is on, the customer reference is added. This allows the behaviour before login to be linked to the customer.

## The switches of the card "Tracking"

You find the card under **Extensions → My extensions → Cross Selling Pro → Configure** or in the plugin dashboard under **System → Plugin configuration**. All switches can be set per sales channel.

| Setting                                     | Effect                                                                                                                                      | Default                                        |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| "Ignore setting in Consent Manager"         | Always sets the comfort cookie for recommendations, even without consent in the cookie notice. The admin help text says: "not recommended!" | off                                            |
| "Enable order tracking"                     | Sends orders to InsightSearch. Needed for revenue from recommendations and for purchase data                                                | on                                             |
| "Enable cart tracking"                      | Reports products added to the cart                                                                                                          | on                                             |
| "Send customer reference"                   | See help text below                                                                                                                         | on                                             |
| "Events from the browser"                   | "Always (as before)", "Only with consent" or "Off"                                                                                          | "Always (as before)"                           |
| "Transaction states considered "paid""      | Which payment states count as paid in the statistics                                                                                        | "Paid", "Paid partially", "Refunded partially" |
| "Transaction states considered "cancelled"" | Which payment states count as cancelled                                                                                                     | "Cancelled", "Failed", "Refunded"              |

### "Send customer reference"

The admin help text reads: "If enabled, the customer ID and customer number of logged-in customers are sent with orders, cart events and clicks. Personalised recommendation types such as "Buy again" need this. If disabled, these events are only linked by the session identifier."

### "Events from the browser"

The default is "Always (as before)". This sends page views, impressions and clicks to InsightSearch **even without consent**, linked by the session identifier.

* **"Only with consent"** only sends these events once the visitor has accepted the comfort cookie "Personalised recommendations".
* **"Off"** sends no events from the browser.

In both cases, impressions and click rate are missing from the statistics, entirely or in part. Cart and orders do not depend on this switch, but on their own switches.

{% hint style="info" %}
The most restrained setting is: "Events from the browser" set to "Only with consent" or "Off", "Send customer reference" off and "Ignore setting in Consent Manager" off. There is then no personalisation via the customer account (such as "Buy again") and fewer figures in the statistics.
{% endhint %}

### Payment status and invoice payments

Orders with cancelled payment states do not count as revenue from recommendations. Paid, open and unknown ones count. If payments in your shop are never confirmed as paid, for example with invoice payments, additionally select "Open" under "Transaction states considered "paid"".

## Cookies and browser storage

The plugin adds its cookies to the Shopware cookie notice itself.

| Name                                | Entry in the cookie notice          | Group                | Lifetime      | Purpose                                                                                       |
| ----------------------------------- | ----------------------------------- | -------------------- | ------------- | --------------------------------------------------------------------------------------------- |
| `cogi_recommendation_session_token` | "Product recommendations (session)" | technically required | a few minutes | Short-lived access key the browser uses to load the recommendations                           |
| `cogi_recommendation_session`       | "Personalised recommendations"      | comfort features     | 365 days      | Random visitor ID so that recommendations fit again on the next visit. Only set after consent |

* If a visitor withdraws consent, the comfort cookie is deleted.
* Without consent, the plugin uses an identifier derived from the shop session instead of the visitor ID. It cannot be reversed and is only valid as long as the session in the shop exists.
* The Conversion Booster remembers its session for one hour in the browser storage, but only with consent. Otherwise only as long as the page is open.

{% hint style="warning" %}
If you use your own consent tool instead of the Shopware cookie notice, assign `cogi_recommendation_session` to the group for comfort or personalisation there yourself. The plugin detects consent by the cookie being set.
{% endhint %}

## Visitor, session and visit

* **Visitor:** with consent, the random ID from the comfort cookie, otherwise the identifier derived from the shop session.
* **Visit:** A visit ends after 30 minutes without activity. It is kept when the customer logs in.
* **Together with the search plugin:** If the InsightSearch search plugin is installed, both plugins recognise visitors and visits in the same way.
* **Cache:** Customer ID, customer number and session are not part of the cached HTML of your pages. The plugin loads them separately for each visitor.

## Bots and crawlers

The shop sends the browser identification so that bots can be detected. Events from bots do not flow into recommendations and statistics. The plugin also filters out bots beforehand for the key figures in the cogi Commander.

## Data in the shop itself

* **User tracking in the admin:** Under **Overview → User tracking** you see the histories of individual sessions on which personalised recommendations are based. You need the permission to view orders for this.
* **cogi Commander:** The plugin counts cart additions and orders from recommendations for the Commander in the shop, regardless of consent. Impressions and clicks, on the other hand, follow "Events from the browser". If the Commander is not installed, the daily totals stay in the shop for 90 days. More on this under [Working with other plugins](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/working-with-other-plugins.md).
* **Queue:** Until the Shopware background processing passes an event on, it waits in your shop's queue. If this processing is not running, events pile up. See [Technical operation](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/technical-operation.md).

## Checklist for your privacy policy

Go through these points with your data protection officer:

1. The two cookies and their groups in the cookie notice.
2. The setting "Events from the browser". The default also sends without consent.
3. Whether you need "Send customer reference", for example for "Buy again".
4. That orders and carts are sent to InsightSearch with amounts and session identifier.
5. That the browser loads the recommendations directly from InsightSearch and the IP address is transferred in the process.
6. If you use your own consent tool: the assignment of `cogi_recommendation_session`.

For questions about contract documents such as data processing agreements, please contact support.

## Read more

{% content-ref url="/pages/I6Hh3YL63avRayt05N4A" %}
[Statistics](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/statistics.md)
{% endcontent-ref %}

{% content-ref url="/pages/2ZVSAniefBU0WuizMlL8" %}
[Technical operation](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/technical-operation.md)
{% endcontent-ref %}

{% content-ref url="/pages/EcsOGIKxOKzqWlk6mPRy" %}
[Working with other plugins](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/working-with-other-plugins.md)
{% endcontent-ref %}

{% content-ref url="/pages/R4ryPjO5ox01iI39KIJG" %}
[Troubleshooting and FAQ](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/troubleshooting-and-faq.md)
{% endcontent-ref %}


---

# 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://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/tracking-and-data-protection.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.
