Untangling a Duplicated Meta Pixel on a WooCommerce Store

A marketing manager brought us a WooCommerce store, silverback-strength.com, whose Meta reporting could not be trusted. Two business portfolios and duplicate pixels were both collecting from the same site, so events were being split across datasets and counted twice. No optimisation decision made on that data would have been sound.

Detangling the accounts

We traced the second stream to a stale Meta connection still configured in WordPress, quietly reporting into the other portfolio's dataset. Removing it left a single Silverback pixel receiving everything, and we re-checked live that the correct pixel — and only that one — fires on product pages.

Fixing the data itself

Consolidating the streams exposed a second problem: purchase and product price values were arriving at Meta as text, with lowercase currency codes. Meta cannot optimise against a value it cannot read as a number. We shipped the correction first as a small custom plugin, then — at the client's request, to keep his plugin list short — moved it into a WPCode snippet named Meta Pixel Price Data Fix.

Campaign structure

With clean signal, the campaign's optimisation goal was the next problem: it was optimising for view content, the cheapest and least meaningful event on the site. We moved it to purchase, and then to initiate checkout when purchase failed to spend at the available budget. Ad sets were cleaned up and named so the account reads at a glance — Silverback - Sales Campaign, Sales - Initiate Checkout (Active), Original - View Content (Paused) — and the daily budget was set to £5/day to pace inside the account's £150 limit rather than exhaust it early.

Telling the client what the data actually said

We also ran the funnel numbers and reported something the client had not asked for: a roughly 4% product-view-to-add-to-cart rate, with product pages taking around four seconds to load, offering no size guide and only a single photograph. No amount of pixel accuracy fixes a product page that does not convert, and we said so.

We supplied a GIF walkthrough of the resulting Ads Manager and Events Manager state so the client could see the change rather than take our word for it.

Status

The tracking work was completed and re-verified live. The client's response was warm — "Your work and communication is great... I will definitely use you again" — but we make no claim of formal sign-off here: the milestone releases were still pending when the engagement paused.