Skip to main content

38 posts tagged with "pixel manager"

View All Tags

New Module Toggle: Disable Deprecated Functions to Trim JavaScript Size

· 4 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

Less code means faster pages. With version 1.53.0, Pixel Manager introduces a new toggle to disable the deprecated functions module entirely, trimming unnecessary JavaScript from your WooCommerce store.

TL;DR

  • New setting to disable deprecated functions module
  • Reduces front-end JavaScript by removing legacy compatibility code
  • Safe to disable if you don't use custom code relying on old event names
  • Part of a new modular architecture for optional features

Google Tag Gateway Proxy: First-Party Tracking Built Right Into WordPress

· 7 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

What if you could route all your Google Analytics and Google Ads tracking through your own domain, without any external services, cloud infrastructure, or ongoing costs?

Starting with version 1.53.0, you can. Pixel Manager now includes a built-in Google Tag Gateway Proxy that makes your tracking truly first-party. Just set a measurement path, and you're done.

TL;DR

  • Route Google tracking through your own domain. No external services required.
  • Bypass ad blockers and browser restrictions automatically
  • Extend cookie lifetimes beyond Safari's 7-day ITP limit
  • One setting to enable, multiple fallback mechanisms to ensure tracking never breaks
  • Zero additional infrastructure costs
Beta Feature

This feature is currently in beta. While we've implemented multiple fallback mechanisms to ensure your tracking never breaks, we recommend testing thoroughly in a staging environment before deploying to production.

Google Tag Scanner Warnings: Why They're Wrong About Pixel Manager's gtag.js Placement

· 9 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

If you've recently checked Google's Tag Coverage Report, you may have seen warnings about your gtag.js implementation:

  • "Tag not placed correctly"
  • "Tag loaded too late"
  • "Tag not found in the <head> section"
  • "Certain pages are not tagged"

If you're using Pixel Manager for WooCommerce in its default configuration, these warnings are misleading and incorrect. Here's why.

Pixel Manager Gets Major Performance Boost: Code Splitting Reduces Front End Size by Up to 50 Percent

· 10 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

In the latest release of Pixel Manager for WooCommerce, a long-standing architectural challenge has finally been solved.

The front end library used to be monolithic and bundled every tracking integration into a single file. That meant Google, Meta, TikTok, Hotjar and everything else shipped together, even if only a fraction was needed.

Now this changes entirely.

The new release 1.50.0 introduces code splitting, also known as chunking. Each pixel loads only when it is actually active. This reduces the amount of downloaded JavaScript significantly and improves page speed for WooCommerce shops.

Google Tag Manager Ruled Illegal to Load Without Consent in the EU — Here’s Why Pixel Manager Is a Safe Alternative

· 3 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

A new ruling by the Administrative Court of Hanover confirms a broader interpretation that affects the entire EU: Google Tag Manager (GTM) cannot be loaded without prior user consent.

The decision is rooted in GDPR and the ePrivacy Directive. Both apply across the EU, so while this case was decided in Germany, its implications extend to all EU member states.

If your WooCommerce store operates in the EU and relies on GTM, this ruling could impact your compliance setup.

The good news: Pixel Manager for WooCommerce already solves the core problems behind this decision.

Why Uploading Conversions to Google Ads in Parallel to Pixel Tracking Is a Bad Idea (and How Pixel Manager Already Solves the Problem)

· 5 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

Marketers have recently been bombarded with advice from some tracking code providers promoting a “conversion upload” solution - a feature meant to recover conversions supposedly lost due to Apple's iPhone privacy updates.

Their solution uses the simple idea to rename Google's gclid parameter and process it under a different name, thus bypassing Apple's Intelligent Tracking Prevention (ITP) restrictions, which filters out known tracking parameters.

At first, this sounds like a clever fix. But here's the catch that many overlook:

⚠️ These providers suggest uploading conversions in parallel to your normal, pixel-based Google Ads conversion tracking.

And that's exactly where things go wrong.

Introducing PageView server-to-server Event Tracking

· 4 min read
Aleksandar Vucenovic
Chief Growth Officer

featured image

TL;DR

Meta (Facebook) now pushes advertisers to track PageView events via the Conversion API (CAPI). We've added support for this in Pixel Manager — just one click to enable it.

However:

  • ⚠️ Increased server load — can cancel out caching benefits.
  • 📈 Small accuracy gain (~10-20%), but very low impact on purchase conversions.
  • ✅ Pixel Manager optimizes this via bundled REST API requests to keep load low.

We only recommend it if you really need it (e.g. Facebook insists) and have solid caching in place. Otherwise, browser-based PageView tracking is good enough for most.