Compliance update: all plugin prefixes changed to pixledger_, database tables renamed to wp_pxlg_*. All events now fully functional \u2014 no locked features. Safe fresh install; not an in-place upgrade (no existing user data).<\/p>","1.6.3":"
Event retention is now fully unrestricted \u2014 configure any number of hours with no cap. Safe update for all users.<\/p>","1.6.2":"
Event retention is now configurable in Settings (up to 30 days). External services documentation added. Safe update for all users.<\/p>","1.6.1":"
Compliance release: WordPress.org Plugin Check fixes (output escaping, input sanitisation, query hardening). No functional changes \u2014 safe update for all users.<\/p>","1.6.0":"
Major update: fixes duplicate GTM\/GA4 events on add-to-cart, fixes tag detection format bug, and adds Event Configuration panel with per-event enable\/disable toggles. Update recommended for all users.<\/p>","1.2.0":"
Major update: universal WordPress events, Event Configuration panel, and 7 new WooCommerce events added. Update recommended for all users.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3584518,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3584518,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3584518,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3584518,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.6.4"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Event Log<\/strong> \u2014 real-time log of every tracked event with status badges, provider, payload viewer, and filters","2":"Settings Page<\/strong> \u2014 configure Meta Pixel, GA4, GTM, Consent Mode, Event Configuration, and advanced options","3":"Event Configuration Panel<\/strong> \u2014 enable or disable individual events grouped by category","4":"Provider Detection<\/strong> \u2014 automatic detection of existing Meta Pixel, GA4, or GTM installations"}},"plugin_section":[],"plugin_tags":[193472,1005,207498,550,286],"plugin_category":[36,45],"plugin_contributors":[263797],"plugin_business_model":[],"class_list":["post-327912","plugin","type-plugin","status-publish","hentry","plugin_tags-ga4","plugin_tags-google-analytics","plugin_tags-meta-pixel","plugin_tags-tracking","plugin_tags-woocommerce","plugin_category-analytics","plugin_category-ecommerce","plugin_contributors-mentotex","plugin_committers-mentotex"],"banners":{"banner":"https:\/\/ps.w.org\/pixledger\/assets\/banner-772x250.png?rev=3584518","banner_2x":"https:\/\/ps.w.org\/pixledger\/assets\/banner-1544x500.png?rev=3584518","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/pixledger\/assets\/icon-128x128.png?rev=3584518","icon_2x":"https:\/\/ps.w.org\/pixledger\/assets\/icon-256x256.png?rev=3584518","generated":false},"screenshots":[],"raw_content":"\n PixLedger fires your Meta Pixel, GA4, and GTM events AND logs every single event locally \u2014 so you always know what was tracked, what failed, what was blocked by consent, and why.<\/p>\n\n The Event Intelligence Layer<\/strong><\/p>\n\n Every event that fires through PixLedger is recorded in your own database with a full audit trail: which provider received it, whether it was delivered successfully, whether it was blocked by consent, and the complete payload that was sent.<\/p>\n\n WooCommerce Events<\/strong>\n* ViewContent \u2014 product page visits\n* AddToCart \u2014 cart additions with product data\n* RemoveFromCart \u2014 cart removals\n* CartView \u2014 cart page visits\n* InitiateCheckout \u2014 checkout page visits\n* AddPaymentInfo \u2014 payment details entered\n* AddShippingInfo \u2014 shipping details entered\n* CouponApplied \u2014 discount codes applied\n* Purchase \u2014 completed orders with full order data\n* OrderRefunded \u2014 refunds issued\n* ProductReview \u2014 WooCommerce product reviews submitted<\/p>\n\n Universal WordPress Events (works on any WordPress site)<\/strong>\n* PageView \u2014 every frontend page load with page context\n* NotFound404 \u2014 404 errors with requested URL\n* OutboundLinkClick \u2014 clicks on external links\n* PhoneClick \u2014 clicks on tel: links\n* EmailClick \u2014 clicks on mailto: links\n* DownloadClick \u2014 clicks on downloadable files (PDF, ZIP, DOC, etc.)\n* FormSubmit \u2014 any form submission\n* UserLogin \u2014 user login events\n* UserRegister \u2014 new user registrations\n* CommentPosted \u2014 comment submissions\n* SearchPerformed \u2014 site search queries\n* SearchEmpty \u2014 searches with zero results<\/p>\n\n Custom Events<\/strong>\n* Declarative: add Event Log<\/strong>\nA real-time, searchable log of every event that fires on your site. See exactly what was tracked, by which provider, with what payload. Filter by provider, event name, status, or date. Paginated with bulk delete and auto-refresh.<\/p>\n\n Event Configuration Panel<\/strong>\nChoose exactly which events PixLedger tracks. Enable or disable any event individually. Defaults are sensible out of the box \u2014 turn off what you don't need, enable what you do.<\/p>\n\n Consent Mode v2<\/strong>\nBuilt-in Consent Mode v2 support. Events are blocked at the pipeline level when consent is denied \u2014 not as an afterthought. The Event Log shows blocked events with the specific consent category that denied them.<\/p>\n\n Tag Detection<\/strong>\nPixLedger detects if Meta Pixel, GA4, or GTM are already loaded by another plugin or your theme. It skips its own injection automatically to prevent duplicate events. Detection notices are shown in Settings.<\/p>\n\n Visitor ID Tracking<\/strong>\nEvery event is tagged with an anonymous visitor ID (90-day cookie) so you can trace a visitor's journey across sessions. Visible in the Event Log \u2014 clickable journey view available in Pro.<\/p>\n\n Attribution Capture<\/strong>\nUTM parameters, click IDs (fbclid, gclid, ttclid, msclkid), landing page, and referrer are captured on every page load and saved to the order on purchase.<\/p>\n\n Rate Limiting<\/strong>\nConfigurable rate limiting prevents spam bots from flooding your event log. Default: 5 same-event repetitions per visitor per minute. Adjustable in Settings.<\/p>\n\n PixLedger works with or without WooCommerce. Universal events (PageView, clicks, forms, search, user account events) fire on any WordPress site. WooCommerce ecommerce events load automatically when WooCommerce is detected.<\/p>\n\n PixLedger Pro adds server-side tracking, advanced analytics, and journey intelligence:<\/p>\n\n Learn more at pixledger.com<\/a>.<\/p>\n\n PixLedger connects to the following third-party services to deliver tracking events to advertising and analytics platforms. These connections only occur when the respective provider is enabled and configured in Settings.<\/p>\n\n PixLedger loads the Meta Pixel script ( PixLedger loads the GA4 script ( PixLedger loads the GTM container script ( No. PixLedger works on any WordPress site. WooCommerce ecommerce events (ViewContent, AddToCart, Purchase, etc.) only load when WooCommerce is active. Universal events (PageView, clicks, forms, search) work on any WordPress site.<\/p><\/dd>\n No. PixLedger detects if Meta Pixel, GA4, or GTM are already loaded by another plugin or your theme. It automatically skips its own script injection to prevent duplicate events. You'll see a notice in Settings explaining what was detected.<\/p><\/dd>\n Blocked events are events that were prevented from reaching the provider because the visitor denied consent. This is Consent Mode v2 working correctly. The status badge shows the specific consent category that was denied. To test the plugin without consent blocking, go to Settings and uncheck \"Enable Consent Mode\".<\/p><\/dd>\n The visitor ID is an anonymous string like No. Customer emails are SHA-256 hashed before being stored. The hash is used for Meta Pixel advanced matching and GA4 enhanced conversions \u2014 both platforms accept hashed emails for customer matching.<\/p><\/dd>\n By default, PixLedger keeps events for 7 days (168 hours). You can change this in Settings \u2192 Advanced \u2192 Event retention<\/strong> \u2014 set any number of hours with no upper limit. A WP-Cron job runs hourly and automatically purges older records.<\/p><\/dd>\n Yes. The Event Configuration panel in Settings lets you enable or disable any event individually. Disabling an event means it is never dispatched \u2014 no log row, no provider call, no database write.<\/p><\/dd>\n No, when configured correctly. The frontend tracker script loads in the footer with All event data is stored in your own WordPress database in two tables: All plugin data is removed on deletion \u2014 both database tables ( Added: TagDetector::get_detected_names() method for Settings page to retrieve plugin display names per tag type<\/p><\/li>\n Added: EventRegistry \u2014 central catalogue of all trackable events with per-event enable\/disable toggles<\/p><\/li>\nWhat PixLedger Tracks<\/h4>\n\n
data-pxl-event=\"EventName\"<\/code> to any HTML element \u2014 no code needed\n* Programmatic: pxl('track', 'EventName', { properties })<\/code> for developers<\/p>\n\nSupported Providers<\/h4>\n\n
\n
Key Features<\/h4>\n\n
Works on Any WordPress Site<\/h4>\n\n
Privacy & GDPR<\/h4>\n\n
\n
PixLedger Pro<\/h4>\n\n
\n
External Services<\/h3>\n\n
Meta Pixel<\/h4>\n\n
fbevents.js<\/code>) from connect.facebook.net<\/code> and sends ecommerce and page events to Meta on every relevant page load. This occurs only when Meta Pixel is enabled and a Pixel ID is configured. Data sent includes event names, page URLs, and hashed customer email (for advanced matching). No data is sent if Meta Pixel is disabled in Settings.<\/p>\n\n\n
Google Analytics 4<\/h4>\n\n
gtag.js<\/code>) from googletagmanager.com<\/code> and sends ecommerce and page events to Google Analytics on every relevant page load. This occurs only when GA4 is enabled and a Measurement ID is configured. Data sent includes event names, page URLs, and ecommerce data (product names, prices, order values). No data is sent if GA4 is disabled in Settings.<\/p>\n\n\n
Google Tag Manager<\/h4>\n\n
gtm.js<\/code>) from googletagmanager.com<\/code> and pushes events to the window.dataLayer<\/code> object. This occurs only when GTM is enabled and a Container ID is configured. The data pushed includes event names and ecommerce data in GA4 Enhanced Ecommerce schema. No script is loaded if GTM is disabled in Settings, or if GTM is already loaded by another plugin or your theme.<\/p>\n\n\n
Minimum Requirements<\/h4>\n\n
\n
Automatic Installation<\/h4>\n\n
\n
Manual Installation<\/h4>\n\n
\n
After Activation<\/h4>\n\n
\n
\n
Do I need WooCommerce?<\/h3><\/dt>\n
Will PixLedger conflict with my existing Meta Pixel or GA4 setup?<\/h3><\/dt>\n
Why are some events showing as \"Blocked\" in the Event Log?<\/h3><\/dt>\n
What does the visitor ID look like and where is it stored?<\/h3><\/dt>\n
pxl_a3f8c2d1b2e4f6a8<\/code> stored in a 90-day cookie and in the visitor_id<\/code> column of the wp_pxl_events<\/code> database table. It contains no personally identifiable information.<\/p><\/dd>\nAre customer emails stored in plain text?<\/h3><\/dt>\n
How long are events kept in the database?<\/h3><\/dt>\n
Can I disable specific events I don't need?<\/h3><\/dt>\n
Does PixLedger slow down my site?<\/h3><\/dt>\n
defer<\/code>, uses passive event listeners, throttles high-frequency events, and batches AJAX requests every 5 seconds (never one request per event). The performance impact is negligible.<\/p><\/dd>\nWhere is the data stored?<\/h3><\/dt>\n
wp_pxl_events<\/code> (all tracked events) and wp_pxl_attribution<\/code> (UTM and click ID data per order). Your data never leaves your server \u2014 PixLedger does not have access to it.<\/p><\/dd>\nWhat happens to my data if I delete the plugin?<\/h3><\/dt>\n
wp_pxl_events<\/code> and wp_pxl_attribution<\/code>), all plugin options, and all scheduled cron jobs. This is handled by uninstall.php<\/code>.<\/p><\/dd>\nHow do I test that Meta Pixel is working?<\/h3><\/dt>\n
\n
How do I test that GA4 is working?<\/h3><\/dt>\n
\n
1.6.4<\/h4>\n\n
\n
1.6.3<\/h4>\n\n
\n
1.6.2<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n