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).
1.6.6
New: interactive “Verify Setup” tool — open any page of your site and watch conversion tracking fire live, even when tracking is managed by Google Tag Manager or another plugin. Click a phone / WhatsApp / email link or submit a form and get a per-action ✓/✗ summary plus a live timeline of Google Ads, GA4 and Meta hits.
Verify tells real Google Ads conversions (label-carrying hits) apart from the base/remarketing tag, merges the multiple endpoints of a single conversion into one row, and warns when more than one GA4 property fires on the same page (likely double counting).
Verify follows you across pages for 30 minutes (admin-only, never set for visitors), so real journeys like homepage → contact page → form submit can be tested end to end. A floating pill shows it is live, with a one-click Stop.
1.5.1
The event log is now a fixed, performance-only rolling buffer: removed the retention filter so no limit is ever raised by payment, and every free feature works fully within it.
Reworded the dashboard upgrade hints so they only mention capabilities that genuinely require external resources (platform API comparison, server-side CAPI recovery, continuous monitoring and email alerts) — no locally available reporting is held back.
1.5.0
The plugin now focuses solely on online-sales (WooCommerce) conversion tracking, fully free and fully functional. Lead tracking (calls, WhatsApp, form submissions) has moved entirely to the separate Conversion Tracking Kit Pro plugin — no lead code ships in the free plugin anymore.
Unified all internal handles under a single, distinct prefix to avoid any chance of conflicts with other plugins.
Security: the self-hosted update channel now pins TLS verification and only accepts an update package served from the official domain, so a tampered manifest can never point WordPress at an off-site plugin zip.
1.4.0
New: “Conversions by channel” dashboard card — see where your tracked conversions came from (organic search, Google Ads, Meta, TikTok, direct, referral…), including organic search which ad platforms never credit. Captured first-party from referrer + click IDs; no external API.
1.3.0
Setup wizard refinements and clearer guidance through the GA4, Meta Pixel and Google Ads steps.
1.1.0
Extension hooks for add-ons (tracker filter, dashboard action, purchase action).
Event log: new “source” column (browser/CAPI) and per-order distinct purchase counting.
Automatic table migration after updates.
1.0.3
All database queries now use fully prepared statements (%i identifier placeholders); minimum WordPress raised to 6.2.
gtag.js loader is now properly enqueued (async) via wp_enqueue_script instead of a hardcoded script tag.
Plugin Check compliance pass.
1.0.2
Setup test: also detect Meta Pixel requests sent as POST to facebook.com/tr/ without a query string (large payloads) — fixes false “no request detected” for Meta.
1.0.1
Setup test: raised the resource timing buffer and added a PerformanceObserver stream so tracking requests are not missed on asset-heavy pages (false “no request detected” results).
