Custom Tracking Domains
Custom tracking domains let you use your own branded domain for open tracking pixels and click tracking links, instead of Score CRM's default domain.
Why Use Custom Tracking Domains?
| Benefit | Description |
|---|---|
| Brand consistency | Links show your domain, not a third-party tracker |
| Improved deliverability | ISPs trust links from your own domain more than shared tracking domains |
| Professional appearance | track.yourbrand.com looks better than track.scorecrm.com |
| Reduced spam flags | Shared domains can be flagged if other users send spam |
How It Works
Custom tracking domains use Cloudflare for SaaS to handle SSL certificates and traffic routing automatically.
- You add a CNAME record pointing your tracking subdomain to Score CRM
- Cloudflare automatically provisions an SSL certificate for your domain
- All tracking URLs in your campaigns use your branded domain
- When recipients click links, traffic flows through Cloudflare to Score CRM's tracking server
Setup Process
Step 1: Choose Your Domain
Select a subdomain for tracking, for example:
track.yourbrand.comclick.yourbrand.comemail.yourbrand.com
Step 2: Add in Score CRM
- Go to Organization Settings → Tracking Domains
- Click Add Domain
- Enter your subdomain (e.g.,
track.yourbrand.com) - Click Save
Step 3: Configure DNS
Add a CNAME record at your DNS provider:
| Type | Name | Value |
|---|---|---|
| CNAME | track | scre.to (or the CNAME target shown in Score CRM) |
Step 4: Wait for Verification
After adding the DNS record:
- Score CRM calls the Cloudflare API to register your custom hostname
- Cloudflare begins the SSL certificate provisioning process
- A background job checks the status every 5 minutes
- When SSL is active, the domain status changes to Verified
This typically takes 5-15 minutes, but can take up to a few hours depending on DNS propagation.
Step 5: Start Using
Once verified, your next campaigns will automatically use the custom tracking domain for all tracking URLs.
Domain Status
| Status | Meaning |
|---|---|
| Pending | Domain added, waiting for DNS verification and SSL provisioning |
| Verified | SSL certificate is active, domain is ready for use |
| Failed | Verification failed (usually a DNS misconfiguration) |
Troubleshooting
| Issue | Fix |
|---|---|
| Domain stuck in "Pending" | Verify your CNAME record is correctly configured. DNS propagation can take up to 48 hours. |
| SSL certificate not provisioning | Ensure there are no conflicting DNS records (e.g., an A record for the same subdomain) |
| Links not using custom domain | The domain must be in "Verified" status before campaigns use it |
Best Practices
- Use a dedicated subdomain: Don't use your main domain (e.g.,
yourbrand.com), use a subdomain (e.g.,track.yourbrand.com) - Set up before sending: Configure and verify your tracking domain before launching campaigns
- Monitor certificate expiry: Cloudflare handles auto-renewal, but check periodically
- One domain per organization: Each organization should have its own tracking domain