Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

PixLedger - WooCommerce Conversion Tracking for Meta, GA4 & GTM

开发者 mentotex
更新时间 2026年9月3日 04:47
PHP版本: 8.1 及以上
WordPress版本: 7.1
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

google tag manager woocommerce tracking ga4 meta pixel consent mode

下载

1.6.4 1.6.5

详情介绍:

PixLedger fires your Meta Pixel, GA4, and GTM events AND logs every single event locally — so you always know what was tracked, what failed, what was blocked by consent, and why. The Event Intelligence Layer 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. What PixLedger Tracks WooCommerce Events Supported Providers Key Features Event Log A 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. Event Configuration Panel Choose exactly which events PixLedger tracks. Enable or disable any event individually. Defaults are sensible out of the box — turn off what you don't need, enable what you do. Consent Mode v2 Built-in Consent Mode v2 support. Events are blocked at the pipeline level when consent is denied — not as an afterthought. The Event Log shows blocked events with the specific consent category that denied them. Tag Detection PixLedger 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. Visitor ID Tracking Every 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 — clickable journey view available in Pro. Attribution Capture UTM parameters, click IDs (fbclid, gclid, ttclid, msclkid), landing page, and referrer are captured on every page load and saved to the order on purchase. Rate Limiting Configurable rate limiting prevents spam bots from flooding your event log. Default: 5 same-event repetitions per visitor per minute. Adjustable in Settings. Works on Any WordPress Site 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. Privacy & GDPR PixLedger Pro PixLedger Pro adds server-side tracking, advanced analytics, and journey intelligence: Learn more at pixledger.com.

安装:

Minimum Requirements Automatic Installation
  1. Go to Plugins → Add New in your WordPress admin
  2. Search for PixLedger
  3. Click Install Now and then Activate
Manual Installation
  1. Download the plugin zip file
  2. Go to Plugins → Add New → Upload Plugin
  3. Upload the zip file and click Install Now
  4. Click Activate Plugin
After Activation
  1. Go to PixLedger → Settings
  2. Enter your Meta Pixel ID, GA4 Measurement ID, and/or GTM Container ID
  3. Enable the providers you want to use
  4. Configure the Event Configuration panel to choose which events to track
  5. Visit your store and check PixLedger → Event Log to confirm events are firing

屏幕截图:

  • Consent Mode v2 — set default consent state per category (analytics storage, ad storage, ad user data, ad personalization).
  • Event Configuration — enable or disable page, navigation, click, and interaction events individually.
  • Event Configuration — form, site search, and user account events, each with a plain-language trigger description.
  • Event Configuration — user account and WooCommerce events, including Add to Cart, Remove from Cart, and Cart View.
  • Event Configuration — full WooCommerce funnel coverage: Begin Checkout, Add Payment Info, Coupon Applied, Purchase, Order Refunded.
  • Custom Events and Advanced settings — track your own events via data attributes or the JS API, plus configurable rate limiting and retention.
  • Event Log — real-time sent / failed / blocked / deduplicated counts with full filtering by provider, event, and status.
  • Event Payload viewer — inspect the exact JSON sent to each provider for complete conversion tracking transparency.

升级注意事项:

1.6.5 Plugin name and tags updated for clarity — no functional changes. Safe update for all users. 1.6.4 Compliance update: all plugin prefixes changed to pixledger_, database tables renamed to wp_pxlg_*. All events now fully functional — no locked features. Safe fresh install; not an in-place upgrade (no existing user data). 1.6.3 Event retention is now fully unrestricted — configure any number of hours with no cap. Safe update for all users. 1.6.2 Event retention is now configurable in Settings (up to 30 days). External services documentation added. Safe update for all users. 1.6.1 Compliance release: WordPress.org Plugin Check fixes (output escaping, input sanitisation, query hardening). No functional changes — safe update for all users. 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. 1.2.0 Major update: universal WordPress events, Event Configuration panel, and 7 new WooCommerce events added. Update recommended for all users.

常见问题:

Do I need WooCommerce?

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.

Will PixLedger conflict with my existing Meta Pixel or GA4 setup?

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.

Why are some events showing as "Blocked" in the Event Log?

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".

What does the visitor ID look like and where is it stored?

The visitor ID is an anonymous string like pxl_a3f8c2d1b2e4f6a8 stored in a 90-day cookie and in the visitor_id column of the wp_pxl_events database table. It contains no personally identifiable information.

Are customer emails stored in plain text?

No. Customer emails are SHA-256 hashed before being stored. The hash is used for Meta Pixel advanced matching and GA4 enhanced conversions — both platforms accept hashed emails for customer matching.

How long are events kept in the database?

By default, PixLedger keeps events for 7 days (168 hours). You can change this in Settings → Advanced → Event retention — set any number of hours with no upper limit. A WP-Cron job runs hourly and automatically purges older records.

Can I disable specific events I don't need?

Yes. The Event Configuration panel in Settings lets you enable or disable any event individually. Disabling an event means it is never dispatched — no log row, no provider call, no database write.

Does PixLedger slow down my site?

No, when configured correctly. The frontend tracker script loads in the footer with defer, 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.

Where is the data stored?

All event data is stored in your own WordPress database in two tables: wp_pxl_events (all tracked events) and wp_pxl_attribution (UTM and click ID data per order). Your data never leaves your server — PixLedger does not have access to it.

What happens to my data if I delete the plugin?

All plugin data is removed on deletion — both database tables (wp_pxl_events and wp_pxl_attribution), all plugin options, and all scheduled cron jobs. This is handled by uninstall.php.

How do I test that Meta Pixel is working?

  1. Enter your Pixel ID in Settings and enable Meta Pixel
  2. Disable Consent Mode in Settings (for testing only)
  3. Visit your store as a logged-out visitor
  4. Open Meta Events Manager → Test Events tool
  5. Enter your store URL and browse — events should appear in real time

How do I test that GA4 is working?

  1. Enter your Measurement ID (G-XXXXXXXXXX) in Settings and enable GA4
  2. Open Google Analytics → Admin → DebugView
  3. Install the Google Analytics Debugger Chrome extension and enable it
  4. Browse your store — events appear in DebugView within 30 seconds

更新日志:

1.6.5 1.6.4 1.6.3 1.6.2 1.6.1 1.6.0 1.5.0 1.4.0 1.3.0 1.2.0 1.1.1 1.1.0 1.0.0