Description
UniPixel brings next-level event tracking to WordPress with full client- and server-side support for Meta, TikTok and Google.
No need for extra apps, external cloud servers, or separate custom domains for server-side sending. Easy install to your existing WordPress website.
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, «TikTok Events 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.
No complex cloud setup or additioal hosting, easy installation, be setup in mintues.
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.
Setup
Configure Meta (Facebook) Conversion API tracking?
To enable Meta (Facebook) Conversion API tracking, you need:
– Facebook Pixel ID
– Access Token
Getting Your Facebook Pixel ID
- Log in to Facebook Business Manager: https://business.facebook.com/
- Go to Events Manager.
- Select your Pixel.
- Copy the Pixel ID from the top-right corner.
Generating an Access Token
- Go to Business Settings in Facebook Business Manager.
- Navigate to System Users and click Add System User.
- Assign Admin permissions and select your Business Account.
- In the Permissions tab, ensure access to «Manage Ads».
- Click Generate Access Token.
- Copy and save the token securely.
Enter these details in WordPress Admin > UniPixel Settings > Meta.
Configure TikTok Event Tracking?
UniPixel now includes full support for TikTok Events API, allowing you to send both client-side and server-side events directly to TikTok for accurate ad reporting.
To enable TikTok event tracking, you only need:
- TikTok Pixel ID
- Access Token
Getting Your TikTok Pixel ID
- Log in to TikTok Ads Manager: https://ads.tiktok.com/
- Go to Assets > Events.
- Choose Web Events.
- Select or create your TikTok Pixel.
- Copy the Pixel ID shown under your Pixel name.
Getting Your TikTok Access Token
- In TikTok Events Manager, open your Pixel.
- Go to Settings > Advanced Settings > Access Token.
- Click Generate Access Token.
- Copy and save the token securely.
Enter both your Pixel ID and Access Token inWordPress Admin > UniPixel Settings > TikTok.
No extra steps required
Unlike other platforms, TikTok setup is quick and straightforward —
you do not need to set up a Business Center App, external server, or custom domain for server-side sending.
UniPixel handles both the client-side pixel and server-side Events API calls automatically inside WordPress.
Just activate TikTok in UniPixel settings, enter your credentials, and you’re ready to start tracking conversions and optimizing your TikTok campaigns.
configure Google Server-Side Tracking?
To enable Google Analytics (GA4) and Google Ads server-side tracking, you need:
– GA4 Measurement ID
– Google Tag Manager (GTM) Container ID (if using GTM)
– Google API Secret
Getting Your GA4 Measurement ID
- Log in to Google Analytics: https://analytics.google.com/
- Click Admin > Data Streams.
- Select your website data stream.
- Copy the Measurement ID (format: G-XXXXXXXXXX).
Getting Your Google Tag Manager (GTM) Container ID
- Log in to Google Tag Manager: https://tagmanager.google.com/
- Select your container.
- Copy the Container ID (format: GTM-XXXXXX).
Getting Your Google API Secret
- Go to Google Analytics Admin.
- Under Data Streams, select your website stream.
- Scroll down to Measurement Protocol API Secret.
- Click Create, name it (e.g., «Server-Side Tracking»), and copy the API Secret.
Enter these details in WordPress Admin > UniPixel Settings > Google.
What if I already have Meta or Google tracking installed?
If your site already includes tracking via another plugin or manually, select «Pixel Already Included» in UniPixel settings. This prevents duplicate tracking scripts but still allows UniPixel to send custom events.
How does server-side event tracking work?
UniPixel supports both client-side and server-side event tracking:
– Client-side events are sent directly from the browser.
– Server-side events use API calls to prevent ad blockers from blocking conversions.
To enable server-side tracking for Meta, enter your Access Token.
For Google, enter your API Secret.
How does UniPixel prevent duplicate events?
UniPixel uses event deduplication by assigning a unique event ID to each event. This ensures that events sent via both client-side and server-side are not counted twice.
Tips
Deduplication
UniPixel automatically prevents duplicate counting when both client-side and server-side events are enabled.
Each event is assigned a unique event_id when triggered. This same ID is sent to both the browser pixel and the server API, allowing platforms to merge identical events.
- Meta (Facebook / Instagram) – Uses
event_idto match Pixel and Conversion API events so they count once. - Google (GA4 / Ads) – Uses shared
client_idandsession_idvalues for client/server matching. Works automatically for both client-first and server-first setups. - TikTok – Uses shared event IDs across Pixel and Events API for seamless deduplication.
No extra setup is required — UniPixel handles ID creation and matching automatically.
Privacy and 3rd Party Services
This plugin uses external services provided by Meta (Facebook) and Google to track and log user events for analytics and advertising purposes. The plugin interacts with the following services:
- Meta (Facebook) Pixel: Sends user event data (e.g., PageView, Purchase) to Facebook for tracking purposes.
- Meta’s Graph API: Sends user event data server-side for tracking and logging purposes.
- Google Analytics: Sends user event data to Google for analytics and tracking via the Measurement Protocol and Google Tag Manager.
Domains
This plugin communicates with the following domains:
– Meta (Facebook):
– https://www.facebook.com
– https://graph.facebook.com
– Google:
– https://www.google-analytics.com
– https://www.googletagmanager.com
– Buildio:
– https://buildio.dev
Data Sent
Data sent to these domains may include:
– User interactions (e.g., clicks, page views, purchases)
– IP address and user agent (collected by tracking mechanisms)
– Custom event data such as purchase amount, currency, and transaction ID (depending on how the plugin is configured)
– Diagnostic information may be sent to Buildio to assist with plugin performance and bug fixes, including site url, ip address and basic interactions. No sensitive information or keys are sent.
Privacy and Terms
For more details on Meta’s and Google’s privacy policies and terms of use, please visit the following links:
- Meta (Facebook) Privacy Policy
- Meta (Facebook) Terms of Service
- Google Privacy Policy
- Google Terms of Service
- Buildio Privacy Policy
License
This plugin is licensed under the GPLv2 or later.
Installation
- Install via WordPress Admin Panel:
- Navigate to the ‚Plugins‘ menu in WordPress.
- Click ‚Add New‘ and search for «UniPixel».
- Click ‚Install Now‘ and then ‚Activate‘.
Reviews
Contributors & Developers
“UniPixel: Server-side Event Tracking & Consent for Meta, TikTok and Google” is open source software. The following people have contributed to this plugin.
ContributorsInterested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.3.0
- New: TikTok now added! Track events both client-side and server-side to TikTok’s Event API.
2.2.0
- New: Comes with Consent Management Banner now built in to UniPixel. Easy configuration and 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
- Security and compatibility improvements. Upgrade for enhanced data handling and overall stability.
1.5.0
- 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.







