30-40% of conversion data is lost to combined privacy restrictions (Industry consensus, 2025). That gap between your WooCommerce dashboard showing 50 orders and GA4 reporting 12 purchases? It’s not broken tracking. It’s the compound effect of consent rejection, ad blockers, Safari cookie limits, and payment gateway redirects—working exactly as designed.

Here’s what nobody tells you: some attribution gap is permanent and expected. GA4 can only count what reaches it. WooCommerce counts every database record. The question isn’t how to eliminate the gap—it’s how large the gap should be and what you can do to minimize it.

The Five Causes Compounding Together#

Each privacy restriction alone might cause 10-15% data loss. Combined, they create attribution gaps that make GA4 seem broken. Understanding each cause explains why your numbers will never match.

1. Consent Rejection (40-70% in EU Markets)

60-70% of EU users reject cookies when given equal-prominence options (USENIX Security Symposium/CNIL, 2024). When visitors decline tracking consent, GA4 receives nothing—no page views, no events, no purchase data. These visitors become completely invisible to your analytics while still buying your products.

The impact varies by market: US stores typically see 10-20% consent impact. EU stores with GDPR-compliant banners showing balanced accept/reject options see 40-70% of visitors reject tracking entirely.

2. Ad Blockers (31.5% of Users Globally)

31.5% of internet users globally use ad blockers (Statista, 2024). Most ad blockers don’t just block ads—they block Google Analytics scripts entirely. These visitors browse your store, add products, complete purchases, and GA4 never knows they existed.

Ad blocker usage is even higher among tech-savvy demographics. If you sell electronics, software, or developer tools, expect 40-50% of your audience running blockers that make them invisible to GA4.

3. Safari ITP Cookie Limits (7 Days)

Safari limits first-party cookies to 7 days under ITP restrictions (WebKit/Apple Documentation, 2024). A visitor who sees your ad on Monday, researches competitors Tuesday through Friday, and buys on Saturday the following week? Safari deleted their tracking cookie. GA4 sees a new visitor, not a conversion from your ad campaign.

Safari commands roughly 25% of browser market share in North America, higher among iOS users. Multi-session attribution—the foundation of understanding which campaigns drive purchases—breaks for a quarter of your visitors.

You may be interested in: Payment Gateway Redirects Are Killing Your Conversion Tracking

4. Payment Gateway Redirects

PayPal, Stripe Checkout, Klarna, Afterpay—external payment gateways redirect visitors away from your site to complete payment. When they return to your thank-you page, the tracking script may not fire correctly, the session may have expired, or third-party cookie restrictions prevent the connection.

Payment gateway timing creates silent tracking failures. The visitor paid. WooCommerce recorded the order. GA4 never saw the purchase event because the JavaScript didn’t execute on the redirect return.

5. iOS ATT and Cross-Device Tracking

iOS App Tracking Transparency doesn’t directly affect website GA4, but it fragments cross-device attribution. A visitor who sees your Facebook ad on their iPhone, then purchases on their laptop? That conversion path is invisible to both Facebook attribution and GA4’s understanding of the full journey.

The compound effect: each restriction removes a slice of visitors from GA4’s view. Combined, they create the massive gaps store owners panic about.

The Math of the Gap#

Understanding why your numbers don’t match requires seeing the compound effect:

• Starting point: 100 actual WooCommerce orders
• After consent rejection (assume 30% reject): 70 potentially visible to GA4
• After ad blockers (31.5% of remaining): ~48 potentially visible
• After Safari ITP (25% of remaining with multi-session journeys): ~40 potentially visible
• After payment gateway timing issues (10% of remaining): ~36 counted in GA4

Result: 100 WooCommerce orders, 36 GA4 conversions—a 64% gap.

Your actual gap depends on your audience composition, market, payment methods, and consent configuration. But the pattern explains why perfect tracking configuration still shows massive discrepancies.

You may be interested in: Coded UTM Links for WordPress: Cleaner URLs, Hidden Campaigns, and Ad Blocker Protection

What’s a “Normal” Gap?#

Benchmarks vary by market and audience:

• US-focused e-commerce, younger demographic: 20-35% gap typical
• US-focused, older demographic: 15-25% gap typical
• EU/UK with GDPR consent: 40-60% gap typical
• Tech products, developer audience: 40-50% gap typical (higher ad blocker usage)
• B2B services: 25-40% gap typical

If your gap significantly exceeds these ranges, investigate tracking configuration. If it falls within range, your tracking is likely working—the gap is measurement reality, not failure.

What You Can Actually Do#

You can’t eliminate the gap, but you can minimize it and build systems that don’t depend on GA4 being complete.

1. Optimize Consent Configuration

Consent Mode v2 allows GA4 to receive anonymized pings from visitors who reject full tracking. This enables behavioral modeling that estimates conversions from declining users. The modeling requires 1,000+ daily events from both consenting and declining users for 7 consecutive days—most small stores never qualify, but medium stores might.

2. Exclude Tracking Scripts from Cache/Optimization

Cache plugins and JavaScript optimizers can break tracking timing. Ensure your analytics scripts are excluded from minification, deferral, and aggregation. Test after every cache plugin update.

3. Implement Enhanced Conversions

Google Ads Enhanced Conversions use hashed customer data (email, phone) to attribute conversions even when cookies fail. This recovers some conversions that standard tracking misses, particularly for logged-in customers.

4. Use WooCommerce as Your Source of Truth

Stop treating GA4 as the source of truth for revenue. WooCommerce database records are complete—every order, every refund, every actual business transaction. Use GA4 for understanding behavior patterns and channel attribution, but trust WooCommerce for revenue reporting.

5. Implement Server-Side Tracking

Server-side tracking captures conversions that browser-based GA4 cannot reach. Transmute Engine™ runs as a first-party server on your subdomain (like data.yourstore.com), receiving events from WordPress via the inPIPE plugin and routing them simultaneously to GA4, Facebook CAPI, Google Ads, and BigQuery.

Server-side captures what browser-based tracking misses: visitors with ad blockers, those on Safari with expired cookies, and purchases after payment gateway redirects. It creates a parallel data source alongside your WooCommerce truth—not replacing GA4, but filling its gaps.

The Mindset Shift#

The gap between WooCommerce and GA4 isn’t a problem to solve—it’s a measurement reality to understand. Browser privacy restrictions exist to protect visitors, and they’re not going away. Every browser update adds more restrictions, not fewer.

Your job isn’t to fight privacy. It’s to build measurement systems that work within privacy constraints.

That means accepting some visitors will always be invisible to browser-based analytics, using server-side tracking to capture what browsers can’t, trusting WooCommerce for actual revenue figures, and using GA4 for what it’s good at: understanding patterns among the visitors it can see.

Key Takeaways#

• 30-40% attribution gap is normal—it’s the compound effect of consent, ad blockers, Safari ITP, and payment redirects
• GA4 can only count what reaches it—WooCommerce counts every database record regardless of browser behavior
• EU stores with GDPR consent see 40-60% gaps because 60-70% of visitors reject tracking when given balanced options
• The gap is measurement reality, not broken tracking—perfect configuration still shows discrepancies
• Server-side tracking creates a parallel data source capturing conversions browser-based GA4 cannot see

Stop panicking about the gap. Start understanding it—and build measurement that works within reality, not against it.