Bad data costs organizations an average of $12.9 million per year (Gartner, 2024). For WooCommerce store owners, the corruption starts somewhere nobody thinks to look: the default settings of your tracking plugin. Every major WooCommerce tracking plugin—PixelYourSite, Pixel Manager, Conversios, FunnelKit, GTM4WP—calculates your purchase value differently. Same order, same customer, same cart total. Five different numbers arriving at GA4, Facebook Ads, and Google Ads.

The question isn’t whether your platforms show different revenue numbers. The question is why they always will—as long as you’re trusting a plugin’s default field mapping to get it right.

The Tax, Shipping, and Discount Chaos Nobody Audits

Here’s the thing. When a customer places a $100 order with $8 tax and $5 shipping, what “purchase value” should your tracking plugin send to GA4? Is it $100? $108? $113? What if the customer had a 10% coupon—does the plugin deduct $10 before or after adding tax?

Every plugin answers this question differently, and most store owners have no idea which answer their plugin chose.

GTM4WP includes a separate toggle for tax inclusion and exclusion in ecommerce tracking—defaulting to including tax (GTM4WP documentation, 2024). If your WooCommerce store displays prices excluding tax (common in B2B), GTM4WP sends a higher value to GA4 than what the customer actually sees at checkout. Your conversion value is inflated before it even reaches a report.

FunnelKit takes the opposite approach. It offers explicit checkboxes to exclude shipping and/or taxes from the total sent to GA4—settings most users never configure (FunnelKit documentation, 2025). Out of the box, your purchase values might strip components that other plugins include.

Now layer in the fact that PixelYourSite, Pixel Manager, and Conversios each handle these fields with their own logic. One plugin might include shipping in the GA4 value but exclude it from the Facebook CAPI payload. Another might apply the coupon deduction before tax calculation. A third might send the gross total everywhere and leave it to you to figure out why your revenue reports diverge.

Why Your ROAS Is Built on Mismatched Numbers

GA4 underreports WooCommerce revenue by 15-50% due to ad blockers and browser restrictions (Seresa research, 2025). That’s the data volume problem. But the purchase value problem is different—and arguably worse. Even the conversions GA4 does capture might carry the wrong dollar amount.

Consider a simple scenario. Your WooCommerce store processes a $200 order with $16 sales tax, $12 shipping, and a $20 coupon discount. Here’s what happens across plugins:

Plugin A sends $200 (product subtotal, no tax, no shipping, pre-coupon).
Plugin B sends $180 (subtotal minus coupon).
Plugin C sends $208 (subtotal plus shipping, minus coupon, plus tax).
Plugin D sends $196 (subtotal plus tax, minus coupon, no shipping).

Same order. Four different conversion values. And that’s before ad blockers eat 31.5% of your tracking events entirely (Statista, 2024).

Your Google Ads ROAS calculation depends on accurate conversion values. When the purchase value sent to Google Ads doesn’t match what Facebook received, your cross-platform attribution becomes meaningless. You’re optimizing ad spend against numbers that were never correct to begin with.

You may be interested in: Google Ads Shows 85 Conversions, GA4 Shows 60: Stop Chasing Matching Numbers

The Field-Mapping Lottery Nobody Talks About

The WooCommerce tracking plugin market has fragmented into six or more competing solutions. Each one built its platform integrations independently. Each one made different assumptions about what “purchase value” means.

This isn’t a bug—it’s a design decision. WooCommerce stores can be configured to display prices including or excluding tax. Shipping can be taxed or untaxed. Coupons can apply before or after tax calculation. There is no single “correct” purchase value—but there IS a requirement for consistency across every platform receiving it.

And that’s exactly what the plugin-based approach can’t guarantee. When your GA4 tracking comes from one plugin’s calculation and your Facebook CAPI data comes from another (or even from a different integration within the same plugin), the field mappings diverge silently.

Most store owners never discover the discrepancy. They check whether the purchase event fires—not whether the value it carries matches their WooCommerce order total. The first audit most people perform is asking “did GA4 record a conversion?” The audit they should perform is asking “did GA4 record the right conversion value—and does it match Facebook and Google Ads?”

Why Plugin-Based Tracking Creates Compounding Errors

The value problem compounds with scale. A 10% discrepancy on a single order is annoying. A 10% discrepancy across 500 monthly orders means your platform-reported revenue is off by $5,000-$50,000 depending on your average order value.

And it gets worse. When you run promotions (coupons, free shipping, bundled discounts), the discrepancy pattern changes. Your baseline error rate shifts because each plugin handles promotional values differently. Payment gateway redirects create another layer of value discrepancy—some plugins lose the order data entirely when the customer leaves your site to complete payment.

The result? Your monthly revenue in GA4, Facebook Ads, and Google Ads will never reconcile. Not because the platforms themselves are wrong, but because they each received different numbers from the start.

One Calculation, Every Destination

The fix isn’t finding the “right” plugin settings. The fix is eliminating the field-mapping lottery entirely.

Server-side tracking solves this by calculating the purchase value once—at the server level, using WooCommerce’s own order data as the single source of truth—and sending that identical value to every destination simultaneously. No plugin-level field mapping. No per-platform configuration drift. One calculation, everywhere.

Transmute Engine™ does exactly this. It’s a dedicated Node.js server running first-party on your subdomain that receives order events from WooCommerce via the inPIPE plugin, calculates the correct purchase value once using the actual order data, and routes that consistent value to GA4, Facebook CAPI, Google Ads, BigQuery, and every other configured destination in parallel.

You may be interested in: Your WooCommerce Data Has a Trust Problem

Key Takeaways

• Every major WooCommerce tracking plugin uses different defaults for tax, shipping, and discount handling in purchase values sent to platforms
• GTM4WP defaults to including tax; FunnelKit offers opt-out checkboxes most users never touch—the same order produces different values depending on which plugin you install
• Bad data costs organizations $12.9 million per year (Gartner, 2024)—for WooCommerce stores, the corruption starts at the plugin-level field mapping
• The three-order audit—a standard order, a discounted order, and a free-shipping order—will reveal whether your plugins send consistent values across platforms
• A single-source-of-truth pipeline that calculates purchase value once from WooCommerce order data and sends consistently to all destinations eliminates the field-mapping lottery

Frequently Asked Questions

Your conversion data is only as good as the values your plugins send. See how Transmute Engine calculates once and sends consistently to every platform.