docs: engagement tracking https updates #820
Merged
Conversation
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
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
danielfsousa
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
TASK-80256
Note
Low Risk
Documentation-only updates that adjust guidance and internal links; risk is limited to potential confusion if any of the updated doc links/wording is incorrect.
Overview
Reorients HTTPS engagement tracking guidance toward SparkPost Managed HTTPS (Let’s Encrypt) as the recommended/default path, and reframes the CDN and reverse-proxy articles as alternative setups for users who need custom certificate handling.
Updates and clarifies multiple related docs: retitles the CDN guide (
enabling-https-engagement-tracking-on-sparkpost.md), refreshes metadata dates, adds managed-HTTPS callouts/eligibility bullets, standardizes SSL→TLS terminology, and fixes/updates cross-links (including related-articles links and the custom tracking domains page to mention automatic certificate management after verification).Written by Cursor Bugbot for commit d8db4c2. This will update automatically on new commits. Configure here.