WordPress plugin intelligence profile

Halfborg Pixel Tracking for WooCommerce

Sends WooCommerce e-commerce events to the Meta Pixel and Conversions API, Google Analytics 4 and Google Ads.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version1.2.2
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 5.0 · PHP 7.2
Directory statusactive
Last directory update26 Oct 20267d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Halfborg Pixel Tracking for WooCommerce version 1.2.2 as active, updated 7d ago and tested up to WordPress 7.0.

Overview

About this plugin

Halfborg Pixel Tracking for WooCommerce sends your store’s e-commerce events to Meta and Google from one plugin.

For Meta, it sends events both from the browser (Meta Pixel) and from your server (Facebook Conversions API), so conversions are still recorded when the browser pixel is blocked. The two halves share an event ID so Meta counts each event once.

For Google, it loads one Google tag at the top of every page and sends the full WooCommerce funnel to Google Analytics 4 and Google Ads.

Features

  • Meta: ViewContent, AddToCart, InitiateCheckout and Purchase, sent from both the browser and the server with deduplication
  • Google Analytics 4: view_item_list, select_item, view_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info and purchase, with full item data
  • Google Ads: purchase conversion with transaction ID, new-customer flag and optional cart data for Merchant Center, dynamic remarketing (retail) with product IDs that match your Merchant Center feed, and optional enhanced conversions
  • Each Google purchase is reported once, even if the thank-you page is reloaded
  • Consent Mode defaults that deny storage in the EEA, UK and Switzerland until a consent tool updates them
  • Shop managers and administrators are left out of Google tracking by default
  • Works with WooCommerce’s High-Performance Order Storage (HPOS)
  • Works with the classic and the block-based cart and checkout, and with classic and block themes
  • Customer data is SHA-256 hashed before it is sent

How It Works

  • As a visitor browses, adds to cart and checks out, the plugin sends each step to the services you have configured
  • Google add-to-cart and remove-from-cart events are recorded from WooCommerce’s own cart, so they are captured whether the product was added from a product page, a shop page link, an AJAX button or a cart block, and when a quantity is changed
  • When a customer completes an order, the purchase is sent with its value, currency, items and order number
  • Customer data is hashed with SHA-256 before it leaves your server

External services

This plugin connects to Meta (Facebook) and Google to send e-commerce tracking events. This is the core purpose of the plugin and it cannot function without them. Each service is used only once you enter its ID on the settings screen.

1. Meta Conversions API (server-side)

com. This is what allows conversions to be attributed to your Meta ad campaigns even when the browser pixel is blocked.

Events are sent when a visitor views a product (ViewContent), adds a product to the cart (AddToCart), begins checkout (InitiateCheckout), and completes an order (Purchase).

The data sent with these events is: the customer’s email address, phone number, first and last name, city, state, postcode and country — each of which is irreversibly hashed with SHA-256 before it leaves your server — together with the order or product value, the currency, the product IDs, the number of items, an event ID used for deduplication, the page URL, and the visitor’s IP address, browser user-agent and Meta browser cookies ( _fbc and _fbp ), which Meta requires in unhashed form for attribution.

Nothing is sent until you enter a Pixel ID and a Conversions API Access Token on the settings screen. If either is missing, no server-side event is sent.

2. Meta Pixel (browser-side)

com. Each browser event carries the same event ID as its server-side counterpart so Meta can deduplicate the pair. com/tr is included for visitors with JavaScript disabled.

This service is provided by Meta Platforms, Inc. Please review their terms and privacy policy, and make sure your site’s own privacy policy and cookie consent notice disclose this tracking to your visitors:

  • Meta Terms of Service: https://www.facebook.com/legal/terms/
  • Meta Business Tools Terms: https://www.facebook.com/legal/terms/businesstools
  • Meta Privacy Policy: https://www.facebook.com/privacy/policy/

3. Google Analytics 4 and Google Ads (browser-side)

com into your visitors’ browsers. Nothing is loaded for Google if both IDs are empty.

net ): product list views, product clicks, product views, add to cart, remove from cart, cart views, begin checkout, shipping and payment method selection, and purchases. These events carry the product IDs, SKUs, names, categories, prices and quantities involved, the cart or order value, the currency, any coupon codes, and for purchases the order number, tax and shipping.

If you enter a Merchant Center ID, the Google Ads purchase conversion also carries that ID, your feed’s country and language, the sold product IDs, prices and quantities, and the order discount. Google’s tag also collects the page URL, the visitor’s IP address, browser details and Google cookies.

If you turn on enhanced conversions, the purchase conversion also includes the customer’s billing email address, phone number, first and last name and street address, each SHA-256 hashed before it is added to the page, plus their unhashed city, state, postcode and country.

This service is provided by Google LLC. Please review their terms and privacy policy, and make sure your site’s own privacy policy and cookie consent notice disclose this tracking to your visitors:

  • Google Terms of Service: https://policies.google.com/terms
  • Google Analytics Terms of Service: https://marketingplatform.google.com/about/analytics/terms/us/
  • Google Privacy Policy: https://policies.google.com/privacy
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • conversion api
  • google ads
  • google analytics
  • pixel
  • woocommerce
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.0 · PHP 7.2
Update activity26 Oct 20267d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.2.11.2.2
Version1.2.01.2.1
Version1.1.01.2.0
WordPress compatibility7.0.47.0.7
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.