Skip to content

docs: make open tracking public and self-serve - #333

Merged
duharry0915 merged 1 commit into
mainfrom
harry/open-tracking-public
Oct 20, 2026
Merged

duharry0915 merged 1 commit into
mainfrom
harry/open-tracking-public

Conversation

@duharry0915

Copy link
Copy Markdown
Collaborator

Open tracking is now free on every plan and self-serve (api #1708, console #1231), so the page no longer needs to be hidden or point people at support.

  • Unhide Knowing when an email is opened in the nav.
  • Remove the private-beta / Developer-plan / 403 wording and the "Getting access" section.
  • Add the console path: Add Domain → Open tracking, or the domain's Edit dialog.
  • Explain the PENDING window when tracking is turned on for a VERIFIED domain: no new inboxes, and track_opens sends get rejected until it re-verifies.
  • Add the two DNS settings that block the link certificate: proxied records (Cloudflare) and CAA records (0 issue "amazon.com"). Also add the recovery step: turn tracking off and back on.
  • track_opens also works on forward.
  • Document the tracking_certificate_failed domain reason in the API reference and in the domain troubleshooting table.
  • Update the open tracking line on the inbox capabilities page.

fern check, check_permissions.py --check and generate_mcp_tool_catalog.py --check pass locally.

🤖 Generated with Claude Code

Open tracking is free on every plan and turned on per domain in the console
or through the API. Unhide the page, drop the private-beta and 403 wording,
add the console steps, the PENDING window, and the DNS settings that block
the link certificate (proxied records, CAA). Document the
tracking_certificate_failed domain reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

✨ API Changes

No changelog changes

💡 Download api-changelog-diff artifact or tag @fern Writer in #github-prs for changelog.

@github-actions

Copy link
Copy Markdown

@duharry0915
duharry0915 merged commit fe52e17 into main Oct 20, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants