doc: New support for per-rcpt tracking (SparkPost/Momentum#1391)#859
Merged
Conversation
Signed-off-by: Doug Koerich <douglas.koerich@bird.com>
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dkoerichbird
requested review from
PauloJeunonSousa,
balupillai,
deepakpn,
rafaelmatsumotomb and
viniciusgiles
viniciusgiles
approved these changes
Jul 13, 2026
balupillai
approved these changes
Jul 13, 2026
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
3 participants
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.
Note
Low Risk
Documentation-only updates with no code, configuration defaults, or security behavior changes.
Overview
This PR documents per-recipient engagement tracking for HTTP transmissions: inline recipients can set
open_tracking,click_tracking, andinitial_openin each recipient'soptionsobject, overriding transmission-level flags for that recipient only and allowing mixed tracked/untracked audiences in one send. It clarifies that this applies only to inline recipients on the REST Transmissions API (not stored lists or SMTPX-MSYS-API).Precedence is updated in
engagement-tracking-http.mdandmsg-gen.mdto add recipient level (highest), with revised fallback examples and a JSON example showing one recipient with tracking off and another inheriting transmission defaults.lastUpdatedmetadata is bumped on both pages; a trailing newline fix is included on the engagement tutorial page.Reviewed by Cursor Bugbot for commit aba2def. Bugbot is set up for automated code reviews on this repo. Configure here.