Allow setting a custom domain for click & open tracking

[rahulkumarsingh73690]

Currently, UseSend uses the default AWS SES tracking links for click and open tracking. Since these tracking domains are shared across many users, all links look the same from a deliverability perspective.

This increases the risk of emails being flagged as spam, especially for transactional and marketing emails sent at scale.

Problem

• Default SES tracking links are shared
• Shared tracking domains reduce sender reputation isolation
• Higher chance of spam filtering due to identical tracking URLs across senders

Proposed Solution
Allow users to configure a custom tracking domain (e.g. track.example.com) for:

• Click tracking
• Open tracking

This would:

• Improve email deliverability
• Isolate sender reputation
• Align with best practices used by ESPs like SendGrid, Postmark, and Mailgun

Expected Behavior

• Users can add and verify a custom tracking domain via DNS (CNAME)
• UseSend uses this domain for all click/open tracking links
• Fallback to default SES links if custom domain is not configured

Why this matters
Using a custom tracking domain significantly reduces spam risk and improves inbox placement, especially for businesses sending from their own branded domains.

Thanks for considering this feature 🙌
Happy to help with testing or documentation if needed.

[harshcodesdev]

Hey @KMKoushik I’d like to take this on as it’s still unassigned.

I’ve been looking into AWS SES custom redirect (tracking) domains and how they integrate with configuration sets. Plan is to add SES support for creating/verifying a custom tracking domain (via DNS CNAME), store the status, and use it automatically for click/open tracking with a fallback to default SES tracking when not configured.

I’ll start with Implementation and open a draft PR early for feedback. Let me know if that works 👍

[KMKoushik]

@harshcodesdev yes but make sure it's tailored to cloud. if not make it only configurable for self-hostied version

[harshcodesdev]

@KMKoushik Quick clarification the current config sets are shared per-region, so setting a custom tracking domain on one would affect all domains using it. For self-hosted (single user) this is fine, but for cloud (multi-tenant) we'd need per-domain config sets.

Should I scope this to self-hosted only for now and handle cloud in a follow-up?

[KMKoushik]

yeo, focus on the self-hosted for now, it will be completely different in cloud