TrueMetriks Analytics

Your WooCommerce store is more than a list of orders - and so is your marketing. TrueMetriks Analytics gives you the complete picture. It is a full marketing-analytics platform for WooCommerce. You see the entire customer journey, funnel reporting, and your true ROAS - real profit measured against real ad spend. Not running WooCommerce? The plugin still works. You do not need a store. On any WordPress site - a blog, a portfolio, a lead-generation site, a course or membership site - install it, connect it once, and it starts tracking page views and visitor journeys, with the same first-party tracking and ad attribution behind them. WooCommerce is not required, and never has to be installed. It simply adds the ecommerce layer on top: product views, add to cart, checkout, and server-side purchase tracking. Everything else described below works either way. It also tracks every order on your store server-side, sending Facebook, Google, GA4, and TikTok (coming soon) the numbers your browser pixel never could. Everything happening on your store, in one place, with the real numbers behind it. The problem it solves Browser pixels lose sales. When a pixel gets blocked by iOS, Safari, or an ad blocker, that purchase disappears from your Facebook, Google, and TikTok reporting. The money hit your bank, but your ad platforms never counted it. So you make decisions on numbers that are wrong. You kill winning ads that look unprofitable and keep funding losers that look fine. You are not bad at this - you are optimizing on broken data. The fix is moving your tracking off the browser and onto the server, then putting all of it in one dashboard you can read. TrueMetriks connects your WooCommerce store and sends events straight from your server through your own first-party domain. They cannot be blocked by a browser setting, and they do not vanish when a shopper clears their cookies. Install the plugin, sign in to TrueMetriks once, and your real numbers start flowing. What you can see

• The full customer journey. Every touch from the first ad click to the purchase, stitched across sessions and devices, so you can see the path that actually drove the sale.
• Funnel reporting. Where visitors enter, where they drop off, and which step is leaking revenue across your checkout and upsell flows.
• Your true ROAS. Real ad spend measured against real profit - not the inflated or deflated numbers each ad platform reports about itself.
• Which ads, funnels, and products make money. Attribution down to the campaign, creative, funnel step, and product, so you know exactly where your budget should go.
• Your real numbers inside the ad platforms, too. The free TrueMetriks Ad Overlay Chrome extension drops your true ROAS, cost per lead, and cost per sale straight onto Facebook Ads Manager and Google Ads, so you read the real metric next to each campaign without leaving the platform you optimize in.

Here is your revenue page. See total revenue drilled down to the exact source, campaign, ad, or email that produced it - each with its own real ROAS, spend, and profit. Here is funnel reporting. Build any funnel and drill into how it performs step by step, so you see exactly where visitors convert and where they drop off. Here is your main overview. Your complete store performance in one place - traffic, revenue, conversion rate, and new versus returning buyers. Here is the TrueMetriks Chrome extension. It puts your true ROAS, cost per lead, cost per sale, and profit directly inside your Facebook Ads Manager and Google Ads dashboards. The tracking that feeds it

• Every order is captured. The plugin hooks WooCommerce at the order level, so anything that creates an order fires a conversion - including one-click upsells and custom checkout flows. No more invisible revenue.
• Conversions are recovered after cookies clear. A shopper clicks your Facebook ad on Tuesday and buys on Friday with their cookies wiped - the plugin saved the original click at checkout and replays it on the server-side sale, so Facebook still gets the credit.
• Your ad platforms see real attribution. Click IDs and UTMs are matched to each purchase and sent server-side to Facebook Conversions API, Google Ads, GA4, and TikTok (coming soon), with full customer identity for stronger matching.
• No duplicate events. TrueMetriks sends conversions server-side only, so you can remove the Facebook Pixel and stop double-counting.
• Your catalog syncs to Facebook automatically. Connect a Facebook Product Catalog and every WooCommerce product you create, update, or delete pushes through on its own, ready for Advantage+ and Dynamic Product Ads.
• One plugin instead of four. It replaces the usual stack of a Pixel plugin, a Google Analytics plugin, a Google Ads conversion plugin, and a catalog plugin - and it does not break every time WooCommerce updates.

See what our customers did Stores and media buyers running their tracking and analytics on TrueMetriks have tripled store revenue, scaled past $100k a month, and cut cost per lead from $70 to $12. Read and watch their stories at https://truemetriks.com/testimonials/ Part of the TrueMetriks platform This plugin is the WooCommerce on-ramp to TrueMetriks - a complete analytics, server-side tracking, and conversion-attribution platform for performance marketers. The plugin sends the clean events; the TrueMetriks dashboard and Chrome extension are where you finally see your true numbers - real ROAS, real cost per lead, full customer journeys, and which ads, funnels, and products actually make you money. Requires a TrueMetriks account TrueMetriks Analytics connects your store to your TrueMetriks account. New to TrueMetriks? Start a 14-day free trial at https://app.truemetriks.com/signup - no credit card required. Then click "Sign in with TrueMetriks" inside the plugin to connect. External services This plugin connects your site to TrueMetriks so it can track your store and send your analytics and conversion data to the ad platforms you choose.

• TrueMetriks (app.truemetriks.com) - when you click "Sign in with TrueMetriks", the plugin links your site to your TrueMetriks account. The Privacy card in the plugin settings also reads and saves your privacy mode here. No analytics events are sent to this address. Terms: https://truemetriks.com/terms - Privacy: https://truemetriks.com/privacy
• Your TrueMetriks tracker - your store's page views and WooCommerce events are sent to TrueMetriks through your own first-party tracking address, then on to the platforms you connect, such as Facebook, Google, GA4, and TikTok (coming soon). Terms: https://truemetriks.com/terms - Privacy: https://truemetriks.com/privacy

Privacy policy: https://truemetriks.com/privacy

1.0.32

• New: WooCommerce refunds. When you refund an order in WooCommerce, in full or in part, the plugin tells TrueMetriks, and the refunded amount is taken off that sale in your TrueMetriks revenue, ROAS and profit. The sale keeps its date and the ad that won it. Refunds are never sent to your ad platforms. Each refunded order gets a note saying whether the refund reached TrueMetriks.

1.0.31

• New: WooCommerce Subscriptions support. Each subscription payment now tells TrueMetriks whether it is the first payment or a renewal. Your TrueMetriks dashboard shows renewals apart from new sales, and you choose what your ad platforms receive for a renewal (a custom event, a Purchase, or nothing) in your TrueMetriks dashboard. Nothing changes for stores without WooCommerce Subscriptions.
• Fixed: a renewal order no longer copies the original checkout's tracking details (visitor id, IP address, order markers) from WooCommerce Subscriptions. A renewal order now carries only the buyer's own details, so TrueMetriks matches it to the buyer by their email rather than to the original checkout's visitor id.
• New: if WooCommerce Subscriptions gives the plugin an error, or a sale still fails to reach TrueMetriks after every retry, the plugin now tells TrueMetriks within the hour so our team can look into it. No buyer details are sent, only the order number and what went wrong.
• New: each sale now tells TrueMetriks when the order was placed. A sale reaches TrueMetriks when the order first becomes Processing or Completed, which can be days after it was placed, so TrueMetriks can now tell an old order apart from a new one.

1.0.30

• New: a Privacy card in the plugin settings. Pick Full tracking, Consent banner (GDPR) or HIPAA (cookieless) without leaving WordPress; it is the same setting as Privacy & Security in your TrueMetriks dashboard. Consent banner mode shows visitors a banner with equal Accept and Reject buttons, at the bottom left, center or right, with a link to your privacy policy (pre-filled from your WordPress privacy page) and, if you like, your own banner text, or follows your existing consent tool when you tick "I already use a consent tool". HIPAA mode sends nothing to ad platforms. WooCommerce orders now carry the buyer's answer as it was when they placed the order, so in consent banner mode an order is passed on to your ad platforms only when the buyer clicked Accept. Nothing changes for sites that stay on Full tracking.

1.0.29

• New: the plugin now checks that the tracker is really on your live pages. Cache plugins keep showing visitors the copies of your pages they saved before you connected TrueMetriks, and those copies have no tracker, so no visits were tracked even though the plugin said "Connected". When you connect, the plugin now asks your cache plugin to clear its cache (LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Speed Optimizer, Breeze, Cache Enabler, Hummingbird, WP-Optimize, Comet Cache, Nginx Helper and WP Engine are supported). It then loads your homepage the way a visitor sees it. If the tracker is missing, a warning appears in wp-admin with a "Clear cache now" button and the exact place to clear it by hand, and the same warning shows in your TrueMetriks dashboard. The check repeats in the background and the warning clears itself once the tracker is found. It never runs while a visitor is loading a page.
• New: the Connection card now explains what to do if a cache or speed plugin still minifies, combines, defers or delays the TrueMetriks script: add your tracker hostname to its JavaScript exclude lists, then clear the cache once.

1.0.28

• Fixed: add to cart was not tracked, and could interrupt the shop's own cart code, when a theme, plugin or custom code re-triggered WooCommerce's "added to cart" event without the clicked button. The plugin now accepts the event with or without the button and falls back to the product being viewed. The plugin's WordPress and WooCommerce hooks also now accept fewer arguments than WooCommerce normally sends, so another plugin calling them differently can no longer cause a PHP error.

1.0.27

• New: WooCommerce is no longer required. The plugin now installs and activates on any WordPress site - a blog, a portfolio, a lead-generation site, a course or membership site - and starts tracking page views and visitor journeys as soon as you connect it. Previously it refused to activate without a store. If WooCommerce is not active, the settings page shows Page View on its own and hides the store-only options (purchase, cart, product events, excluded emails and Facebook Catalog), because there is nothing for them to track. Nothing changes for existing stores: with WooCommerce active every event, setting and card behaves exactly as before.

1.0.26

• New: exclude your own test purchases. TrueMetriks settings now has an "Excluded emails" list - add the address you check out with when testing your funnel, and orders placed with it are skipped entirely: they never reach your reports and are never passed on to Facebook, Google or TikTok. Choose "Exact match" for a single address, or "Contains" for a fragment such as @yopmail.com to cover every throwaway address on a domain. The list is searchable and paged, and entries can be edited or removed at any time. Removing an entry starts tracking that address again. Real customer orders are unaffected, and leaving the list empty behaves exactly as before.

1.0.25

• Housekeeping: the plugin now tidies up leftover order-send markers in your options table. If a request was interrupted part-way through sending an order, its marker had nothing to remove it until the plugin was deleted. They never loaded on a page view and nothing was broken by them, but they no longer build up.

1.0.24

• Fixed: an order could still be reported as two sales when WooCommerce ran two of its order confirmations a few seconds apart. Before sending, the plugin now re-reads the order straight from the database, so a confirmation that started earlier cannot send a second copy after another one has already finished.

1.0.23

• Fixed: an order could still be reported as two sales when WooCommerce ran two of its order confirmations at the same instant. Each order is now claimed in the database before it is sent, so when two confirmations race, the database picks one and the other stands down. If a send is interrupted, the claim is released again about a minute later and the order is retried.

1.0.22

• Fixed: an order could be sent to TrueMetriks twice when WooCommerce processed the same order in two overlapping requests at the same time. On busy stores that double-counted the sale in your reports and on connected ad platforms. Each order is now sent once, no matter how many times WooCommerce touches it.

1.0.21

• Fix: server-side Purchase events are now marked sent only after a successful send. Failed sends (network error, timeout, 5xx, rate limit) are retried automatically on a backoff (about 5 attempts over an hour) instead of being silently lost.
• New: if a sale still cannot be sent after all retries, the order is flagged and a WooCommerce admin notice asks the store owner to contact TrueMetriks support.
• Internal: each order now uses one stable event id across retries, so a retry can never double-count a sale.

1.0.20

• The plugin now reliably captures the buyer's visitor ID at checkout on both the classic checkout and the block checkout. Previously some purchases reached TrueMetriks without it, and those orders were recorded as a brand-new anonymous visitor, so the sale did not attach to the ads, landing pages, and browsing that led to it. Server-side Purchase events now land on the buyer's real journey, which means more accurate attribution and funnel reporting. No settings to change.

1.0.19

• Fixed a connection bug where the plugin could disconnect itself immediately after you signed in. If an optional integration status check (Facebook Catalog) returned an authorization error, the plugin treated it as the whole connection being revoked and cleared the stored key, so the tracker never loaded. The saved connection is now only cleared when you explicitly click Disconnect.

1.0.18

• New "Calendly & Typeform" setting. When enabled, the plugin also loads the TrueMetriks attribution helper (/t/forms.js) alongside the tracker, so visitor tracking IDs and ad-platform click IDs ride along into Calendly bookings and Typeform submissions for correct server-side attribution. Off by default; enable it only if your site embeds Calendly or Typeform. Uses the same first-party tracker hostname and cache-bypass attributes as the main tracker.

1.0.17

• Tracker URL: enqueue from /t/s-wp.js (the new WordPress-dedicated path). No functional change to event firing; the new path serves the same WP tracker code unconditionally instead of via a per-site config gate.
• Skip tracking for page-builder preview iframes and the WP Customizer. Elementor (?elementor-preview=), Divi (?et_fb=), Beaver Builder (?fl_builder=), Brizy (?brizy-edit=), WPBakery (?vc_editable=), Oxygen (?oxygen-builder=), and the WP Customizer iframe (?customize_changeset_uuid=) render at frontend URLs so is_admin() does not catch them. These are only opened by editors using the builder, so tracking them polluted analytics. Frontend storefront browsing by an admin or editor is still tracked as a real pageview.

1.0.16

• InitiateCheckout no longer fires on FunnelKit sales pages with embedded express checkout (logged-in shoppers) or on FunnelKit Upstroke one-click upsell pages. The hook is still woocommerce_checkout_init for FunnelKit / CartFlows / WFACP compatibility, but the callback now requires is_checkout() && !is_order_received_page() to match real checkout pages only. Identify-on-email guarded the same way.

1.0.15

• WordPress.org compliance: renamed all tm_ / TM_ identifiers (classes, options, transients, hooks, admin-post actions, AJAX endpoints) to truemetriks_ / TRUEMETRIKS_ for the 4+ character prefix requirement.
• WordPress.org compliance: removed all inline tags from PHP output. Tracker and event payloads now ship via wp_enqueue_script + wp_add_inline_script. Cache-bypass attributes (LiteSpeed / WP Rocket / Cloudflare Rocket Loader) injected via the script_loader_tag filter.
• InitiateCheckout hook moved from wp_footer + is_checkout() to woocommerce_checkout_init so FunnelKit / WFACP checkout pages reliably fire IC.
• InitiateCheckout fires with items=[] and total=0 when the WooCommerce cart is empty so FunnelKit funnels (which manage their own offer outside WC's cart) still emit the funnel-entry event.
• Event-toggle checkboxes now default to checked on both fresh installs and plugin upgrades (previously only seeded on first activation).

1.0.14

• WordPress.org compliance pass. All diagnostic logging is now gated behind WP_DEBUG so production sites get a quiet error log.
• New "Refresh connection status" button on the Facebook Catalog card. Re-fetches the catalog state from your TrueMetriks account immediately, bypassing the 60-second status cache.
• Clarified the Default brand help text - the value is sent as the fallback brand when a WooCommerce product has no brand assigned via product_brand, pwb-brand, or yith_product_brand taxonomies. Facebook Catalog requires a brand on every product.
• Clarified the Facebook Catalog card copy - products sync automatically on every WooCommerce create / update / delete; "Resync all products" is only needed after a sync error or to force a full re-push.
• Default events on activation: PageView, Purchase, Initiate Checkout, Add to Cart, and View Content are now all enabled out of the box on fresh installs. Existing installs keep their current per-event preferences.
• AddToCart payload transients now self-clean when the cart item is removed and have a 15-minute TTL (was 1 hour) to cap options-table bloat on abandoned carts.
• Uninstall cleanup now covers truemetriks_default_brand and the truemetriks_catalog_status transient (introduced in 1.0.13).
• Tested up to WordPress 7.0.

1.0.13

• New: Facebook Catalog integration. Connect a Facebook Product Catalog via OAuth and auto-push WooCommerce products on add/update/delete.
• New: Default brand setting under TrueMetriks > Facebook Catalog.
• New: "Resync all products" button to re-push the full catalog on demand.

1.0.12

• Server-side Purchase POSTs now include four order-level fields: shipping total, tax total, applied coupon codes, and lead_source (read from WooCommerce 8.5+ Order Attribution meta, with fallbacks to common third-party lead/affiliate plugin keys). InitiateCheckout carries shipping/tax/coupon as well. These fields are routed through the worker's per-event field-toggle filter so merchants can decide which platforms receive them via the dashboard Tracking page.
• No new permissions, no database migration. Existing events unchanged when the new fields are toggled off in the dashboard.

1.0.11

• Rich items[] payload for Purchase, AddToCart, ViewContent, and InitiateCheckout. Worker channel mappers translate items[] to per-platform shapes (Facebook contents[], GA4 items[], TikTok contents[], Google Ads cart_data.items[]). Captures id, sku, name, price, quantity, currency, category (first product_cat term), brand (first matching brand taxonomy term), variant (variation attributes), and image_url (medium-size featured image).

1.0.10

• Tracker script now carries attributes recognized by popular WordPress optimization / caching plugins (data-no-optimize="1", data-no-defer="1", data-no-minify="1", data-cfasync="false") so the tracker is not bundled, deferred, or combined by those plugins. Required for correct pageview timing on landing-page templates (FunnelKit, Elementor) where caching plugins otherwise delay execution until first user interaction. If you previously had to add /t/s.js to your caching plugin's JS Excludes list, you can now remove that entry - though leaving it does no harm.

1.0.9

• Extended user matching for CAPI: server-side Purchase POST now carries the full WooCommerce billing record plus optional date-of-birth, gender, and WP user ID (external_id) for cross-platform identity matching across Facebook, Google Ads Enhanced Conversions, GA4 Measurement Protocol, and TikTok.
• Checkout email field now harvests live billing form values (phone, first/last name, address, city, state, postcode, country) so Identify events carry full identity before submit.
• Logged-in WP user profile fields are prefilled into the identity payload on the WooCommerce checkout page.
• No new permissions, no database migration. Backwards-compatible with v1.0.8 in case of a partial deployment.

1.0.8

• Tracker now skips admin context (wp-admin, admin-ajax, customizer, block editor). Storefront tracking unaffected.

1.0.7

• Checkout email capture (Identify) is now debounced - waits 2.5 seconds of typing stillness AND a stricter email-format validation before firing. Typos that customers correct quickly no longer create phantom user entries. Includes a beforeunload/pagehide flush so tab-close mid-typing doesn't lose the email entirely.

1.0.6

• Hook change: cookie persistence now fires on woocommerce_new_order instead of woocommerce_checkout_order_processed. Fixes FunnelKit upsell purchases not stitching into the same session as the front-end product purchase - FK upsell orders are created programmatically via FK's processor (not the standard WC checkout submit path), so the old hook missed them entirely. The new hook fires for all order creations and the existing empty-cookie gate skips admin/REST/cron orders cleanly.

1.0.5

• Session stitching fix - Purchase events now carry the customer's anonymous ID (_evid) and click cookies (_fbp/_fbc/gcl*/_ttclid/_ga) captured at checkout submit time. Rybbit will now stitch server-side Purchase into the original browsing session, and FB / Google Ads / TikTok CAPI receive real click attribution directly from cookies.
• Cookies are persisted as WC order meta during woocommerce_checkout_order_processed (HPOS-safe), so even Purchase events fired hours or days later (manual admin payment verification, async webhooks) retain the original visit attribution.
• Tracker script tag changed from "async defer" to "defer" - fixes InitiateCheckout race where the tracker JS could execute before the footer-emitted window.tmWooCheckout global was set. PageView still fires immediately after DOM ready, just slightly later (negligible).

1.0.4

• Server-side Purchase events now include the plugin's API key as a Bearer token. The TrueMetriks worker recognizes authenticated server-to-server events and skips browser-targeted bot filtering for them - eliminates the false-positive drop that was losing Purchase events at the analytics backend.
• Browser-side tracker (PageView etc.) still runs through full bot detection unchanged.

1.0.3

• Fix: server-side Purchase events were being silently dropped by Rybbit's bot detection due to missing browser-typical headers (Accept-Language, Accept, Accept-Encoding). Now sent explicitly in wp_remote_post calls, restoring conversions to ClickHouse and CAPI.
• Set explicit TrueMetriksPlugin user-agent on outbound conversion POSTs (avoids triggering Chrome-specific sec-fetch-site bot scoring).
• Added per-gate error_log diagnostics for InitiateCheckout so failures on FunnelKit page detection are visible (look for "[TM] inject_initiate_checkout:" entries).

1.0.2

• Diagnostic release - adds verbose error_log() statements (look for "[TM]" prefix) and per-order WC notes for Purchase fire outcome.
• Purchase tracking now hooks three actions (woocommerce_order_status_changed, woocommerce_payment_complete, woocommerce_thankyou) with order-meta dedup, so FunnelKit and non-standard gateway flows are all covered.
• Initiate Checkout moved to wp_footer with FunnelKit page detection (wfacp_is_checkout_page) for reliable output timing.
• wp_remote_post for Purchase now waits for the response (blocking=true) so success/failure is captured in WC order notes.

1.0.1

• Switched Purchase tracking to a single universal woocommerce_order_status_changed hook (catches FunnelKit funnels, upsells in both modes, manual admin orders, subscription renewals).
• Purchase event now fires server-side at the moment of order status change - no longer depends on customer reaching a thank-you page (fixes lost conversions when customer closes tab during FunnelKit upsell flow).
• Added client-side Identify event on checkout email entry for cross-session attribution.
• Removed FunnelKit-specific toggle (no longer needed - WC hook covers FK orders too).
• Switched InitiateCheckout to woocommerce_checkout_init for FunnelKit compatibility.
• Purchase Hook now handles processing and completed transitions cleanly with HPOS-safe order meta dedup.

1.0.0

• Initial release.