Carticy Conversions for WooCommerce
Accurate GA4, Google Ads, and Meta Pixel tracking for WooCommerce, measured from the order-paid event so no sale goes uncounted — with consent built in and setup in minutes.
Your thank-you page misses conversions every day — abandoned redirects, ad blockers, Safari, consent banners. Track from the order instead, and stop under-counting what your ads actually earned.
Also available as a free lite version on WordPress.org →
- 7-day money-back guarantee
- Last updated July 6, 2026
Key Highlights
Discover what makes this plugin stand out
1
Tracked from the order, not the thank-you page
Most tracking fires on the thank-you page, which silently misses every abandoned redirect, ad-blocked pixel, and Safari session. Carticy Conversions records the purchase from WooCommerce's authoritative order-paid event, so the conversion is counted even when the customer never comes back — classic, shortcode, and block (Store API) checkout alike.
2
Guided setup in minutes, no developer
Paste your IDs with an inline "Where do I find this?" walkthrough and real screenshots for every field. The plugin detects existing tags so you never add a duplicate pixel, and it verifies tracking on a real purchase before showing a green check — never a fake one.
3
Consent-respecting by design
Browser and server events are gated on real consent — WP Consent API, Google Consent Mode v2, and first-party signals — with per-service control, a per-order consent audit trail, IP anonymization, and retention. GDPR tooling included, with honest claims only.
Screenshots
See the plugin in action
1 of 5
Features Overview
Features
Description
Tracked from the order, not the thank-you page
Purchases are recorded from WooCommerce's woocommerce_payment_complete and paid-status hooks, with idempotency per order, event type, and destination — so a conversion fires once even across webhooks, cron, and page reloads, and never on an unpaid order.
GA4, Google Ads & Meta Pixel
Send events through direct browser tags or a ready-made GTM container. GA4 carries value, currency, and transaction_id; Meta Pixel and CAPI share a byte-identical event ID; Google Ads conversions fire with the order id — so client and server collapse to one conversion per platform.
Server-side CAPI & GA4 Measurement Protocol (Pro)
Meta Conversions API and GA4 Measurement Protocol fire from your server straight from the order: 0 KB of front-end JavaScript, immune to ad blockers and Safari, queued with automatic retries — and still hard-gated on the stored per-order consent.
Higher Meta Event Match Quality (Pro)
Server-side conversions carry hashed Advanced Matching data — email, phone, name, city, and state — plus durable first-party identifiers: a self-generated _fbp and a first-party visitor ID used as Meta external_id, set server-side so they survive Safari's ITP and ad blockers. More and better identifiers means Meta matches more of your conversions to real accounts, lifting Event Match Quality — and the Home dashboard estimates your match-key coverage from real recent orders.
Payment-gateway accuracy
Reconciles WooCommerce paid orders against tracked purchases, gateway by gateway, and names any order that was missed. The "no purchases missed" claim — computed from your real orders, never asserted.
Consent & GDPR tooling
Multi-source consent intake (WP Consent API, Google Consent Mode v2, a first-party bus, and a data-driven cookie/JS-global adapter) collapses to one per-order record. Tri-state gating sends only on explicit consent, with a per-order audit trail, WordPress exporter and eraser, IP anonymization, and retention.
Refunds & subscriptions
GA4 refund events and WooCommerce Subscriptions renewals are tracked server-side with correct provider semantics and unique transaction IDs, reusing the identity captured at the original order.
Existing-tag detection
Scans your store for GA4, Google Ads, and Meta tags and GTM containers added outside the plugin, and helps you attach, replace, or keep both — so you never accidentally fire two pixels and double-count.
Works alongside Facebook for WooCommerce
Keep the official Facebook for WooCommerce plugin for its catalog, Shop, and product feed, and hand Meta event tracking to Carticy with one click. The takeover switches off that plugin's own Meta Pixel and Conversions API events — removing the duplicate pixel and the synchronous server call it runs during add to cart — while its catalog sync keeps working. Carticy fires the Meta Pixel in the browser, and the Conversions API on Pro. The option appears once your Meta Pixel is configured, and it's fully reversible.
Never slows your storefront
The storefront script is deferred and excluded from optimizers by default, and server events add 0 KB. Crucially, server-side conversions are queued and sent in the background by WooCommerce's Action Scheduler — never a synchronous server call while the shopper waits — so tracking adds no latency to add to cart, cart, or checkout. Fully HPOS-compatible, with classic, shortcode, and block (Store API) checkout.
Pricing Plans
Choose the plan that fits your needs
Most Popular
Annual License
Server-side tracking that recovers the conversions browser tracking misses.
$79.99 Year
- Everything in Free, plus:
- Meta Conversions API (server-side)
- GA4 Measurement Protocol (server-side)
- Recover 20–40% of conversions ad blockers & redirects lose
- Fires from your server — 0 KB added, can’t be blocked
- Still consent-gated, even for async and cron sends
- Reliability:
- Automatic retries with a visible delivery log
- Deduplicated against browser events by order ID
- Support & updates:
- 1 year of updates
- 1 year of priority support
- 14-day money-back guarantee
Lifetime License
Best value — pay once, server-side tracking forever.
$239.99 One-Time
- Everything in Annual, plus:
- Lifetime updates (never pay again)
- Lifetime priority support
- Server-side delivery:
- Meta Conversions API
- GA4 Measurement Protocol
- Automatic retries with a visible delivery log
- Best long-term value
Frequently Asked Questions
Get answers to common questions
Thank-you-page tracking misses any sale where the shopper never returns — abandoned redirect-gateway payments, ad-blocked pixels, Safari sessions, closed tabs. Carticy Conversions records the purchase from WooCommerce’s authoritative order-paid event, so the conversion is counted regardless of what happens in the browser.
Free covers browser-side tracking for GA4, Google Ads, and the Meta Pixel, consent handling, the payment-gateway accuracy check, duplicate-tag detection, and live verification. Pro adds server-side delivery — Meta Conversions API and GA4 Measurement Protocol — that recovers the conversions ad blockers and redirect checkouts lose, with hashed Advanced Matching for higher Event Match Quality.
No. Direct mode installs and fires the tags for you with no Tag Manager needed. If you already run GTM, the plugin prepares a ready-made container file to import — it never silently edits or publishes your container.
No plugin can make your store GDPR compliant — that is the store’s responsibility. What Carticy Conversions gives you is the tooling: consent-gated tracking (WP Consent API, Consent Mode v2, and first-party signals), a per-order consent record, IP anonymization, retention, and WordPress export and erase support. We say consent-respecting and consent-gated, never “compliant.”
Yes. Every server send reads the stored per-order consent record at send time and hard-blocks on denial — even for renewals and refunds processed by cron hours later. A visitor who declined marketing is never sent to Meta or Google, browser or server.
Yes, on Pro. Every server-side conversion carries hashed Advanced Matching data — email, phone, name, city, and state — plus durable first-party identifiers: a self-generated fbp and a first-party visitor ID used as Meta externalid, set from your server so they keep matching even when Safari’s ITP or an ad blocker drops the browser pixel. More and better identifiers is exactly what Event Match Quality rewards, and the Home dashboard estimates your match-key coverage from your real recent orders.
No. Within the plugin, every event carries the order id as the dedup key, so client and server collapse to one conversion per platform. For tags added outside the plugin, the existing-tag detector warns you and offers to attach, replace, or keep both — you decide.
Yes. If that plugin is active, Carticy detects it and offers a one-click takeover of Meta event tracking: it turns off the official plugin’s Meta Pixel and Conversions API events — which otherwise double-count with Carticy and add a synchronous server call to add to cart — while leaving its catalog sync, Shop, and product feed untouched. The takeover only appears once your Meta Pixel is set up in Carticy, and you can hand tracking back to Facebook at any time.
No. Client-side tags are loaded asynchronously and deferred, and the plugin never makes a blocking outbound request while the shopper waits. Pro server-side events (Meta Conversions API, GA4 Measurement Protocol) are queued and sent in the background by WooCommerce’s Action Scheduler, off the storefront request path — so unlike setups that fire a synchronous server call during add to cart, Carticy Conversions adds no latency to add to cart, cart, or checkout. Server-generated events also add 0 KB of front-end JavaScript and cannot affect Core Web Vitals, and the storefront script self-excludes from cache and optimizer plugins.
Yes. Because purchases are tracked from server-side order-paid hooks, classic, shortcode, and block checkout all work identically — including the abandoned-return case where the customer closes the tab after paying.