UniPixel: Meta, Pinterest, TikTok, Google & Microsoft Server...

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 — fully featured popup with built-in translations for 18 languages, editable wording per language, 5 layout styles (centred card / top or bottom bar / corner card), optional non-blocking mode, and a Reject all button toggle. Or skip the popup entirely and let UniPixel read consent from your existing CMP — supports OneTrust, Cookiebot, Osano, Silktide, Orest Bida, Complianz, CookieYes, Moove GDPR, and CookieAdmin (Softaculous).
• 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.

Why Server-Side Tracking Matters

Around 43% of internet users run ad blockers. Safari limits cookies to 7 days. iOS App Tracking Transparency reduced reported conversions by 30-40% for many advertisers. When your tracking relies only on a browser pixel, these restrictions silently discard your conversion data.

Server-side tracking sends conversion data directly from your server to the ad platform API. Ad blockers cannot touch it. Cookie limits do not apply. The result: your ad platforms see your real conversions, optimise better, and your ad spend works harder.

Why UniPixel

UniPixel sends API calls directly from your own WordPress server. No GTM server container, no external cloud, no routing your data through third-party services.

• 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.

Optional Advanced Matching sends hashed user data (email, phone, address) alongside events to help platforms improve Event Match Quality.

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_id to match Pixel and Conversion API events so they count once.
• Pinterest — uses event_id to match Tag and Conversions API events for full deduplication.
• TikTok — uses shared event IDs across Pixel and Events API for seamless deduplication.
• Google (GA4 / Ads) — uses shared client_id and session_id values for client/server matching. Works automatically for both client-first and server-first setups.
• Microsoft (Bing / UET) — uses eventId to match UET tag and Conversions API events for deduplication.

Read the full description on the official page →