Inxmail
How to configure Inxmail at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive marketing offers, Support marketing analytics
Overview
This guide explains how to reflect Inxmail in the Consenter Manager. On the website itself, Inxmail is used for sign-up forms and web-tracking link parameters; its open and click tracking runs in emails and is governed by the newsletter consent, not the cookie banner. This guide therefore uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. Inxmail sign-up forms on the website and web-tracking parameters in mailing links (Inxmail GmbH, Freiburg, Germany).
What the service does in this scope. Web-tracking parameters link newsletter clicks with clicks on the website; they are added to all links when enabled under Configure web tracking in the mailing settings. The parameters are evaluated by the website's analytics tool (e.g. Google Analytics, etracker, econda). Person-based tracking in emails is controlled per recipient via the Tracking permission attribute. Inxmail states that recipients' consent is required for this processing.
Step 1 — Implement Inxmail
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Receive marketing offers; Support marketing analytics (post-click) |
| Sign-up form | Include the Tracking Permission element |
| Web-tracking parameters | Enable only if the receiving analytics tool is itself covered by Consenter consent |
| Website cookies | Inxmail sets no website tracking cookie in this scope; post-click analysis happens in the analytics tool, which needs its own entry |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Entry needed | Optional — only to disclose form data processing | Website footprint limited to forms |
| Processing purposes | Receive marketing offers | Newsletter |
| Tracking method | No tracking | No website tracking cookie in scope |
| Identifier | Direct identifier | Email address on sign-up |
| Data categories | User-provided data, direct identifier | Form data |
| Legal role of data recipient | Processor | Inxmail data processing agreement |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Until unsubscribe | — |
| Processing location | Germany | German company; no CLOUD Act flag unless the DPA lists US sub-processors |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on