feat(smtp): add contactPixelTrackingConsent to transactional email recipients - #29
Open
piyush-sib wants to merge 2 commits into
Open
Conversation
…cipients Adds the per-recipient ContactPixelTrackingConsent *bool (JSON key contactPixelTrackingConsent) to SendSmtpEmailTo, SendSmtpEmailTo1, SendSmtpEmailCc and SendSmtpEmailBcc, plus the matching docs tables and the api/swagger.yaml snapshot, per the updated source swagger (DTSL/public-api#5895). Pointer type so an explicit false (anonymise) is still serialized while unset is omitted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 5, 2026
Open
feat(smtp): add contactPixelTrackingConsent to transactional email recipients
getbrevo/brevo-php#144
Open
…iption Per-contact consent gates click links as well as the open pixel: an=1 is stamped at send time by DTSL/sendmail-personaliser#1231 and consumed by DTSL/redirection#2384, in production since 2026-08-03. The description added earlier in this PR said "open (pixel) tracking" only, which understated what passing false actually does. Four phrase-level edits, applied to every occurrence (to/to_1/cc/bcc plus the docs/ tables): - "for open (pixel) tracking" -> "for open (pixel) and click tracking" - "consented to open tracking, in which case the open pixel identifies the recipient" -> "consented to open and click tracking, in which case the open pixel and tracked links identify the recipient" - "anonymise the open event" -> "anonymise the open and click events" - "the open is anonymised unless" -> "the open and click are anonymised unless" Comment/doc text only: no type, signature or serialisation change. Matching spec wording update is DTSL/public-api#5900 (bundle) and #5895 (legacy client spec). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
piyush-sib
force-pushed
the
feat/smtp-email-contact-pixel-tracking-consent
branch
from
August 5, 2026 07:03
8d32a1a to
6aad08c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the per-recipient
contactPixelTrackingConsentboolean to theSendTransacEmailrecipient models, per the updated source swagger (DTSL/public-api#5895). This is the SDK counterpart of the per-contact pixel tracking consent feature onPOST /v3/smtp/email(backend live since 2026-07-15; documented on developers.brevo.com).Changes
Added
ContactPixelTrackingConsent *bool(json:"contactPixelTrackingConsent,omitempty") to:SendSmtpEmailToSendSmtpEmail.ToSendSmtpEmailTo1SendSmtpEmail.MessageVersions[].ToSendSmtpEmailCcCc+MessageVersions[].CcSendSmtpEmailBccBcc+MessageVersions[].BccAlso updated the matching
docs/*.mdtables and theapi/swagger.yamlsnapshot (4 recipient definitions).Note on
*bool: the field is a pointer (unlike other bools in this SDK) because the API is tri-state —true(identified tracking),false(anonymise), absent (unknown-consent). A plainboolwithomitemptycould never transmitfalse.Verification
go build ./...+go vet ./lib→ clean{Email, ContactPixelTrackingConsent: &false}→{"email":"a@b.c","contactPixelTrackingConsent":false}; unset → field omittedSibling PRs: getbrevo/brevo-java#27, getbrevo/brevo-csharp#19, getbrevo/brevo-ruby#17 (same field).
🤖 Generated with Claude Code
Description wording covers clicks too
Per-contact consent gates click links as well as the open pixel —
an=1is stamped at send time by DTSL/sendmail-personaliser#1231 and consumed by DTSL/redirection#2384, in production since 2026-08-03. A follow-up commit here extends the field description accordingly ("open (pixel) and click tracking",falseanonymises both events). Comment/doc text only — no type, signature or serialisation change.Matching spec wording: DTSL/public-api#5895 (single spec PR — legacy client spec + OpenAPI bundle + generated v3).