Advanced Pixel for Barion
| 开发者 | mrdarkside |
|---|---|
| 更新时间 | 2026年5月12日 00:03 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
pageView automatically for fraud prevention and basic analytics.
Full Tracking (optional): Tracks all mandatory e-commerce events per the Barion Pixel documentation:
- contentView - Product page views
- addToCart - Add to cart actions (client-side, compatible with page caching)
- initiateCheckout - Checkout page views
- purchase - Completed orders with full revenue tracking
- setEncryptedEmail - Encrypted billing email for user identification
- CookieYes
- Complianz
- Real Cookie Banner
- GDPR Cookie Compliance (Moove)
- Cookie Notice by dFactory
- English (default)
- Hungarian (hu_HU)
- Czech (cs_CZ)
- Slovak (sk_SK)
- German (de_DE)
- Croatian (hr)
- Romanian (ro_RO)
- Slovenian (sl_SI)
- Serbian (sr_RS)
- Base Pixel with automatic pageView tracking
- Full e-commerce event tracking with all required fields
- WP Consent API integration for universal cookie consent support
- Client-side add-to-cart tracking (compatible with page caching)
- Variable product support (tracks variation prices)
- Duplicate purchase prevention
- Debug mode with console logging
- Detects other plugins loading bp.js to avoid double-loading
安装:
- Upload the
advanced-pixel-for-barionfolder to/wp-content/plugins/ - Activate the plugin through the 'Plugins' menu in WordPress
- Go to Settings > Barion Pixel and enter your Barion Pixel ID
- Optionally enable or disable Full Pixel Tracking
- WordPress 5.0 or higher
- PHP 7.2 or higher
- WooCommerce 5.0 or higher (for full event tracking)
- WP Consent API for universal cookie consent support
- Any WP Consent API compatible cookie plugin (CookieYes, Complianz, etc.)
常见问题:
Do I need WooCommerce?
The Base Pixel (pageView) works without WooCommerce. Full event tracking (contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail) requires WooCommerce.
I already use the Barion Payment Gateway plugin. Will this conflict?
No. The Barion Payment Gateway is a payment processor only — it doesn't implement Barion Pixel event tracking. Both plugins coexist perfectly. If both have a Pixel ID configured, Advanced Pixel for Barion detects that bp.js is already loaded and skips re-loading it.
Which cookie consent plugins are supported?
All plugins that implement the WP Consent API standard: CookieYes, Complianz, Real Cookie Banner, GDPR Cookie Compliance (Moove), Cookie Notice by dFactory, and others. Direct fallback integration with Cookie Law Info is also built in.
What is the difference between Base Pixel and Full Tracking?
Base Pixel loads bp.js and fires pageView on every page. This is used by Barion for fraud prevention and basic analytics. Full Tracking adds e-commerce events (product views, add to cart, checkout, purchase) that enable marketing analytics and may qualify your store for lower Barion commission rates.
Can I use only the Base Pixel?
Yes. Just uncheck "Enable Full Pixel Tracking" in the settings. The base pixel will still load and fire pageView events.
How does the plugin handle page caching?
The addToCart event uses client-side JavaScript instead of PHP sessions, so it works correctly with all page caching setups (WP Super Cache, W3 Total Cache, LiteSpeed, WordPress.com hosting, etc.). Other events fire on dynamic pages that are not cached.
更新日志:
- Fix: emails containing
+in the local part (e.g.alice+tag@example.com), or with TLDs longer than four letters (e.g..museum,.online), were rejected by bp.js withFormat of e-mail address or hash is invalid. The plugin now SHA-1 hashes the email client-side (via the Web Crypto API) before passing it to bp.js, which bypasses bp.js's restrictive internal email regex. The Barion Pixel API explicitly supports pre-computed SHA-1 hashes.
- Fix:
setEncryptedEmailwas firing multiple times on a single checkout page load (thechange+blurpair plus theupdated_checkoutrebind caused duplicates). - Fix: bp.js rejected partial values (e.g.
x@y) with error 12 (Format of e-mail address or hash is invalid in setEncryptedEmail). The email is now validated against the HTML5 spec for valid email addresses before being sent; pre-computed SHA-1 hashes are also accepted, matching the Barion Pixel API reference. - Fix: aligned the bp.js call with the Barion documentation —
bp('identity', 'setEncryptedEmail', ...)(previously'identify'). - setEncryptedEmail now fires once for logged-in users on checkout load, and once per distinct, valid email entered into the billing field (no more
blurhandler, idempotent rebinding via a data attribute).
- Fix: events script (contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail) was never printed because it was enqueued after
wp_print_footer_scriptshad already run. - New:
setEncryptedEmailnow also fires when the customer enters their email on the checkout page (and on checkout load for logged-in users), as required by the Barion Pixel API reference. - Fix: cookie consent auto-detection (WP Consent API and Cookie Law Info) now runs after
DOMContentLoaded, so it can see globals defined by consent plugins that load later in the page.
- Initial release
- Base Barion Pixel (pageView) implementation
- Full event tracking: contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail
- WP Consent API integration (supports CookieYes, Complianz, Real Cookie Banner, and others)
- Cookie Law Info fallback integration
- Admin settings panel with debug mode
- Client-side addToCart tracking (compatible with page caching)
- Variable product support (tracks variation prices)
- Duplicate purchase prevention
- bp.js double-load detection