[WordPress] 外掛分享: PixelSift for WooCommerce

首頁 › 外掛目錄 › PixelSift for WooCommerce
全新外掛
安裝啟用
—
尚無評分
剛更新
最後更新
—
問題解決
WordPress 7.0+ PHP 7.4+ v0.1.2 上架:2026-10-29

外掛標籤

開發者團隊

⬇ 下載最新版 (v0.1.2) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「PixelSift for WooCommerce」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Tracking tags are easy to install twice. A theme adds a GA4 snippet, a plugin adds the same ID again, Google Tag Manager loads a third copy, and your purchases are counted twice. PixelSift for WooCommerce checks your own store’s pages and tells you, in plain English, what is wrong and how to fix it.
PixelSift is read-only and runs on your own server. By default it makes no external calls. No data leaves your site.
What it checks
PixelSift scans the front end of your own store: the home page, a product page, the cart page, the checkout page and the order-received page (loaded without an order). On those pages it looks for:

Google Analytics 4 (gtag.js): the same measurement ID set up by more than one plugin or snippet, the same ID configured twice on one page, gtag.js loaded more than once, and more than one GA4 ID.
Google Tag Manager: the same container loaded twice or by two sources, several containers, and GA4 loaded directly while a container is also present (a common cause of double counting).
Meta Pixel: the same pixel ID initialised more than once or by two sources, more than one pixel ID, the pixel library loaded twice, and pixel events with no pixel base code.
Google Ads: the same AW- conversion ID set up more than once.
Universal Analytics leftovers: old UA-style tags that no longer collect data and can be removed.
TikTok, Pinterest and Microsoft Advertising (UET): the same pixel set up more than once.
Ecommerce events: the purchase event sent by more than one plugin, tags with no purchase event, and a product page with no ecommerce events.

For each tag it shows which plugin, theme or must-use plugin added it.
Plugin conflicts
Many stores run more than one tracking plugin. PixelSift flags common overlaps between:

Site Kit by Google
GTM4WP
PixelYourSite
Meta for WooCommerce
Google Analytics for WooCommerce

PixelSift works alongside these plugins and does not replace them. It points out where two of them, or a plugin and your theme, are sending the same tag.
Health score and fix guidance
Every scan gives a 0–100 health score with a breakdown that shows exactly how many points each finding cost. Each finding explains what was detected, on which page, why it matters, and the steps to fix it, with a link to the right settings screen of the plugin involved. For example: “keep one source for this GA4 ID and turn off the other”. Only problems PixelSift can prove from your pages (the same ID twice, the same code block repeated) lower the score. Checks it cannot prove, for example two plugins both set up to send purchases but with different or unknown IDs, are shown as “Info” (worth checking) and cost no points. You can mark a finding as reviewed, for example when two GA4 IDs are intentional, and it stops counting against the score.
Everything is free
All scanning, the health score and the fix guidance are included in this plugin. No feature is locked, time-limited or limited by quota.
Privacy

No external calls. Scans request your own store’s pages from your own server with a WordPress loopback request (wp_remote_get to your own site address, 20-second timeout per page). Requests to any other host are refused.
No data is sent to the plugin author or any third party.
No visitor or customer data is read. The scanner looks at the page code your store serves, not at orders or customers.
No tracking, analytics or “phone home” inside the plugin.

Limits
PixelSift reads the HTML and scripts your pages serve. It cannot see:

tags inside a Google Tag Manager container, because reading the container would mean contacting Google;
server-side events (such as the Meta Conversions API, server-side GTM or the Measurement Protocol), except as hints in the page code;
settings inside your Google or Meta accounts;
tags that are added later by JavaScript, or only after a visitor accepts a cookie banner, if they are not in the page code;
purchase events as they happen, because it never creates test orders.

If your server cannot make a loopback request to itself (some hosts block this), the scan reports which pages could not be loaded.
PixelSift is an independent tool. It is not affiliated with or endorsed by Automattic, WooCommerce, Google or Meta. WooCommerce is a trademark of Automattic Inc. Google Analytics, Google Tag Manager and Google Ads are trademarks of Google LLC. Meta is a trademark of Meta Platforms, Inc.

延伸相關外掛

文章
Filter
Mastodon