SalesViewer
How to configure SalesViewer at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics, Receive marketing offers
Overview
This guide explains how to implement SalesViewer and how to reflect it in the Consenter Manager.
- Configure the third-party service.
- Map the configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. SalesViewer® B2B company identification script on a website.
What the service does in this scope. SalesViewer states that its entire tracking works without cookies, that data is collected and stored "without a reference to IP addresses", and that it offers a voluntary opt-out for company-based tracking. It identifies companies visiting the site (B2B lead generation).
Simplified format. SalesViewer documents no alternative privacy settings. The guide uses a single fixed-behaviour configuration.
⚠ Recommendation — running SalesViewer before consent is legally uncertain. SalesViewer positions its cookieless technology as usable without consent. The script still runs in the browser and the IP address is processed transiently to identify the company. Have your DPO or independent counsel confirm before loading SalesViewer without consent; otherwise load it after consent.
Step 1 — Configure SalesViewer
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Support marketing analytics; Receive marketing offers (if identified companies are approached) |
| Cookies | None for tracking |
| IP addresses | Not stored with the collected data |
| Opt-out | Provide SalesViewer's opt-out link (sets an opt-out cookie) |
| Loading | See ⚠ recommendation |
| Retention | Not documented — check the DPA |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Support marketing analytics, Receive marketing offers | B2B lead generation. |
| Tracking method | No tracking | Cookieless. |
| Identifier | IP address | Processed transiently for company identification. |
| Data categories | IP address, Browsing and interaction data, Device characteristics | Activity data of company visitors. |
| Legal role of data recipient | Processor | Verify against your SalesViewer DPA. |
| Personalisation model | Group based (properties) | Company-level segmentation. |
| Maximum storage duration | Not documented | — |
| Processing location | Per contract | SalesViewer is a German company; check sub-processors. |
Privacy-policy follow-up
- SalesViewer as recipient; company identification by IP matching; no cookies; opt-out link.
Verification checklist
- No SalesViewer cookies set (except opt-out cookie on request).
- Opt-out link published in the privacy policy.
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