Setting Up a Click Tracking Subdomain
Get to know how to set up a new click tracking subdomain with Batch to use your own domain in tracking links.
About Subdomains
An email subdomain is a prefix added to your main domain name.

If your company domain is company.com
, you can create any subdomain that will be usef for your tracking links: click.company.com
, track.company.com
, etc.
The following examples are not subdomains:
Separate domain with hyphen: domain-x.com (e.g.,
click-company.com
)Different root domain: domain.x.com (e.g.,
company.click.com
)
Setup Overview
To use your own subdomain for tracking links (such as click.yourdomain.com
), you need to configure a Content Delivery Network (CDN) / proxy that:
Intercepts clicks on your tracking subdomain
Forwards the requests to Batch servers
Maintains the tracking functionality while preserving your domain branding
Here is how this would work:

Setting Up a Tracking Subdomain
Choosing a Subdomain Name
Choose a subdomain name that is clear, short and trustworthy. Here are some advices to find a good subdomain name:
❌ DON'T
Technical solution names (e.g., batch.domain.com): While technical teams may prefer this approach to simplify DNS management, it's not recommended. Solution-specific subdomains are rarely used in production email infrastructure and can confuse recipients.
Single-letter abbreviations (e.g., b.domain.com): Avoid abbreviated subdomains that could be confused with technical subdomains like bounce records, and make DNS management difficult.
Random names (e.g. xp3kd8.domain.com): These may be confusing for your recipients and spam filters.
⚠️ PROCEED WITH CAUTION
Suspicious terms: Avoid using terms that might worry users because they are too trechnical or privacy concerning (e.g.,
proxy.company.com
,analytics.company.com
,tracking.company.com
, etc).Long prefixes: Avoid unnecesarily long prefixes like
email-tracking.company.com
, etc.
✅ DO
Use clear, short (2-5 characters) and trustworthy prefixes. Here are some examples:
click.company.com
go.company.com
link.company.com
Use a subdomain dedicated exclusively to Batch click tracking. Ensure it's not already in use for emails or other purposes in your organization.
Configuration
→ Batch Tracking Endpoint
Your CDN must be configured to forward all HTTPS requests to Batch's tracking endpoint.
Origin Server Configuration:
Endpoint:
eu.spgo.io
Protocol: HTTPS only
Method: Forward all incoming requests
→ Step-by-Step guides
Our partner, SparkPost, offers step-by-step guides to help you configure your CDN: Configuring your CDN
Alternatively, you can use a reverse proxy following SparkPost's documentation.
Setup Validation
Once you have configured your CDN, please contact us mentioning the tracking subdomain you have chosen. This will help us validate the setup and activate the custom click tracking for your project.
You can contact:
A Solutions Engineer if an implementation project is ongoing
Or our Custom Care team through support@batch.com
Troubleshooting
You can verify that your custom tracking domain is properly forwarded to Batch's tracking endpoint using the curl
command to check the routing and security:
curl -v https://subdomain.company.com/f/a/b/c/d
Look for the HTTP/2 302
status code. This redirect indicates that your CDN has successfully forwarded the request to Batch's tracking server.
Last updated