UniPixel: Server-side Event Tracking & Consent for Google & Meta

UniPixel brings next-level event tracking to WordPress with full client- and server-side support for Meta, Google, and TikTok.\ It solves the growing gaps caused by browser restrictions, ad blockers, and cookie limits — ensuring your conversion data stays accurate, complete, and privacy-safe. Key Features

• Fine-tuned control over client-side and server-side event sending for every platform.
• Works with Meta Conversion API and Google Server-Side Tagging.
• Tracks standard WooCommerce events (ViewContent, AddToCart, InitiateCheckout, Purchase) with full order and product data.
• Create and manage your own custom events for clicks, views, and interactions.
• Automatic deduplication keeps matching client/server events counted only once.
• Built-in consent banner integrates with your site’s privacy framework to control when events are allowed to send.
• Live event viewer for testing, plus optional database logging for full event history.
• Simple setup with clear layouts, recommended defaults, and inline help.

Why Use UniPixel Modern tracking needs more than browser pixels.\ UniPixel sends verified conversion events directly from your own server to Meta and Google — keeping data flowing even when scripts or cookies are blocked.\ Client-side tracking still runs for richer, contextual insights, while server-side delivery ensures reliability and compliance.\ Everything is managed inside WordPress, giving you transparent control over how events send, when consent applies, and how data is logged. The result: more complete measurement, better ad platform optimisation, and a future-proof tracking setup for your store or website. == Installation ==

1. Install via WordPress Admin Panel:
2. Navigate to the 'Plugins' menu in WordPress.
3. Click 'Add New' and search for "UniPixel".
4. Click 'Install Now' and then 'Activate'.

2.2.0

• New: COmes with Consent Management Banner, built in to UniPixel, and options to control - one-click compliance for your site along with the benefits of server-side events.

2.1.4

• Minor updates and fixes:
• Improved Orest Bida cookie consent detection and handling (2.1.1 – 2.1.3)
• Small database schema update and upgrade fix (2.1.4)

2.1.0

• New: Control over both client-side setting and server-side setting for all of your events, including PageView, WooCommerce events and your own custom events.
• New: Easy to apply "Use Recommended Settings" button, to make setup much easier.
• New: Better settings for Google events, clearer separation of Client-side and Server-side choices
• New: Testing Console that supports seeing your events fire in real time to support better debugging and setup.
• New: Better options and control over storing/logging of all the vents that are fired, with more information too.
• New: Google PageView events now supports client-side and new server-side sending options.

1.15.1

• Fix: some events were not sending due to bug in Consent settings

1.15.0

• New feature: Honouring of Cookie Consent choices from supported systems: OneTrust, Cookiebot, or Osano. Turning this On means that UniPixel event tracking only takes place if the user has given consent in the relevant categories (e.g. Marketing or Performance). Optional setting.
• Improvement: ViewContent / view_item now filters out bots and crawlers to provide more accurate visitor data (server-side events were greater in qty than client side events)
• Fix: View Content for Google fixed to be correct event terminology, "view_item".

1.14.1

• Fix for "Enable Platform" setting not being honoured properly on some occasions when sending events.

1.14.0

• New feature to send 'ViewContent' / 'view_content' events for WooCommerce when products are viewed, providing additional information to Meta and Google. This helps populate reports in Google Analytics and Meta for better insights to things like "Purchase Journey", and adds to Sales Funnel insights.
• New feature to Turn-on or Turn-off platform Response Logging for WooCommerce server-side events (the response from Google or Meta). Provides option to improve performance if desired vs documenting the response from Google and Meta. Server-side Response Logging is turned-off by default for ViewContent events (to assist with performance for common occuring content views).
• Performance improvement: If Response Logging is turned off for Server-side events, this is now coupled with another update that allows remote post to the platform to be non-blocking, meaning that it doesn't hold up other WordPress processes and maintains seamless performance.

1.13.1

• Improved Meta Commerce tracking: Events like Purchase and AddToCart are now matched to your product catalog in Meta’s Commerce Manager, enabling more accurate attribution and shop insights.

1.13.0

• Meta/Facebook tracking: Now with New Option to send PageView as Server-side
• Meta/Facebook tracking: Added "event_source_url" (Page URL) now sent for better event info
• Meta/Facebook tracking: Fix - removed currency info for non-applicable events

1.12.2

• Code improvements to handle Meta Disabled, Google Disabled, prevent unneceseary processes going on if Disabled.

1.12.1

• Google tracking quality update

1.12.0

• New improvements to Google tracking, now with better gclid handling for Google Ads conversion tracking (campaign conversion tracking). Fixed a problem with Google's tracking script (gtag) not loading properly in some scenarios. Improved debgugging and testing features including new separate options for client-side and server-side debugging for Google DebugView.

1.11.1

• Added product name to Add To Cart and Checkout triggers for Google Analytics

1.11.0

• Bug fixes and event quality improvements for Google Analytics data sending. Some google events no being recognised because of missing "event_id". Introduction of "Enable Google DebugView" option in General Settings to support event feedback and testing in Google Analytics.

1.10.7

• Event quality updates and deduplication improvements, inlcuding more data sent for purchases.

1.10.6

• Initiate Checkout regularity updated

1.10.4

• Meta fbc matching improvement

1.10.3

• Update to timestamp being sent to Meta in fbc, using milliseconds now, to reduce Meta notification saying that timestamp in the future in some cases. This improves event matching quality in Meta.

1.10.1

• Fix for client_id not being sent in some cases for Google server-side sending, meaning that some woocommerce events were not being registered on Google.

1.10.0

• Improvements to Meta data-sending to address Meta's 'fbc' feedback warning, caused by differences in event_time being reported.
• Fixed currency value not being sent, fixed Cart Totals for Add To Cart events
• Changes to 'Session' handling (moved to using 'Transients', safer for WordPress).
• New feature in Admin to provide feedback, request features or report issues.
• New feature for Admin settings to turn on/off Logging tracking events in the Browser Console, to assist with debugging and setup.

1.9.3

• Fix for incorrect format of "fbc" value being sent in some instances to Meta.

1.9.2

• Fix for better consistency when sending 'fbc' to Meta, which helps with deduplication and increases conversion reporting

1.9.1

• Fix for Add to Cart event tracking for category "Add to Cart" buttons that use ajax

1.9.0

• IMPORTANT FIXES: Several fixes to address introduced bugs in 1.8.*, including re-factoring of WooCommerce server-side and client-side event sending. Addresses several issues identified in different WooCommerce versions where Add To Cart, Initiate Checkout and Purchases were not sending properly in some circumstances.

1.8.5

• Bug fix for Meta client side sending to improve event data consistency

1.8.4

• Bug fix causing error on non-woocommerce websites

1.8.2

• Updates to help text

1.8.1

• Bug fix for admin event updates creating duplicates in some scenarios

1.8.0

• New UX and easier setup for WooCommerce server side events, including improved event sending reliability.

1.7.1

• New diagnostics for better plugin performance and debugging.

1.7.0

• Admin UI improvements and additions, improved help text support and performance updates.

1.6.0

• Significant security and compatibility improvements. Upgrade for enhanced data handling and overall stability.

1.5.0

• Significant security and compatibility improvements. Upgrade for enhanced data handling and overall stability.

1.2.0

• Added Google Server side API integration.

1.1.1

• Initial release with Meta (Facebook) Conversion API integration.