Title: Advanced Pixel for Barion Author: Gergely Csécsey Published: 19. März 2026 Last modified: 13. September 2026 --- Plugins suchen ![](https://ps.w.org/advanced-pixel-for-barion/assets/banner-772x250.png?rev=3638894) ![](https://ps.w.org/advanced-pixel-for-barion/assets/icon.svg?rev=3638894) # Advanced Pixel for Barion Von [Gergely Csécsey](https://profiles.wordpress.org/mrdarkside/) [Herunterladen](https://downloads.wordpress.org/plugin/advanced-pixel-for-barion.1.0.10.zip) [Live-Vorschau](https://de.wordpress.org/plugins/advanced-pixel-for-barion/?preview=1) * [Details](https://de.wordpress.org/plugins/advanced-pixel-for-barion/#description) * [Rezensionen](https://de.wordpress.org/plugins/advanced-pixel-for-barion/#reviews) * [Installation](https://de.wordpress.org/plugins/advanced-pixel-for-barion/#installation) * [Entwicklung](https://de.wordpress.org/plugins/advanced-pixel-for-barion/#developers) [Support](https://wordpress.org/support/plugin/advanced-pixel-for-barion/) ## Beschreibung 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](https://wordpress.org/plugins/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 * Keeps one base pixel on the page, because two copies of bp.js stop events from reaching Barion ## Screenshots [⌊Settings page — enter your Barion Pixel ID, then enable Full Pixel Tracking and Debug Mode.⌉⌊Settings page — enter your Barion Pixel ID, then enable Full Pixel Tracking and Debug Mode.⌉[ Settings page — enter your Barion Pixel ID, then enable Full Pixel Tracking and Debug Mode. [⌊Product page — Debug Mode logs contentView when the page loads, and addToCart when the customer adds the product to the cart.⌉⌊Product page — Debug Mode logs contentView when the page loads, and addToCart when the customer adds the product to the cart.⌉[ Product page — Debug Mode logs `contentView` when the page loads, and `addToCart` when the customer adds the product to the cart. [⌊Checkout page — initiateCheckout carries the cart contents and the revenue, and setEncryptedEmail sends the SHA-1 hashed billing email.⌉⌊Checkout page — initiateCheckout carries the cart contents and the revenue, and setEncryptedEmail sends the SHA-1 hashed billing email.⌉[ Checkout page — `initiateCheckout` carries the cart contents and the revenue, and` setEncryptedEmail` sends the SHA-1 hashed billing email. [⌊Order received page — purchase reports the completed order with its contents and revenue.⌉⌊Order received page — purchase reports the completed order with its contents and revenue.⌉[ Order received page — `purchase` reports the completed order with its contents and revenue. [⌊Events wait for consent. Accept marketing cookies in your banner and Debug Mode logs Consent granted (grantConsent).⌉⌊Events wait for consent. Accept marketing cookies in your banner and Debug Mode logs Consent granted (grantConsent).⌉[ Events wait for consent. Accept marketing cookies in your banner and Debug Mode logs `Consent granted (grantConsent)`. ## Installation 1. Upload the `advanced-pixel-for-barion` folder to `/wp-content/plugins/` 2. Activate the plugin through the ‚Plugins‘ menu in WordPress 3. Go to Settings > Barion Pixel and enter your Barion Pixel ID 4. Optionally enable or disable Full Pixel Tracking #### Requirements * WordPress 5.0 or higher * PHP 7.4 or higher * WooCommerce 5.0 or higher (for full event tracking) #### Optional * [WP Consent API](https://wordpress.org/plugins/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 ## FAQ ### 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. A Barion gateway implements the Base Pixel: it loads bp.js and sends the init event. It doesn’t implement the Full Pixel, which is the e-commerce events Barion reviews an integration on (contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail). That part is what this plugin adds, so both keep working together: that one handles payments, this one handles tracking. Clear the gateway’s optional Pixel ID field, though. Two copies of bp.js on one page stop events from reaching Barion altogether, so while a Pixel ID is configured here, Advanced Pixel for Barion switches the gateway’s Base Pixel off and serves it instead. It leaves the gateway’s pixel alone if this plugin has no Pixel ID. ### 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](https://wordpress.org/plugins/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. A person at Barion performs this approval. Contact Barion when your implementation is complete. ### 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](https://www.barion.com/en/business/barion-smart-gateway/). ### 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. ## Rezensionen Zu diesem Plugin liegen noch keine Rezensionen vor. ## Mitwirkende und Entwickler „Advanced Pixel for Barion“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt: Mitwirkende * [ Gergely Csécsey ](https://profiles.wordpress.org/mrdarkside/) [Übersetze „Advanced Pixel for Barion“ in deine Sprache.](https://translate.wordpress.org/projects/wp-plugins/advanced-pixel-for-barion) ### Interessiert an der Entwicklung? [Durchstöbere den Code](https://plugins.trac.wordpress.org/browser/advanced-pixel-for-barion/), sieh dir das [SVN-Repository](https://plugins.svn.wordpress.org/advanced-pixel-for-barion/) an oder abonniere das [Entwicklungsprotokoll](https://plugins.trac.wordpress.org/log/advanced-pixel-for-barion/) per [RSS](https://plugins.trac.wordpress.org/log/advanced-pixel-for-barion/?limit=100&mode=stop_on_copy&format=rss). ## Änderungsprotokoll #### 1.0.10 * Fix: adding a product from a shop or category page reported a price of 0 to Barion. WooCommerce renders no price on the archive add-to-cart button and the plugin read one from it, so every add from an archive counted as worth nothing. The price now comes from the Store API cart line, which is where the checkout block path already read it. * Fix: a second base pixel on the page stopped every event from reaching Barion. The Barion Payment Gateway prints its own base pixel whenever its Pixel ID field is filled, whatever its own tracking setting says and even with the gateway itself switched off. Two copies of bp.js leave the page with two iframes under one id, and the copy that loses that race posts its events into an iframe that has not read the visitor’s consent yet. bp.js throws there and nothing is sent. The plugin now switches the gateway’s base pixel off while a Pixel ID is configured here. * Fix: the plugin loaded a second copy of bp.js on top of any plain Barion snippet that got there first, such as a Google Tag Manager tag or one pasted into the theme header. Its guard asked for a global that the snippet Barion documents never sets. * New: debug mode warns when something else on the page loads a second copy of bp.js. A snippet that runs after the plugin is out of its reach, and until now nothing said so. #### 1.0.9 * Fix: `grantConsent` was sent as the page loaded rather than when the visitor accepted the cookie banner. Barion rejects a Full Pixel integration for exactly that, because a shop reporting consent before anyone has answered looks the same as one that never asks. Consent is now sent only for a decision the visitor makes on that page load. A returning visitor triggers nothing, since bp.js keeps their answer in its own cookie and Barion already has it. * Fix: with the WP Consent API plugin active but no cookie banner registered against it, every visitor was reported as having granted marketing consent. An unset consent type is how that API says no banner is driving it, and the plugin read it as a real answer. It now ignores the API in that state. * New: the settings page warns when the WP Consent API is active but no cookie banner registers with it. Installing it next to a banner that does not support it connects nothing, and until now nothing said so. #### 1.0.8 * Fix: `grantConsent` was 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: `grantConsent` was 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. #### 1.0.7 * 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 with `Call 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. #### 1.0.6 * Fix: `initiateCheckout` and `setEncryptedEmail` never 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_email` field, and the block has neither. It now reads the Cart and Checkout blocks‘ data store. Classic checkout behaviour is unchanged. * Fix: `addToCart` never 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: `addToCart` now 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. #### 1.0.5 * 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/plugins` unless a plugin registers its own directory, and the plugin never did. It now registers `languages/` on` init`. #### 1.0.4 * Compatibility: tested against WordPress 7.0 and WooCommerce 11.0. * `Requires PHP` raised 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. #### 1.0.3 * Fix: `setEncryptedEmail` was firing multiple times on a single checkout page load (the `change` + `blur` pair plus the `updated_checkout` rebind 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 with `Format 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 `blur` handler, idempotent rebinding via a data attribute). #### 1.0.1 * Fix: events script (contentView, addToCart, initiateCheckout, purchase, setEncryptedEmail) was never printed because it was enqueued after `wp_print_footer_scripts` had already run. * New: `setEncryptedEmail` now 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. #### 1.0.0 * 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 ## Meta * Version **1.0.10** * Zuletzt aktualisiert **vor 3 Wochen** * Aktive Installationen **60+** * WordPress-Version ** 5.0 oder höher ** * Getestet bis **7.1.3** * PHP-Version ** 7.4 oder höher ** * Sprache * [English (US)](https://wordpress.org/plugins/advanced-pixel-for-barion/) * Schlagwörter * [barion](https://de.wordpress.org/plugins/tags/barion/)[e-commerce](https://de.wordpress.org/plugins/tags/e-commerce/) [pixel](https://de.wordpress.org/plugins/tags/pixel/)[tracking](https://de.wordpress.org/plugins/tags/tracking/) [woocommerce](https://de.wordpress.org/plugins/tags/woocommerce/) * [Erweiterte Ansicht](https://de.wordpress.org/plugins/advanced-pixel-for-barion/advanced/) ## Bewertungen Es wurden noch keine Rezensionen eingereicht. [Deine Rezension](https://wordpress.org/support/plugin/advanced-pixel-for-barion/reviews/#new-post) [Alle Rezensionen anzeigen](https://wordpress.org/support/plugin/advanced-pixel-for-barion/reviews/) ## Mitwirkende * [ Gergely Csécsey ](https://profiles.wordpress.org/mrdarkside/) ## Support Behobene Probleme in den letzten zwei Monaten: 1 von 1 [Support-Forum anzeigen](https://wordpress.org/support/plugin/advanced-pixel-for-barion/)