xpay✦ Commerce
Directory
WooCommerce plugins
Advanced Pixel for Barion
Advanced Pixel for Barion
Barion Pixel integration for WooCommerce with full e-commerce event tracking, cookie consent support, and WP Consent API compatibility.
Will this break my store?
What the WordPress.org registry says about keeping Advanced Pixel for Barion running.
Tested to 7.1
Tested against the WordPress branch in use today.18 days ago
7.4
Your host must be running at least this version.5.0
1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how Advanced Pixel for Barion is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
Not enough dataListing transparency
10 / 10Ratings
No one has rated this plugin on WordPress.org yet. That is a statement about the ratings page, not about the plugin — plenty of well-kept plugins never collect them.
Advanced Pixel for Barion adds Barion Pixel tracking to your WooCommerce store. It supports two modes:
Base Pixel (always active): Loads the Barion tracking script on all pages. Fires 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
Full Tracking is also one of the conditions of Barion’s discounted “Advanced” gateway package. You have to request that package from Barion, and Barion reviews your pixel implementation before granting it — installing this plugin does not change your fees on its own. See the FAQ below.
Cookie Consent
Barion requires a grantConsent event before it approves a Full Pixel integration. The plugin sends it automatically, and reads these consent managers directly, with no extra plugin:
- CookieYes
- Complianz
- Cookiebot
- Cookie Law Info (legacy banner)
For every other cookie banner, install the WP Consent API plugin. It is the WordPress standard for passing consent between plugins, and Real Cookie Banner, GDPR Cookie Compliance (Moove) and Cookie Notice by dFactory all support it. You can also wire your banner up by hand in a few lines.
Supported Languages
- 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)
Privacy
This plugin loads the Barion Pixel script (bp.js) from pixel.barion.com on all frontend pages. Page view and e-commerce event data is sent to Barion’s servers. On purchase completion, the billing email address is passed to bp.js which encrypts it with SHA1 before transmission — no plaintext email leaves your server.
Key Features
- 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
The Base Pixel (pageView) works without WooCommerce. Full event tracking (contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail) requires WooCommerce.
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.
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.
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.
Yes. Just uncheck “Enable Full Pixel Tracking” in the settings. The base pixel will still load and fire pageView events.
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.
A person at Barion performs this approval. Contact Barion when your implementation is complete.
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.
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.
Categories
Plugin details
Tags on WordPress.org
