← All guides

Brevo: Anonymize opening and click tracking

By default, Brevo tracks opens and clicks per recipient. If you don't need these behavioral profiles, you can activate anonymous tracking for campaigns and transactional emails.

Campaigns

Under Settings → Default settings → Tracking Anonymous email tracking can be activated. Future opens and clicks will continue to be counted in aggregate but will no longer be attributed to individual contacts.

Set transactional emails separately

There is a separate setting for transactional emails under Settings → Automations → Transactional emails → Tracking. Both areas must be configured separately.

Anonymous does not mean “no tracking” here

Brevo continues to count open and click events as well as aggregated engagement values. The setting reduces the personal attribution; If you don't need any opening/click measurement, you should also check which tracking functions can be completely deactivated.

Basis

The general technical differences between opening and click tracking and necessary shipping data are explained in Newsletter without opening and click tracking.

Prerequisites

Access to campaign and transactional email tracking settings and a test recipient address.

check

Use a test email to check whether opening and click events are recorded according to the selected setting and whether campaign and transaction emails remain separate.

Dismantling

If more detailed evaluation is needed again, only reactivate the required tracking type and document its purpose and storage again.

Related guides

Sources and verification

This guide is based on multiple current sources. Vendor documentation is not treated as proof that every concrete installation automatically follows the same privacy characteristics.

Important: IP processing is not IP storage

An IP address has to be processed to establish and deliver a network connection. Hosting providers, firewalls or DDoS protection may also process or retain it for a limited time for security purposes. No Logging distinguishes this security layer from unnecessary persistent visitor logging by the website, application and ordinary access logs.

↑