> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.brevo.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.brevo.com/_mcp/server.

## Transactional Email — clarified `contactPixelTrackingConsent` behavior

We clarified the description of the per-recipient `contactPixelTrackingConsent` field on the transactional send-email endpoint to accurately reflect how it behaves:

* `contactPixelTrackingConsent: true` — recipient has consented; the open pixel identifies them.
* `contactPixelTrackingConsent: false` — the open event is anonymized (counted in aggregate statistics only).
* **If the field is not passed**, the recipient is treated as unknown consent status and the email is still sent — the open is anonymized unless your account is configured to track unknown-consent contacts. A value other than `true`/`false` is rejected. The field is ignored entirely when the feature is not enabled for your account.

This corrects earlier wording that suggested a missing field would block the send and generate an error event. Behavior is unchanged — this is a documentation clarification only.

**Endpoint updated:**

[Send a transactional email](/reference/send-transac-email) — `POST /smtp/email`