Mailgun Tracking Domain Setup

Why Click Tracking in Mailgun Fails Without Proper Domain Configuration

You click a link in an email, and nothing happens. Not because the link is broken — but because Mailgun couldn’t track it. This isn’t a fluke. It’s a sign your click tracking setup is missing a critical piece: a properly configured tracking domain.

Mailgun doesn’t track clicks by default. It needs a dedicated tracking domain to rewrite your URLs and capture user behavior. Without it, links go straight to the destination — and all insight disappears. This isn’t just about missing analytics. Improper configuration can trigger bounces, land your messages in spam folders, or outright break link functionality.

Think of the tracking domain as a bridge between your email and your analytics. If the bridge isn’t built correctly — if DNS records are missing or misconfigured — the traffic stops at the edge. The chain breaks, and data is lost before it even starts.

Key takeaways

Click tracking in Mailgun requires a dedicated tracking domain to rewrite and monitor links.
Missing or incorrect DNS records (like CNAME or TXT) prevent Mailgun from verifying ownership, causing tracking failures.
Improper setup can result in link bounces, inbox filtering, or complete tracking breakdown.

What Is a Tracking Domain in Mailgun, and Why Does It Matter?

You use a tracking domain—like tracking.yourcompany.com—to handle click redirects in Mailgun without relying on your sending domain’s reputation. This isolation means a misconfigured link or a spammy tracker won’t hurt your main domain’s deliverability or sender score. It's a simple but powerful way to keep your email performance clean and measurable.

How Click Tracking Works Behind the Scenes

When someone clicks a link in your Mailgun email, the request goes to your tracking domain first. Mailgun logs the click, then redirects the user to the intended destination. This process happens invisibly to the end user. The key is that this redirect isn't coming from your original domain—so even if the click-tracking infrastructure gets flagged or throttled, your primary domain remains untouched.

Mailgun’s own documentation supports this separation, emphasizing that using a dedicated subdomain for tracking is an industry-standard approach for maintaining clean metrics and sender reputation (Mailgun Documentation). This isn’t just about convenience—it’s about resilience.

Why Is the Tracking Domain Isolating Critical?

Without a separate tracking domain, every click relies on your sending domain. If that domain has a bad reputation (e.g., due to spam complaints or bounce issues), email providers may throttle or block click-tracking requests—causing your analytics to fail even if the email itself delivered.

Using a dedicated domain means you can troubleshoot analytics issues without jeopardizing email delivery. If your tracking domain gets marked by a blocklist, your main domain is unaffected. This is especially important for campaigns that rely on real-time click data.

It also lets you apply specific DNS records—like SPF, DKIM, and DMARC—to the tracking subdomain independently. This ensures that clicks are verified and trusted by recipient servers. The RFC 5322 standard on email format reinforces the need for strict domain control in email systems, particularly when tracking is involved.

While configuration takes a few minutes, the long-term impact on visibility and deliverability is meaningful. You’re not just tracking clicks—you’re protecting your overall email performance. For teams managing high-volume campaigns, this detail makes a measurable difference.

If you’re validating your email lists before sending, tools like MailTester can help ensure your sender base is clean and reliable—reducing the risk of reputation damage before it starts. Try bulk verification to check list health, or use the real-time API to validate each address on the fly.

The Step-by-Step Process to Configure Your Tracking Domain in Mailgun

You can set up Mailgun tracking domain configuration for click tracking by adding a custom domain, verifying it via DNS TXT record, then enabling click and open tracking in the domain settings. Once done, test with a sample email to confirm links are being tracked properly. This ensures your campaign analytics reflect real user engagement, not just delivery status.

Log in to your Mailgun account and go to the Domains tab. This is where you manage all domains associated with your Mailgun account, including those used for sending and tracking.
Click 'Add New Domain' and enter your tracking domain (like tracking.example.com). Choose a subdomain that’s dedicated to tracking. Avoid using your main sending domain to prevent confusion and ensure clean analytics.
Follow Mailgun’s DNS prompt and add the required TXT record to verify ownership. DNS verification confirms you control the domain. Without it, Mailgun won’t allow tracking features to activate.
Wait for DNS propagation — typically 5 to 30 minutes. The time depends on your DNS provider and the TTL (Time to Live) setting. You can check propagation status using tools like MXToolbox.
In the domain settings, enable 'Click Tracking' and 'Open Tracking'. These features insert tracking pixels and redirect URLs into your messages so you can measure opens and link clicks. They do not affect message delivery.
Test the configuration using a sample email with a tracked link. Send a test message to yourself or a partner mailbox. Click the tracked link and check the Mailgun dashboard to verify the click is recorded.

Why the domain matters for tracking reliability

Using a dedicated tracking domain keeps your analytics isolated from sending behavior. It prevents spam filters from associating poor engagement with your primary domain. This separation is standard in enterprise email practices — see the RFC 5322 guidelines on email structure and routing for reference.

Verify your setup before sending to production lists

Always test tracking with a small sample. A single misconfigured redirect can break the entire tracking chain. If clicks aren’t registering, double-check DNS records and ensure the link uses the correct tracking URL format.

Common DNS Mistakes That Break Mailgun Click Tracking

You’re missing click tracking because of tiny DNS missteps: a missing quote in a TXT record, a typo in the subdomain name, or a CNAME clash. These small errors disrupt Mailgun’s routing and break tracking links. Even after fixing them, delays in DNS propagation can hide the issue. Test carefully — a single character off can prevent tracking entirely.

Incorrect TXT or CNAME Record Syntax

Never omit the quotes around TXT record values. Without them, some DNS providers fail to parse the record correctly, especially if it contains special characters.
Double-check the exact subdomain name. Typing clicks.mailgun.com instead of clicks.yourdomain.com stops tracking dead in its tracks.
Use the full domain in your CNAME target — not just a subdomain. A CNAME pointing to mailgun.com won't work; it must point to the correct subdomain like clicks.yourdomain.com.
Check for extra spaces, capitalization issues, or incorrect TTL values. These don’t always break DNS, but they can delay propagation or cause inconsistent results.

Propagation and Conflicts

Don’t test immediately after updating DNS. Propagation can take up to 48 hours. Use tools like MXToolbox to verify the record is live and visible globally before testing.
Verify no other CNAME records overlap with Mailgun’s routing path. Multiple CNAMEs pointing to the same name cause ambiguity and routing failure.
Check for conflicting SPF or DKIM records. While not directly tied to click tracking, overlapping or misconfigured authentication records can trigger email filtering that breaks click links.
Use RFC 1035 as a reference for correct DNS record structure. It’s the definitive guide on how DNS is meant to work.

If you're sending to a large list, verify your addresses first. A single invalid or misconfigured domain can silently sabotage tracking for many users. Use MailTester’s bulk verification tool to catch invalid emails or domain issues before you send.

Verifying Your Tracking Setup With Real Email Delivery and Click Testing

Send a test email through Mailgun with a tracked link, check the message headers to confirm your custom tracking domain is used, click the link to verify it redirects as expected, and use MailTester’s inbox-placement tester to validate deliverability and simulate real-world delivery behavior.

Send a test email via Mailgun with a tracked link. Use a known inbox (Gmail, Outlook, etc.) and include a link with the go parameter. This triggers the tracking system and lets you observe the full path from send to click.
Inspect the message headers to confirm your tracking domain is in use. Open the raw email in your inbox, look for the Return-Path or Received headers, and verify the tracking domain (e.g., track.yourdomain.com) replaces Mailgun’s default. This ensures your branding and domain reputation are maintained.
Click the tracked link in a browser or network tool. Use DevTools’ Network tab to see the HTTP redirect chain. The first hop should be your configured tracking domain, followed by the original target. A failed redirect, 404, or blocked request indicates misconfiguration.
Test inbox placement and link delivery with MailTester. Use MailTester’s inbox placement tool to send a test email to multiple real inboxes (Gmail, Yahoo, Outlook). It checks for spam detection, delivery success rate, and whether the tracked link is properly rendered and clickable after arrival. This confirms your setup works across real-world conditions.

Why This Matters

Even if your tracking domain is configured in Mailgun, delivery filters, DNS issues, or client-side rendering can block or rewrite links. A single test email isn’t enough. You need real inbox placement data to confirm the link survives the journey intact.

According to RFC 8314, email tracking behavior is highly dependent on delivery environment, filtering rules, and client support. What works in a test environment may fail in production.

Next-Level Validation

Let’s go further: use the MailTester API to verify hundreds of addresses at scale before sending. If your list has stale or invalid emails, even perfect tracking will fail. Start with a free verification to clean your list before your campaign begins.

How MailTester Helps You Validate Tracking Domain Setup Before Sending at Scale

You can catch DNS misconfigurations in your Mailgun tracking domain before sending by using MailTester’s real-time API to verify both the domain’s validity and its DNS records. It checks if your tracking domain’s TXT record resolves correctly, flags missing or incorrect CNAMEs, and identifies conflicts like conflicting MX records that could break click tracking. This helps prevent bounces, reduced deliverability, and wasted sends.

What MailTester Checks in Your Tracking Domain

When you configure a tracking domain in Mailgun, the setup relies on precise DNS records—TXT for verification and CNAME for redirecting clicks. MailTester validates these in real time during verification. If your TXT record doesn’t resolve or your CNAME is missing, your tracking links won’t work, even if the email sends.

It also checks for common misconfigurations that aren’t immediately obvious: a conflicting MX record on the same domain, overly restrictive SPF policies, or DNS propagation delays. These can silently block tracking or trigger spam filters. Running through MailTester’s API gives you a full diagnostic before you send to hundreds or thousands of recipients.

Run the Checks Before You Scale

Let’s say you’ve set up a tracking domain for an upcoming campaign. You don’t want to wait until delivery reports show zero click tracking. Using MailTester’s real-time verification API, you can test your tracking domain configuration on a list of real addresses—whether they’re test accounts, real users, or your own internal test emails.

This isn’t just about validating addresses. It’s about validating the entire email ecosystem. A 2023 report from Return Path (now part of Oracle) found that DNS misconfigurations are one of the top three reasons for delivery failure in transactional emails. MailTester surfaces these issues early, so you can fix them before they cause lost opens, clicks, or revenue.

Use it before you deploy campaigns at scale. You can test individual addresses with the email checker or run bulk validations with the bulk verification tool. The insights are instant, the feedback is precise, and the cost to test is low—especially when you consider the alternative: a campaign that fails silently due to a broken tracking domain.

Why Your Tracking Links Are Being Blocked — Even With Correct Configuration

You're using Mailgun’s tracking domain correctly, but links still get blocked? That’s because some mail servers block links from domains with no sender history, especially if they’re newly registered or linked to a weak reputation. Even properly configured tracking domains can trigger filters if they haven’t been warmed up or lack DNS stability. Mailgun’s default domains are safe, but without consistent sending patterns, they can be flagged — especially on Gmail and Outlook. The fix is simple: use a dedicated, reputable tracking domain with a clean DNS record and a history of legitimate traffic.

Mailgun’s Default Domains Aren’t Automatically Trusted

Mailgun’s tracking domains are technically compliant and fully functional. But if you’ve just started sending or are using them across multiple senders, they appear suspicious to filtering systems. Mail servers use sender reputation as a signal, not just syntax. A domain with no consistent sending pattern, no prior deliverability history, and no established DNS reputation gets treated like a low-trust source — even if the configuration is flawless.

Your Tracking Domain Needs Warmup — Even If It's "Correct"

Let’s be clear: no matter how well you’ve set up SPF, DKIM, and DMARC, reputation matters just as much as configuration. New domains — even ones from Mailgun — can be blocked if they’re suddenly used for high-volume tracking. A sudden spike in clicks from a domain with no past sends often looks like a phishing attempt or a link spam campaign. This is especially true on Gmail and Outlook, which apply aggressive filtering to domains without sender reputation. That’s why warming up your tracking domain is not optional.

It’s not just Mailgun. Industry standards like those from Spamhaus and RFC 7226 emphasize that domain history and sending behavior are critical to filtering decisions. A clean DNS setup without sending history still carries risk.

To avoid this, use a dedicated tracking domain you’ve verified and warmed up before sending. This means sending small, consistent volumes first, ensuring open and click rates stay healthy. Only then should you scale up. If you're testing tracking links before rollout, use inbox placement testing to check how your domains appear in real inboxes across major providers. This helps you spot issues early — before you send your campaign.

Best Practices for Maintaining a Reliable Tracking Domain

You should use a dedicated subdomain under a domain you fully control—never a free or disposable one—for tracking. This reduces risk, ensures alignment with email authentication standards, and helps maintain sender reputation. Monitor DNS settings regularly to catch misconfigurations early. Pair the tracking domain with strong SPF, DKIM, and DMARC policies on your sending domain to prevent spoofing and maintain inbox placement.

Use a Controlled Subdomain, Not a Disposable One

Always assign tracking to a subdomain like track.yourcompany.com, not a domain you don’t own.
Free domains (e.g., click.mailgun.com or track.gotmail.com) are easily abused, flagged, or shut down—making your tracking unreliable.
Use trusted DNS providers and verify DNS records through tools like MXToolbox to confirm proper propagation and resolve issues before sending.

Align Authentication and Monitoring

Ensure your sending domain has strict SPF, DKIM, and DMARC records configured—this builds trust with receiving servers and reduces the chance of your tracking domain being isolated.
Check your domain’s DMARC policy regularly; an overly restrictive or misconfigured policy can lead to rejected tracking links even if they’re valid.
Set up alerts for DNS changes using provider tools or third-party monitors. Unexpected changes can break tracking and degrade deliverability.
Test tracking links in real inboxes using tools like MailTester’s Inbox Placement Test to verify functionality in live environments.

Let’s be clear: tracking domains aren’t just a technical detail—they’re part of your sender reputation. A poorly configured tracking domain can hurt deliverability even if the message itself is clean. Use real verification upfront, and check every address with MailTester before sending to catch invalid or risky emails early, reducing bounce risk and protecting your domain’s standing. You can verify lists at scale with bulk verification, or check individual addresses with the real-time email checker. For continuous validation, integrate MailTester into your CRM or email platform via our API and app integrations.

The Role of Sender Reputation in Click Tracking Reliability

Even with perfect Mailgun tracking domain configuration, click tracking fails if your sender reputation is weak. ISPs block or strip tracking links from messages sent by domains with poor reputation, low engagement, or high bounce rates. This means your campaign’s analytics won’t reflect real user behavior, regardless of how well your technical setup works.

Reputation Is the Foundation of Deliverability

Let’s be clear: a tracking domain isn’t a magic bullet. If your sending domain is on a blocklist or has a history of spam complaints, even properly formatted tracking URLs will be stripped or blocked before they reach the inbox. This is a hard rule enforced by major providers like Gmail and Outlook, which evaluate sender reputation at the message level.

One study by Return Path (now Validity) found that messages from senders with poor reputation are 3.5 times more likely to be delivered to spam folders or blocked entirely. That same study shows that sender reputation influences not just inbox placement, but also whether tracking technologies like click-tracking links survive the delivery process.

Pre-Launch Validation Prevents Tracking Failure

Before you launch, test both deliverability and sender reputation. Use MailTester’s inbox placement tool to simulate how your message lands across major inboxes, and check if tracking links survive. This is not just about the tracking domain—it’s about the full delivery path.

Let’s say your Mailgun setup is correct. Now run a full deliverability check using MailTester’s inbox placement test to see if your campaign reaches the inbox — and if tracking URLs remain usable. If your domain is flagged, you’ll see it early and avoid wasted sends.

Keep your bounce rate under 2% and spam complaint rate under 0.1% to maintain good standing. High bounces indicate poor list hygiene, while spam complaints signal that recipients aren’t engaging. Both hurt sender reputation and break tracking.

Use MailTester’s bulk email verification to clean your list before sending. It’s not just about validity—it’s about confirming that addresses are active, engaged, and likely to receive your message without triggering filters. Even a single bad address can hurt your overall sender score.

Click tracking depends on a reliable delivery path. The technical setup matters—but sender reputation is the gatekeeper. Fix the delivery foundation first, then the tracking works as intended.

Final Check: How to Confirm Your Click Tracking Is Working in Production

Click tracking depends on accurate DNS setup, proper link rewriting, and reliable endpoint reachability. A single misconfiguration can break the chain, so testing in production is essential.

Verify the full flow

Send a test email to a real inbox and click the tracked link. Confirm the redirect lands at the intended destination and that the tracking endpoint receives the request. Check the response code—200 success means the endpoint is reachable.

Review Mailgun logs and delivery

Monitor Mailgun’s logs for click events. Each click should appear as a recorded event with timestamp, user agent, and IP. If no event appears, verify the tracking domain is correctly configured and the link is fully rewritten.

Test across multiple providers: Gmail, Outlook, Apple Mail. Some block or modify links in transit.
Use MailTester to validate that the email reaches the inbox and all links are delivered as expected.
Check for HTML rendering issues that may break tracking URLs in certain clients.

Sources

Since May 5, 2025, Microsoft Outlook requires SPF, DKIM, and DMARC from domains sending 5,000+ emails per day, rejecting non-compliant mail outright at the SMTP level with error 550 5.7.515. — Microsoft Outlook requirements (via MailOver bulk-sender requirements guide) (2025)
Sending from a domain with at least three months of history improves inbox placement by 28% compared with a brand-new domain. — Woodpecker data (via WarmForge deliverability statistics) (2025)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Can I use my main domain as a tracking domain in Mailgun?

While possible, it’s not recommended. Using your main domain for tracking exposes your sending reputation to risks. Use a dedicated subdomain instead.

How long does DNS propagation take after adding the TXT record?

Typically 5 to 30 minutes. Some DNS providers may take longer. Use tools like MxToolbox to verify propagation.

Why is my tracking link not redirecting?

Check the DNS records. A missing or incorrect TXT record prevents Mailgun from validating ownership, breaking tracking.

Does Mailgun support HTTPS for tracking domains?

Yes, Mailgun supports HTTPS. Ensure your tracking domain has a valid SSL certificate, especially if using it with email clients that enforce HTTPS.

Can a tracking domain affect my sender reputation?

Only indirectly. If the tracking domain is abused or associated with spam, it may harm deliverability. Keep it isolated and clean.

How do I test if my tracking domain is vulnerable to spoofing?

Use authentication records like SPF, DKIM, and DMARC. MailTester’s inbox placement test can verify domain alignment and reputation.

Can I track clicks without setting up a tracking domain?

No. Mailgun requires a tracking domain to rewrite and redirect links. Without it, click tracking is disabled.

What happens if I delete a tracking domain in Mailgun?

All past click tracking data remains accessible, but new tracking links will not work. Reconfigure a new domain if needed.

Is it safe to use a subdomain like track.yourcompany.com?

Yes, as long as it has proper DNS records and is not flagged as spam. It’s the standard recommended approach.

How can I detect if my tracking domain is on a blocklist?

Use a service like Spamhaus or MxToolbox to check the domain’s IP or DNS reputation. MailTester also checks blocklist status during verification.

Can I use Mailgun’s free domain for tracking?

Mailgun does not provide a free tracking domain. You must configure your own subdomain with proper DNS records.

Does Mailgun allow custom tracking domains that don’t match the sending domain?

Yes. You can use any domain you control. Just ensure proper DNS setup and authentication records are in place.