GoHighLevel Email Tracking Limitations with Custom SMTP

What GHL Actually Tracks

With custom SMTP, GoHighLevel's tracking capabilities break down into two categories: what works and what's completely blind.

Works Fine

• Opens — GHL injects a 1x1 tracking pixel into every HTML email. When the recipient's email client loads images, the pixel fires and GHL records an open.
• Clicks — GHL rewrites every link in your email to pass through their tracking redirect. When someone clicks, GHL logs it and forwards to the original URL.

Both work because GHL controls the email content before handing it to your SMTP server.

Completely Blind

• Delivered — GHL doesn't know if the recipient's server accepted the message (see SMTP stats broken)
• Bounced — Hard bounces and soft bounces are invisible
• Deferred — Temporary failures and retries aren't tracked
• Spam complaints — Feedback loop data never reaches GHL
• Unsubscribes via list-unsubscribe header — Provider-level, not GHL-level

This isn't a bug. It's an architectural limitation explained in our SMTP stats breakdown.

Why the Gap Exists

The SMTP protocol is a one-way handoff. When GHL sends via custom SMTP:

1. GHL composes the email (adds pixel, rewrites links)
2. GHL connects to your SMTP server and transmits the message
3. Your SMTP server accepts the message and queues it
4. GHL's job is done — connection closes

Everything after step 3 happens between your SMTP server and the recipient's mail server. Bounces, deferrals, and delivery confirmations flow back to your SMTP provider, not to GHL.

For GHL to see this data, they'd need to consume webhooks from every SMTP provider (Mailgun, SendGrid, SES, Postmark, etc.). As of April 2026, they haven't built this.

Practitioner note: This is the number one thing I explain to new GHL agency owners. They set up custom SMTP, see empty delivery stats, and think something's broken. Nothing's broken — GHL just wasn't designed to be a deliverability dashboard. Accept that and build monitoring elsewhere.

The Open Tracking Problem

Even the metrics GHL does track have significant accuracy issues.

Apple Mail Privacy Protection

Since iOS 15 (September 2021), Apple Mail pre-fetches tracking pixels through proxy servers. This means:

• Every Apple Mail user appears to "open" every email
• Open rates are inflated 20-40% depending on your audience
• You can't distinguish real opens from Apple proxy loads

Image Blocking

Some email clients block images by default:

• Outlook desktop (some configurations)
• Corporate email with security policies
• Privacy-focused clients

These recipients genuinely open your email but never trigger the pixel.

Bot Clicks

Security scanners at large organizations pre-click links to check for malware. This inflates click rates, especially for enterprise audiences.

What This Means

GHL open rates are directional indicators, not accurate measurements. Use them for trend analysis (is engagement going up or down?) rather than absolute numbers.

Practitioner note: I tell agencies to ignore open rates entirely and focus on click rates and reply rates. Those are harder to fake and more closely tied to actual engagement. And even then, check your SMTP provider for the real delivery data.

Building Real Tracking

Since GHL can't give you complete data, build your monitoring stack at the provider level.

Mailgun

• Dashboard: Logs & Analytics shows delivered, bounced, deferred, complained
• Webhooks: Configure webhooks to push events to your own system
• API: Pull detailed stats programmatically

SendGrid

• Activity Feed: Real-time event stream for every email
• Stats API: Aggregate delivery metrics
• Event Webhook: Push events to your endpoint

AWS SES

• CloudWatch: Delivery, bounce, complaint metrics
• SNS Notifications: Real-time bounce and complaint alerts
• Event Publishing: Route events to S3, Kinesis, or SNS

Google Postmaster Tools

Regardless of SMTP provider, set up Google Postmaster Tools for:

• Domain reputation with Gmail
• Spam rate
• Authentication pass rates
• Encryption stats

This is free and gives you Gmail-specific inbox placement data that no ESP provides.

The Practical Monitoring Workflow

For GHL agencies, here's what actually works:

1. Daily: Check SMTP provider dashboard for bounce spikes or complaint increases
2. Weekly: Review Google Postmaster Tools for reputation trends
3. Monthly: Audit bounce rates, complaint rates, and engagement metrics at the provider level
4. In GHL: Use open and click data only for A/B testing subject lines and content — not for deliverability monitoring

Don't try to force GHL into being your deliverability dashboard. It's your campaign tool. Your SMTP provider is your deliverability dashboard.

Practitioner note: I've built monitoring dashboards for agencies that pull data from Mailgun's API and display it alongside GHL campaign data. It's extra work upfront, but it's the only way to get a complete picture. The agencies that invest in proper monitoring catch problems days before they become disasters.

When LC Email Tracking Is Better

LC Email does show more delivery data inside GHL because GHL has tighter integration with their own Mailgun backend. If tracking convenience matters more than deliverability control, LC Email is simpler.

But LC Email runs on shared Mailgun infrastructure. You're trading monitoring convenience for:

• Shared IP reputation
• Less deliverability control
• No dedicated infrastructure

For most agencies, the custom SMTP trade is worth it. You get better deliverability and build monitoring at the provider level.

If you need help building a complete monitoring workflow for your GHL email infrastructure, book a consultation. I'll set up provider-level dashboards and alerting so you always know what's actually happening with your email.

Sources

• Apple: Mail Privacy Protection
• Mailgun: Webhooks Documentation
• SendGrid: Event Webhook
• Google: Postmaster Tools
• GoHighLevel: Email Services

---

v1.0 · April 2026