Ustun Conversion Tracking for WooCommerce
Set up GA4, Meta Pixel and Google Ads conversion tracking for WooCommerce in minutes — then verify the events actually fire.
Use with caution
Ustun Conversion Tracking for W… works, but test it on a staging site before relying on it in 2026. Was last updated 3 months ago, and scores 55/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Ustun Conversion Tracking f… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| conversion tracking | >100 |
| ga4 | >100 |
| google ads | >100 |
| Meta Pixel | >100 |
| woocommerce | >100 |
About Ustun Conversion Tracking for WooCommer…
From the official readme · v1.7.2Description
Most tracking plugins set up your pixels. Conversion Tracking Kit also proves they work.
“Meta reports 14 conversions, WooCommerce has 19 orders, Google Ads says 3 — which one is right?” Conversion Tracking Kit exists to answer that question.
- Guided setup wizard — paste your GA4 Measurement ID, Meta Pixel ID and Google Ads Conversion ID; done in about 3 minutes.
- Conflict protection, per platform — scans your plugins and homepage first. A conflict pauses only the platform it actually affects (the rest keep tracking), and nothing ever double-fires. You choose: take over, or audit-only.
- Setup test — one click verifies the scripts load and tracking requests actually leave the browser, with deep links to GA4 DebugView and Meta Test Events.
- Verify Setup (live) — browse any page of your site while the plugin watches real conversion beacons — phone, WhatsApp, form — and shows a live check per action. Works even when GTM or another plugin manages your tags.
- Orders vs. events — a dashboard card compares your recent orders against the purchase events that actually fired; refunded and cancelled orders are excluded on both sides.
- Conversions by channel — see where your conversions really came from: Google Ads, Meta, referral — and organic search, which the ad platforms never credit.
- Purchase recovery — an order only counts as tracked once the browser confirms the event went out; missed purchases retry on the customer’s next visit, deduplicated so nothing is counted twice.
- Safe by default — purchase deduplication, Google Consent Mode v2, a Meta Pixel consent gate (the pixel stays muted until your banner reports marketing consent), variation-aware add to cart, admin traffic excluded, staging sites never fire events.
The free version tracks view_item, add_to_cart, begin_checkout and purchase for GA4, Meta Pixel and Google Ads.
External services
This plugin is a conversion-tracking tool, so by design it can load the official tracking libraries of the advertising platforms you choose to connect. Nothing is loaded until you enter the corresponding ID in the setup wizard, and tracking is additionally gated by Google Consent Mode v2, admin exclusion and staging detection.
Google (Google Analytics 4 and Google Ads — gtag.js)
When you enter a GA4 Measurement ID (G-…) and/or a Google Ads Conversion ID (AW-…), the plugin loads Google’s gtag.js library from https://www.googletagmanager.com and sends data to Google. What is sent and when: on each page view, and on shop events (view_item, add_to_cart, begin_checkout, purchase), it sends the configured ID(s) together with the event name and its parameters — for example page URL, referrer, product identifiers, transaction ID, order value and currency — subject to the visitor’s consent state. This is used to measure analytics and ad conversions.
Google terms of service: https://policies.google.com/terms — Google privacy policy: https://policies.google.com/privacy
Meta Pixel (Facebook — fbevents.js)
When you enter a Meta Pixel ID, the plugin loads the Meta Pixel library fbevents.js from https://connect.facebook.net and sends data to Meta. What is sent and when: on each page view (PageView) and on shop events (ViewContent, AddToCart, InitiateCheckout, Purchase), it sends the Pixel ID together with the event name and its parameters — for example content identifiers, value and currency — plus standard browser data Meta collects (such as IP address and user agent). When JavaScript is disabled, a fallback tracking image is requested from https://www.facebook.com/tr. This is used to measure ad conversions.
Meta terms of service: https://www.facebook.com/legal/terms — Meta privacy policy: https://www.facebook.com/privacy/policy — Meta Business Tools terms: https://www.facebook.com/legal/terms/businesstools
Showing a cookie banner and collecting the legally required consent for these services remains the responsibility of the site owner; this plugin is not a consent-management plugin.
Frequently asked questions
Will Conversion Tracking Kit duplicate my existing tracking?
No — that is the #1 mistake it is built to prevent. Before printing anything, Conversion Tracking Kit scans your active plugins and your homepage for existing GA4, Meta Pixel, Google Ads and GTM code. If it finds any, it will not output a single script until you either remove the conflicting source or switch to audit-only mode.
Do I need API keys or access tokens?
No. The free version only needs the public IDs you already have: a GA4 Measurement ID (G-…), a Meta Pixel ID (a number) and/or a Google Ads Conversion ID (AW-…).
What exactly does the setup test verify?
It verifies that the tracking scripts load on your page and that the browser actually fires network requests to Google and Meta. It does not (and cannot, without API credentials) confirm platform-side receipt — for that, the test screen links you straight to GA4 DebugView and Meta Test Events so you can watch the events arrive yourself.
Does it work with consent / cookie plugins?
Yes. Conversion Tracking Kit prints a Google Consent Mode v2 default block before any Google tag. When a known consent plugin (CookieYes, Complianz, Cookiebot, Borlabs, Moove, Real Cookie Banner, iubenda, Termly) is active, consent defaults to denied and your consent plugin stays in charge.
My cookie banner is custom / not on the known list — what happens?
Unrecognized banners cannot be auto-detected, so the automatic default falls back to granted. The dashboard has a “Consent Mode default” setting to override this: choose “always start denied” if your banner sends Google Consent Mode updates itself. Showing a banner and collecting legally valid consent (GDPR/KVKK) remains the site owner’s responsibility — this is not a consent-management plugin.
Why are no events tracked on my staging site?
By design. When the site URL looks like a staging or local environment (localhost, .test, .local, “staging”), Conversion Tracking Kit fires nothing so test traffic never pollutes your real store data.
Why did the purchase event not fire for some orders?
The purchase event fires on the order received (thank-you) page. If the customer never reaches that page (closed the tab, payment app redirect failed) or an ad blocker intervened, the event is missed for that visit — the dashboard card shows you exactly how many orders this affected. Since 1.6.9 the plugin retries automatically on the customer’s next visit to the thank-you page within 7 days (deduplicated platform-side, so nothing is ever counted twice). If the customer never returns at all, that order stays unrecoverable from the browser — recovering it requires sending the conversion from…
Why does Google Ads only receive the purchase event?
By design. Google Ads optimizes bidding on conversions, and for a store the conversion is the purchase — feeding it every add_to_cart as a “conversion” would pollute your conversion column and mislead smart bidding. The full funnel (view_item, add_to_cart, begin_checkout, purchase) still goes to GA4 and Meta, and you can build Ads audiences from the linked GA4 property.
Changelog
Purchases blocked by ad blockers or lost to closed tabs are no longer gone forever — the plugin now retries on the customer's next visit, with platform-side deduplication preventing double counting.
1.7.2
- Google for WooCommerce (Google Listings & Ads) is no longer treated as a conflict just for being active: its global site tag is remarketing/audience only and does not duplicate purchase conversions. Merchant Center stores no longer lose their Ads tracking the moment the plugin is installed.
- Same conversion action = no conflict: when Google for WooCommerce’s Ads conversion action matches the ID + label configured here (the wizard’s import suggests exactly that), Google Ads deduplicates by order number and each sale is counted once — the scanner now says so instead of pausing Google Ads.
- Smarter page scan for AW- tags: a plain AW- config (remarketing) owned by Google for WooCommerce is informational; a real conversion call (send_to with a conversion label) from an unknown source is still flagged as a conflict.
1.7.1
- Fix: the purchase confirmation now waits for EVERY connected platform’s library before reporting (up to 12 seconds). Google’s libraries usually load faster than Meta’s, and the early report could log a purchase as “ga4,gads” even though the Meta Pixel fired seconds later — the pixel itself was never affected, only the dashboard’s platform list. If a library is blocked or the tab closes, the confirmation still goes out with what actually loaded.
1.7.0
- Per-platform conflict lock: a conflict now only pauses the platforms it actually affects. Example: Facebook for WooCommerce fires the Meta Pixel — Conversion Tracking Kit now pauses only its own Meta Pixel and keeps GA4 and Google Ads tracking, instead of pausing everything. A GTM container still pauses all platforms (its contents cannot be inspected). The dashboard shows exactly which platforms are paused and which keep running.
- Meta Pixel consent gate: Google Consent Mode only governs Google tags, so the Meta Pixel now gets its own consent handling. When the consent default is “denied”, the pixel starts muted (fbq consent revoke — events are queued, not lost) and a new consent bridge enables it the moment your banner reports marketing consent. Supported signals: WP Consent API, CookieYes, Complianz, Cookiebot.
- Variable products: add_to_cart now reports the chosen variation (SKU preferred, variation price included) instead of the parent product — what catalog and dynamic ads actually match on.
- Orders vs. events card is now refund-aware: an order cancelled or refunded after its purchase event fired no longer counts as tracked, so cancellations can never mask genuinely missed events.
1.6.9
- Purchase recovery: an order is now only marked “tracked” after the browser CONFIRMS the tracking libraries actually loaded and the purchase event went out. If an ad blocker killed the scripts or the tab closed mid-load, the thank-you page silently retries on the customer’s next visit (within 7 days) instead of losing the conversion forever. Platform-side deduplication (transaction_id for GA4/Google Ads, eventID for Meta) guarantees no double counting.
- The “orders vs. purchase events” dashboard card is now backed by browser-confirmed events only, so the number you see is the number that really reached the platforms’ endpoints from the browser.
1.6.8
- Fix: bundled translations (Turkish) now actually load on customer sites — the explicit textdomain loading was removed in an earlier compliance pass, which silently left the whole admin UI in English.
- Fix: begin_checkout no longer re-fires on every checkout page reload — it fires once per browser session (again only if the cart total changed).
- New: “Include shipping and tax in the purchase conversion value” setting — untick it to report net product revenue to the ad platforms (common ROAS preference).
- New: the scanner now warns when the homepage contains a cookie banner it does not recognize (hosted CMPs like OneTrust/Usercentrics, hand-built banners) and points to the Consent Mode default setting; sites using the WP Consent API standard get the same hint.
1.6.7
- New: “Consent Mode default” setting on the dashboard — sites whose cookie banner is custom or not on the known-plugin list can now force the Google Consent Mode v2 default to denied (or granted) instead of relying on auto-detection.
- Consent plugin auto-detection now also recognizes Real Cookie Banner, iubenda and Termly.
- FAQ: documented the browser-side tracking limits honestly (missed thank-you pages, why Google Ads only receives purchase).
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Ustun Conversion Tracking for… alternatives
All conversion tracking plugins →
FAQ
Ustun Conversion Tracking for WooCo…: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 5, 2026
Is Ustun Conversion Tracking for W… free?
Yes. Ustun Conversion Tracking for W… is free to download and use from the official WordPress.org plugin directory.
Is Ustun Conversion Tracking for W… safe to use in 2026?
Ustun Conversion Tracking for W… works, but test it on a staging site before relying on it in 2026. Was last updated 3 months ago, and scores 55/100 on our health check.
How many websites use Ustun Conversion Tracking for W…?
Ustun Conversion Tracking for W… is active on <10 WordPress websites and has been downloaded 413 times since it launched in June 2026. It was downloaded 52 times in the last 30 days.
Does Ustun Conversion Tracking for W… work with WordPress 7.1?
Ustun Conversion Tracking for W… is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Ustun Conversion Tracking for W… need?
Ustun Conversion Tracking for W… requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Ustun Conversion Tracking for W… last updated?
The latest version, 1.7.2, was released on July 14, 2026 (3 months ago).
Who makes Ustun Conversion Tracking for W…?
Ustun Conversion Tracking for W… is developed and maintained by abdullahustun.
What are the best alternatives to Ustun Conversion Tracking for W…?
The most popular alternatives to Ustun Conversion Tracking for W… are Pixel Manager for WooCommer… (40K+ installs), CallRail Phone Call Tracking (10K+ installs) and Conversios (10K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
