Skip to main content
All CollectionsSettings
How to Enable Tracking on Email Sends in WeGive
How to Enable Tracking on Email Sends in WeGive
Madelyne W avatar
Written by Madelyne W
Updated this week

When enabling email tracking in WeGive, it's critical to configure your tracking subdomain properly to ensure secure links. If not set up correctly, recipients may encounter broken links or insecure warnings. This guide explains how to set up SSL for your CNAME subdomain and troubleshoot common issues.


Why SSL Is Essential for Tracking Links

Tracking links in WeGive use a CNAME subdomain (e.g., email.yourdomain.org) pointing to Mailgun. When a recipient clicks a link in an email:

  1. Link Rewrite: Links are rewritten to use the tracking subdomain.

  2. Click Tracking: The link routes through Mailgun, where clicks are logged.

  3. Redirection: The recipient is redirected to the original URL.

Since Mailgun does not support HTTPS directly, enabling SSL on the tracking subdomain ensures secure communication. This prevents browsers from flagging links as insecure or broken.


Common Issues and Resolution

Issue: Tracking Links Are Broken

Common issues include links are broken because the subdomain lacked SSL. To resolve this:

  1. Enable SSL for the subdomain via your DNS provider or hosting service (e.g., Cloudflare).

  2. Confirm that the subdomain is proxied and serves content over HTTPS.

Issue: Conflicts with Multiple Mailgun Accounts

If your domain is linked to multiple Mailgun accounts, conflicts can arise. Verify which Mailgun account manages your domain and remove duplicates.


Steps to Enable SSL for Tracking Links

  1. Access Your DNS Provider Log in to your DNS provider (e.g., GoDaddy, Cloudflare).

  2. Set Up or Verify the CNAME Record

    • Create or confirm a CNAME record for your tracking subdomain (e.g., email.yourdomain.org).

    • Ensure it points to mailgun.org.

  3. Enable SSL for the CNAME Subdomain

    • If using a provider like Cloudflare:

      • Enable the proxy for the CNAME record.

      • Set the SSL configuration to Full (not Flexible) to ensure secure communication.

    • If not using a proxy service, request Mailgun to issue an SSL certificate for your subdomain.

  4. Test the Configuration

    • Open the tracking subdomain (e.g., https://email.yourdomain.org) in a browser.

    • Verify it resolves securely over HTTPS.

  5. Enable Tracking in WeGive

    • Navigate to your email settings in WeGive.

    • Activate tracking and test email links to ensure proper redirection.


Real-World Example: Troubleshooting a Broken Link

In one case, a recipient reported that a link in their email for updating an expired credit card was broken. Upon investigation, it was found that the tracking subdomain (email.exampledomain.org) was not secure, causing the link to fail. Here's how the issue was resolved:

  1. Identified the Problem
    The CNAME record for email.exampledomain.org correctly pointed to mailgun.org, but the subdomain lacked SSL, making it insecure.

  2. Enabled Proxying via Cloudflare
    In Cloudflare, the proxy option for the CNAME record was enabled. This allowed the subdomain traffic to be routed through Cloudflare’s secure HTTPS layer.

  3. Updated SSL Configuration
    The SSL setting in Cloudflare was switched from Flexible to Full, ensuring that secure HTTPS connections were enforced.

  4. Verified the Fix

    • Navigated to https://email.exampledomain.org in a browser and confirmed it resolved securely.

    • Sent a test email and verified that the tracking link now redirected to the intended URL without issues.

Did this answer your question?