Advanced Pixel for Barion
| 开发者 | mrdarkside |
|---|---|
| 更新时间 | 2026年8月25日 22:37 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | 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
- Cookiebot
- Cookie Law Info (legacy banner)
- 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
- Automatic grantConsent and rejectConsent, required for Barion's Full Pixel approval
- 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.4 or higher
- WooCommerce 5.0 or higher (for full event tracking)
- WP Consent API, if your cookie banner is not read directly
- A cookie consent banner — Barion requires one before it approves a Full Pixel integration
屏幕截图:
常见问题:
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?
CookieYes, Complianz, Cookiebot and the legacy Cookie Law Info banner are read directly, with no extra plugin. Every other banner works through the WP Consent API plugin, including Real Cookie Banner, GDPR Cookie Compliance (Moove) and Cookie Notice by dFactory. Turn on Debug Mode to see which one the plugin found.
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. Full Tracking is also a condition of Barion's discounted Advanced package — see the question about fees below.
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 do I check that my events reach Barion?
Barion has no page that lists your events. The Barion admin gives you your Pixel ID (Barion Wallet > Merchant Management > Details), but it does not show incoming events.
You check the events in your browser instead. Enable Debug Mode in Settings > Barion Pixel, then open the browser console (F12). Every event the plugin sends appears with a [Barion Pixel] prefix.
Barion's own bp.js script also writes to the same console, and its message tells you your approval state:
Testing message— your pixel works, but Barion has not authorised it yet. Barion receives only the type of the event, not user data. Every new implementation starts here.Sending message— Barion reviewed and approved your implementation. Barion now receives the full data.
Will this plugin lower my Barion transaction fees?
Not on its own. Barion offers a discounted "Advanced" package for the Barion Smart Gateway, and a complete Full Pixel implementation with consent management is one of its conditions. Two things are important. First, you have to request the package from Barion — it is not applied automatically when you install a pixel. Second, Barion examines your implementation before granting it, and commercial conditions apply as well, for example your average cart size and your card mix. For the current conditions, see the Barion Smart Gateway page.
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:
grantConsentwas never sent on a site without the separate WP Consent API plugin, so Barion refused to approve the Full Pixel integration. Consent detection tried three sources in turn and stopped at the first match, and the last of them attached no listener at all. CookieYes, Complianz, Cookiebot and the legacy Cookie Law Info banner are now read directly, with no extra plugin. - Fix:
grantConsentwas also missed for a returning visitor who had already answered the banner, and on any site whose consent manager finished loading after the page did. The plugin now keeps looking for a consent manager for ten seconds after the page loads, rather than checking once. - New: the settings page warns when no consent manager can be reached, so a broken consent setup is visible before Barion refuses the integration rather than after.
- Fix: a fatal error on any site that runs the plugin without WooCommerce, once a Pixel ID was saved and Full Tracking was on. The footer event script called
is_product(), a function that only exists while WooCommerce is loaded, so the page died withCall to undefined function is_product(). The WooCommerce event hooks are now registered only when WooCommerce is active. The base pixel still loads without WooCommerce, as documented. This dates back to 1.0.0. - Fix: the note about a Pixel ID also being set in the Barion Payment Gateway plugin was shown in English in every language. It was reworded in an earlier release and the translations were never updated to match.
- Fix:
initiateCheckoutandsetEncryptedEmailnever fired on the WooCommerce Checkout block, which has been the default for new stores since WooCommerce 8.3. The plugin only listened for the classic checkout's PHP hooks and its#billing_emailfield, and the block has neither. It now reads the Cart and Checkout blocks' data store. Classic checkout behaviour is unchanged. - Fix:
addToCartnever fired on shop or category pages, on any store. The events script was only loaded on pages that already had an event queued, which no archive page does, so the add-to-cart listeners were never present where customers actually add to cart. This affected classic stores too, and dates back to 1.0.1. - Fix:
addToCartnow also works with the block product buttons used by the Product Collection block. These run on the Interactivity API and fire neither the classic jQuery event nor the block data store, so cart contents are now read from the WooCommerce Store API.
- Fix: the bundled Hungarian, Czech, Slovak, German, Croatian, Romanian, Slovenian and Serbian translations never loaded, so the settings screen stayed in English. WordPress only searches
wp-content/languages/pluginsunless a plugin registers its own directory, and the plugin never did. It now registerslanguages/oninit.
- Compatibility: tested against WordPress 7.0 and WooCommerce 11.0.
Requires PHPraised from 7.2 to 7.4. WordPress 7.0 dropped support for PHP 7.2 and 7.3, so 7.2 was no longer a version the plugin could run on.- No functional changes.
- 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: 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: 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