Your email platform reports 1,500 clicks. Google Analytics reports 1,240 sessions. Your email platform says 85 purchases. Google Analytics says 72 conversions.
The natural reaction is to assume one is wrong. But the reality is that both platforms are doing their job correctly — they are simply measuring different things. Email platforms measure engagement with your message. Google Analytics measures behaviour on your website. These two datasets are related but never identical, and understanding exactly why they diverge is essential for interpreting either one correctly.
The Fundamental Difference: Clicks vs Sessions
The single largest source of discrepancy between email platforms and Google Analytics is that they count fundamentally different events.
An email platform records a click the moment a tracking server receives the redirect request from the subscriber's browser. This happens when someone clicks a link in the email, regardless of what happens next. If the subscriber closes the tab before the page finishes loading, the email platform still counts the click. If the tracking redirect fires but the browser fails to reach your website, the email platform still counts the click. The click event is based on the action of clicking, not on the success of the page load that follows.
Google Analytics records a session only after the landing page loads and the GA tracking script executes successfully. If the page load fails, if the visitor's browser blocks the tracking script, or if the visitor navigates away before the script finishes, no session is recorded. A single email click can produce zero, one, or multiple GA sessions depending on page load behavior, redirect chains, and session timeout rules.
A typical drop-off chain illustrates the difference clearly (numbers shown are illustrative):
| Stage |
Events from 1,000 Email Clicks |
| Email clicks recorded (tracking server fires) |
1,000 |
| Website page loads successfully |
950 |
| GA tracking script loads and executes |
920 |
| GA sessions recorded |
900 |
| Users who complete a conversion |
55 |
Nothing is broken. Each measurement method captures a different stage in the journey, and some attrition at every stage is normal.
The Redirect Chain Adds Another Layer
Email platforms do not send visitors directly to your website. They route clicks through a tracking redirect server that records the event before forwarding the browser to the intended destination. The redirect chain has multiple points where discrepancies can appear:
The email platform's tracking server must receive the request, log the click, and issue an HTTP redirect back to the browser. If that server experiences any latency or if the browser cancels the request during the redirect, the email platform may register a click that never reaches Google Analytics. Conversely, if the user's browser follows the redirect but the tracking server fails to log the event due to an error or timeout, Google Analytics may record a session that the email platform never counted as a click.
In our experience working with email marketing teams, these redirect-induced discrepancies are typically small — affecting roughly 1-3% of traffic — but they contribute to the overall gap between the two platforms.
Attribution Windows Work Differently
Conversions are where reporting differences become most visible and most frustrating. The core issue is that email platforms and Google Analytics apply fundamentally different attribution models.
Email Platform Attribution
Most email platforms use a straightforward last-click model within a defined window. If a subscriber clicks a link in your email and converts within the attribution window — typically 7, 14, or 30 days depending on the platform — the conversion is credited to that email campaign. The attribution is self-contained: the email platform knows the subscriber came from a specific send and assigns credit accordingly.
Google Analytics Attribution
GA4 defaults to a data-driven attribution model that distributes conversion credit across multiple touchpoints based on statistical analysis of how each channel influences conversions. If a subscriber clicks an email link, then later searches for your brand and returns through organic search before purchasing, GA4 may split credit between email and organic search. Under certain conditions, GA4 may credit the final touchpoint exclusively, which could be organic search rather than email.
The Time Lag Problem
Consider a typical scenario: a subscriber clicks an email link on Monday, browses your site without purchasing, returns directly on Tuesday through a bookmark, and completes a purchase on Wednesday. The email platform attributes the purchase to Monday's campaign because it falls within the attribution window. Google Analytics may credit the Tuesday return as direct traffic if it was the last touchpoint before conversion, or may apply a fractional attribution across both interactions.
Neither system is wrong. They are applying different attribution philosophies to the same sequence of events.
Cookie Behavior and Privacy Features
Google Analytics relies on first-party cookies to track sessions, link user interactions over time, and attribute conversions. These cookies are subject to browser-level deletion and blocking in ways that email tracking is not.
Basic email tracking does not depend on cookies in the same way browser-based analytics does. A tracking pixel fires and a click redirect is logged server-side regardless of whether the recipient's browser accepts cookies. This gives email tracking a structural advantage for core engagement measurement that Google Analytics cannot match. More advanced email platform features such as cross-session conversion stitching and identity resolution may incorporate cookies or matching mechanisms, but the fundamental click and open tracking operates independently of them.
Privacy features that affect Google Analytics but not email tracking include:
| Privacy Feature |
Effect on GA |
Effect on Email Platform |
| Intelligent Tracking Prevention (Safari) |
Cookie expiry reduced to 7 days |
No direct impact |
| Enhanced Tracking Protection (Firefox) |
Blocks certain tracking scripts |
No direct impact |
| Ad blockers |
Prevent GA scripts from loading |
May block pixel tracking but less frequently |
| Apple Mail Privacy Protection |
No direct impact |
Inflates email open rates |
| Cookie deletion |
Breaks GA session continuity |
No direct impact |
The direction of privacy changes favours email platforms in terms of measurement reliability, since server-side event logging is inherently more resistant to client-side blocking than browser-based analytics.
Revenue Discrepancies Across Three Systems
Revenue reporting is where discrepancies compound because three different systems are involved: your email platform, Google Analytics, and your ecommerce platform or CRM. Each calculates revenue differently.
Your email platform calculates revenue based on orders attributed to email clicks within a defined attribution window. It typically counts gross order value, includes all items in the cart, and does not account for cancellations, refunds or discounts unless integrated with your order management system. Your ecommerce platform calculates revenue from confirmed orders, accounting for cancellations, refunds, discounts, taxes and shipping. Google Analytics calculates ecommerce revenue based on the transaction data sent through its tracking script, which may include or exclude tax and shipping depending on configuration.
The result is that three platforms can report three different revenue figures for the same set of campaigns, and all three can be correct within their respective definitions.
Understanding UTM Limitations
UTM parameters improve consistency by telling Google Analytics which campaign generated a visit. A link with ?utm_source=email&utm_medium=newsletter&utm_campaign=spring_sale ensures that Google Analytics attributes the resulting session to the correct campaign. Without UTM parameters, Google Analytics categorizes email traffic as direct traffic, losing the attribution entirely.
However, UTM parameters cannot address every discrepancy. If a visitor's browser blocks Google Analytics scripts, the UTM parameters are never read because the script never loads. If the landing page redirects before GA fires, the UTM parameters may be stripped from the URL. If the visitor clears their cookies between clicking the email and converting, GA loses the link between the session and subsequent activity. UTM tags improve the quality of matching but do not eliminate the structural differences between the two measurement systems.
Practical Framework: Which Tool for Which Question
The temptation to declare one platform correct and the other incorrect is the source of most reporting confusion. Each platform offers different levels of reliability for different questions:
| Question |
Best Source |
Can GA Answer with UTMs? |
| How many people clicked my email? |
Email platform |
Partially — counts sessions from email, but misses clicks where pages did not fully load |
| How engaging was my campaign? |
Email platform |
Partially — shows session-level engagement, but misses non-click interactions |
| Which subject line performed best? |
Email platform |
Yes — with unique UTMs per variant, but adds page load dependency |
| How many people reached my website? |
Google Analytics |
Yes — that is what GA is built for |
| What did visitors do on my site? |
Google Analytics |
Yes |
| How does email compare to other channels? |
Google Analytics |
Yes — multi-channel attribution is GA's strength |
| How much revenue did this campaign generate? |
Ecommerce platform or CRM |
Yes — ecommerce tracking in GA, but may differ from confirmed orders |
| What is my actual profit after refunds? |
Ecommerce platform or CRM |
No — GA tracks gross events, not cancellations or refunds |
The differences exist not because one tool is broken, but because each measures a different stage of the journey and applies different rules to the data it collects.
Key Takeaways
- Email platforms count clicks; Google Analytics counts sessions. They are different events measured at different stages of the journey
- Attribution models differ fundamentally — email platforms use link-based last-click attribution while GA4 uses data-driven multi-touch attribution
- Privacy features and ad blockers disproportionately affect Google Analytics because it relies on browser-side scripts and cookies
- Revenue figures diverge because email platforms, Google Analytics and ecommerce platforms each calculate revenue differently with different data sources
- UTM parameters improve consistency but cannot eliminate structural differences between measurement systems
- Use each platform for its intended purpose rather than expecting perfect alignment across all of them
Related Articles
