WooCommerce Tracking

Google’s updated Conversion Goals documentation confirms secondary conversions can enhance algorithm predictions without influencing bids directly. Yet most WooCommerce tracking plugins set add_to_cart and begin_checkout as primary conversion actions alongside purchase by default. When Smart Bidding treats micro-conversions as equal optimization targets, it chases the easiest win — cart additions, not completed orders. The fix: set purchase as the only primary conversion action and demote all funnel steps to secondary.

WooCommerce generates basic Product schema by default — name, description, price, availability, and SKU — but leaves empty the eight JSON-LD attributes AI shopping agents like ChatGPT Shopping, Google AI Mode, and Perplexity need to recommend your products. The missing fields include hasMerchantReturnPolicy, shippingDetails, brand as a nested object, GTIN or MPN identifiers, aggregateRating, color, material, and size. An estimated 94% of stores lack return policy schema, and neither Rank Math Free nor Yoast Free fills these fields automatically. Closing the gap requires paid plugin tiers, custom PHP filter hooks, or a dedicated schema plugin.

Setting up WooCommerce tracking without GTM takes 4 steps. The GTM path takes 12+. That gap—50 to 120 hours of developer time—is why most WooCommerce stores either skip server-side tracking entirely or pay consultants they can’t really afford. There’s a cleaner way to start. This is it. Why GTM Isn’t the Only Path to Server-Side … Read more

Standard UTM parameters are stripped by ad blockers and browser extensions for 42.7% of users (Statista, 2025), leaving Google Tag Manager’s dataLayer blind to campaign source data. inPIPE Free solves this by using coded UTM parameters—randomized strings like ehgys=1276879—that bypass every filter list. When a visitor lands, inPIPE Free automatically decodes these parameters and pushes full campaign intelligence (source, medium, campaign, content, term) to the WordPress dataLayer before GTM fires a single tag. No custom JavaScript, no server GTM container, no rebuild required.

Your WooCommerce dashboard shows 47 orders today. GA4 shows 31 purchases. Where did 16 conversions go? The answer isn’t a configuration error or missing pixel. It’s a fundamental timing problem baked into how WooCommerce processes payments versus how tracking plugins fire events. Here’s the thing: WooCommerce creates orders and changes status to Processing server-side when … Read more

WooCommerce 8.5 introduced native Order Attribution Tracking, but it only captures last-click data within a single session. To know which campaigns actually drive sales, you need both first-touch (what originally brought the customer) and last-touch (what converted them) attribution stored directly on each order. This requires capturing UTM parameters on arrival, persisting them across sessions, and attaching them as order metadata at checkout. Server-side solutions handle this automatically, bypassing cookie expiration and session limits that break native tracking.

WooCommerce tracking plugin conflicts occur when multiple plugins attempt to track the same events—Facebook Pixel, GA4, TikTok, Klaviyo—each adding JavaScript, handling consent differently, and firing duplicate conversions. Common patterns include forgotten legacy plugins, GTM plus plugin plus theme code stacking, and two GA scripts for the same property ID. Auditing requires checking active plugins, theme settings, and browser console for multiple tracking requests. The solution is consolidating to a single source of truth: one system captures events and routes to all platforms, eliminating conflicts and duplicate data entirely.