Global Configuration
Elasticsuite collects data based on user behaviors on the website.
This data is stored in several Elasticsearch indices and is needed for the following features to work properly :
- Search Analytics Dashboard (Open Source Version)
- Behavioral Autocomplete (Premium Version)
- Behavioral Optimizers (Premium Version)
- A/B Testing Campaigns (Premium Version)
- Facets Recommender (Premium Version)
| Parameter | Default value | Description |
|---|---|---|
| Enabled | Yes | If the tracking service is enabled. |
| Retention delay | 12 | In months. Tracking data older than this will be removed regularly. |
| Use the API to collect data | No | Configures the tracker to send data directly to a dedicated REST API endpoint instead of the legacy invisible pixel method. Highly recommended if your frontend cache (like Fastly) blocks tracking pixels, or if you send larger data payloads. |
| Headless mode | No | Tells Magento that all tracking events are strictly managed and dispatched by a separate frontend application (e.g., PWA or Vue Storefront). Magento will rely entirely on the frontend app and will not inject events from the PHP backend. |
| Filter bot hits | Yes | Automatically detects and ignores tracking hits generated by known AI bots and search engine crawlers. This prevents automated scripts from polluting your data or artificially inflating your metrics. |
Session Configuration
| Parameter | Default value | Description |
|---|---|---|
| Visit Cookie Name | STUID | Visit cookie name, a short-term duration cookie to track visits. |
| Visit Cookie Lifetime | 3600 | By default, short-term cookie is one hour. |
| Visitor Cookie Name | STVID | Visitor cookie name, a long-term duration cookie to track returning visitors. |
| Visitor Cookie Lifetime | 365 | By default, long-term cookie is one year. |
Tracking Anonymization
| Parameter | Default value | Description |
|---|---|---|
| Anonymize customer data after a delay. | No | When enabled, the link between Visitor cookie (anonymous) and Magento Customer (that contains personal data) will be regularly removed. |
| Anonymization Delay | 365 | Displayed only if last field is set to Yes. Tracked customer related data will be anonymized after this delay. |
Queue cleanup configuration
| Parameter | Default value | Description |
|---|---|---|
| Delay | 7 | In days. Defines how long invalid tracker events are kept in the events indexing queue before being automatically removed by a periodic background process [1, 2]. |
| Purge now | - | A manual action button that allows you to immediately delete all invalid tracker events from the indexing queue, completely bypassing the configured delay setting [2]. |