UniPixel: Meta, Pinterest, TikTok, Google & Microsoft Server-Side Tracking for WooCommerce
| 开发者 | buildiodev |
|---|---|
| 更新时间 | 2026年3月31日 19:49 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 6.9.4 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
标签
woocommerce pixel
tiktok events api
server-side tracking
meta conversion api
pinterest conversions api
下载
2.5.0
2.6.1
2.5.1
2.3.0
1.12.2
2.5.3
2.5.6
2.6.0
2.6.2
2.6.3
1.11.0
2.3.1
1.10.6
1.10.7
1.6.1
1.7.0
1.7.1
1.8.0
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.9.0
1.9.1
1.9.2
1.11.1
1.12.0
1.12.1
1.10.3
1.13.0
1.14.0
1.14.1
1.9.3
1.10.0
1.13.1
1.15.0
1.10.4
2.5.2
2.5.4
1.10.1
1.10.2
2.1.1
2.1.2
2.1.3
2.1.4
1.10.5
2.2.0
1.15.1
2.1.0
2.3.2
2.4.0
详情介绍:
Ad blockers, iOS privacy changes and cookie restrictions mean your browser-based tracking pixel is only reporting a fraction of your actual conversions. Your ads cannot optimise on data they never receive.
UniPixel fixes this by sending conversion events directly from your WordPress server to Meta, Pinterest, TikTok, Google and Microsoft — bypassing the browser entirely. No external cloud hosting, no GTM server container. Install, paste your credentials, and server-side tracking is live.
What It Does
- Meta Conversion API (CAPI) — server-side and client-side event sending with full deduplication.
- Pinterest Conversions API — server-side and client-side tracking with full deduplication.
- TikTok Events API — server-side and client-side tracking with automatic deduplication.
- GA4 Measurement Protocol — server-side event delivery to Google Analytics and Google Ads.
- Microsoft UET & Conversions API — client-side tracking via UET with early support for Microsoft's Conversions API (CAPI) pilot program. WooCommerce events and custom events supported.
- WooCommerce events — ViewContent, AddToCart, InitiateCheckout and Purchase tracked automatically with full product data (names, categories, variants, values).
- Custom events — create your own click, view and interaction events for any WordPress page. Not limited to WooCommerce.
- Automatic deduplication — each event gets a unique ID shared between client and server, so platforms count it once.
- Built-in consent management — includes its own consent banner or reads from OneTrust, Cookiebot, Osano, Silktide, Orest Bida, Complianz, CookieYes and Moove GDPR.
- Live event testing — real-time console shows events as they fire, with full payload data.
- Event logging — optional database storage of every event sent, for debugging and audit.
- Meta, Pinterest, TikTok, Google and Microsoft — server-side and client-side tracking for all five platforms.
- No GTM required — no server container setup, no custom subdomain, no separate hosting.
- No external cloud — your data goes from your server to the ad platform. Nothing in between.
- Works on any WordPress site — WooCommerce stores get automatic ecommerce event tracking. Non-WooCommerce sites use custom events for lead gen, SaaS, content or anything else.
- Five-minute setup — install, enter your Pixel ID and access token, enable the platform. Done.
安装:
- In WordPress Admin, go to Plugins > Add New.
- Search for "UniPixel".
- Click Install Now, then Activate.
- Go to UniPixel in the admin menu to configure your platforms.
屏幕截图:
常见问题:
What credentials do I need for Meta?
Your Facebook Pixel ID (from Events Manager) and an Access Token (from Business Settings > System Users). Enter both in UniPixel > Meta Setup.
What credentials do I need for Google?
Your GA4 Measurement ID (format: G-XXXXXXXXXX) and a Measurement Protocol API Secret (from Admin > Data Streams). Optionally, a GTM Container ID if you use Google Tag Manager. Enter these in UniPixel > Google Setup.
What credentials do I need for Pinterest?
Your Pinterest Tag ID, Ad Account ID and a Conversions API Access Token (from Ads Manager > Conversions > Set Up API). Enter all three in UniPixel > Pinterest Setup.
What credentials do I need for TikTok?
Your TikTok Pixel ID and an Access Token (from Events Manager > Pixel Settings > Advanced Settings). Enter both in UniPixel > TikTok Setup.
What credentials do I need for Microsoft?
Your Microsoft UET Tag ID and a CAPI Access Token (from Microsoft Advertising > Conversion Tracking > UET Tag Settings). Enter both in UniPixel > Microsoft Setup.
What if I already have a Meta pixel or Google tag on my site?
Select "Pixel Already Included" in UniPixel settings. This prevents duplicate tracking scripts while still allowing UniPixel to send server-side events and custom events.
How does deduplication work?
Each event gets a unique event ID. The same ID is sent via the browser pixel and the server API call. Meta, Pinterest, TikTok and Google use this ID to merge duplicate events, counting them once instead of twice.
Does this work without WooCommerce?
Yes. WooCommerce events (Purchase, AddToCart, etc.) require WooCommerce. But PageView, custom click events and custom interaction events work on any WordPress site.
Do I need a GTM server container?
No. UniPixel sends server-side events directly from your WordPress server to each platform's API. No Google Tag Manager setup is required.
更新日志:
2.6.3
- Fix: Improved compatibility with WordPress themes and configurations. Event tracking now works reliably across all WordPress sites.
- Fix: Resolved a compatibility issue that could prevent activation on some hosting environments.
- New: Microsoft WooCommerce events — Purchase, AddToCart, Checkout and ViewContent now tracked automatically for Microsoft Advertising, with support for Microsoft's new Conversions API (CAPI) pilot program.
- New: Microsoft admin experience — updated events page with one-click recommended settings.
- Improvement: AddToCart tracking now works across more WordPress and WooCommerce configurations, delivering more accurate conversion data to all five platforms.
- Improvement: Checkout events now register unique purchase intent more accurately, improving conversion reporting for ad platform optimisation.
- Fix: Resolved an issue affecting WooCommerce event tracking introduced in 2.5.3. All events now fire correctly.
- New: Advanced Matching — automatically sends hashed user data (email, phone, name, address) with events to Meta, TikTok and Pinterest. Improves Event Match Quality scores for better attribution. Enable via General Settings.
- Improvement: Event matching and data quality improvements across all platforms.
- New: Pinterest Conversions API — full server-side and client-side tracking with deduplication. WooCommerce events (Purchase, AddToCart, InitiateCheckout, ViewContent), PageView, and custom events all supported.
- New: Server-side tracking is now optional per platform — start with client-side only and enable server-side when ready.
- Improvement: Access tokens no longer required during initial setup. Add them later to activate server-side tracking.
- New: Consent support added for Complianz, CookieYes, and Moove GDPR — nine consent managers now supported in total.
- Improvement: Simplified consent settings — choose between UniPixel's built-in banner or your existing consent manager. UniPixel detects and respects choices automatically.
- Help and documentation improvements.
- Improvement: Richer product data — variant, category and item-level values now sent across all WooCommerce events for better reporting in Meta, TikTok and Google.
- Improvement: Better cookie handling for fbclid and gclid click attribution.
- Fix: TikTok deduplication — conversions are no longer double-counted.
- Fix: AddToCart now reports the correct item value and correctly identifies variable products (sizes, colours, etc.).
- Improvement: Dashboard updates, all three platforms now shown on the home page.
- Improvement: Consent popup width adjustment and copy refinement.
- Bug fix: important code update to fix a function that created an error
- New: TikTok now added! Track events both client-side and server-side to TikTok's Event API.
- 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.
- 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)
- 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.
- Fix: some events were not sending due to bug in Consent settings
- 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".
- Fix for "Enable Platform" setting not being honoured properly on some occasions when sending events.
- 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.
- 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.
- 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
- Code improvements to handle Meta Disabled, Google Disabled, prevent unnecessary processes going on if Disabled.
- Google tracking quality update
- 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 debugging and testing features including new separate options for client-side and server-side debugging for Google DebugView.
- Added product name to Add To Cart and Checkout triggers for Google Analytics
- Bug fixes and event quality improvements for Google Analytics data sending. Some google events not 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.
- Event quality updates and deduplication improvements, including more data sent for purchases.
- Initiate Checkout regularity updated
- Meta fbc matching improvement
- 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.
- 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.
- 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.
- Fix for incorrect format of "fbc" value being sent in some instances to Meta.
- Fix for better consistency when sending 'fbc' to Meta, which helps with deduplication and increases conversion reporting
- Fix for Add to Cart event tracking for category "Add to Cart" buttons that use ajax
- 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.
- Bug fix for Meta client side sending to improve event data consistency
- Bug fix causing error on non-woocommerce websites
- Updates to help text
- Bug fix for admin event updates creating duplicates in some scenarios
- New UX and easier setup for WooCommerce server side events, including improved event sending reliability.
- New diagnostics for better plugin performance and debugging.
- Admin UI improvements and additions, improved help text support and performance updates.
- Security and compatibility improvements. Upgrade for enhanced data handling and overall stability.
- Compatibility improvements. Upgrade for enhanced data handling and overall stability.
- Added Google Server side API integration.
- Initial release with Meta (Facebook) Conversion API integration.