FirePixel for WooCommerce
| 开发者 | firepixel |
|---|---|
| 更新时间 | 2026年11月5日 01:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
FirePixel for WooCommerce connects your WooCommerce store to the FirePixel platform, enabling server-side conversion tracking for Facebook/Meta Ads, TikTok Ads, and Google Ads.
Key Features:
- Server-side event delivery via FirePixel API — helps reduce signal loss from ad blockers, browser restrictions, and iOS privacy changes
- Automatic tracking of key WooCommerce events: PageView, ViewContent, ViewCart, ViewCheckout (InitiateCheckout), AddToCart, RemoveFromCart, and Purchase
- Frontend pixel/tag script injection for supported ad platforms when configured
- Event deduplication to help prevent double-counting
- Background async event queue — no impact on page load time
- Debug logging via the WooCommerce logger
- Quick Connect flow for easy API key setup
- Multi-platform ad tracking support for Meta/Facebook, TikTok, and Google Ads
- PageView (every storefront page)
- ViewContent (product pages, with the product and its price; shop and category pages)
- ViewCart (cart page)
- ViewCheckout (checkout page, sent to ad platforms as InitiateCheckout)
- AddToCart
- RemoveFromCart
- Purchase (when the order is paid: payment completes, or the order is marked processing or completed)
安装:
- Upload the
firepixel-for-woocommercefolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Go to WooCommerce > FirePixel in your admin dashboard.
- Enter your FirePixel Access Token or use Quick Connect to authenticate automatically.
- Save settings. The plugin will begin sending events immediately.
常见问题:
Do I need a FirePixel account?
Yes. Sign up at firepixel.io to get your API credentials.
Does this plugin slow down my store?
No. When a tracked event occurs, the plugin stores it in a database queue and returns immediately — nothing is sent to FirePixel during the page request. Queued events are processed in the background by WooCommerce Action Scheduler (recurring every 60 seconds), so storefront page loads are not slowed down. WP-Cron is used only as a fallback if Action Scheduler is unavailable.
Is WooCommerce required?
Yes. This plugin requires WooCommerce 7.0 or higher to be installed and active.
What PHP version is required?
PHP 7.4 or higher.
Where can I get support?
Visit firepixel.io for support and documentation.
更新日志:
1.2.6
- Stops sending when you switch the store off in FirePixel, and disconnects when you delete it there.
- Bug and security fixes.
- Product views now send the viewed product to your ad platforms.
- Various bug fixes and improvements to event accuracy.
- Adds support for ChatGPT Ads.
- FirePixel's connection check now passes your store's key in a request header instead of the URL, so the key no longer appears in server logs.
- Various bug fixes and improvements.
- Don't track bots or non-page requests such as robots.txt, feeds and sitemaps.
- Various bug fixes and improvements.
- Events are now sent to FirePixel in the new canonical/1 format. Customer email, phone and name are hashed in your store before they are queued, so they are no longer saved in the queue in plain text.
- Every request to FirePixel is now signed with your store's key instead of sending the key itself, so a captured request cannot be reused.
- Added to cart events now report the correct value and currency.
- The page address sent with each event no longer includes the query string or fragment.
- Phone numbers are formatted with a bundled copy of libphonenumber, so they now match on PHP 7.4 and 8.0 as well. They are still left out if the PHP mbstring extension is missing.
- The endpoint that turns on tracking now reads its key from the request body only, not from the URL.
- Requires the FirePixel API update that accepts the new format.
- Failed deliveries to FirePixel are now recorded in WooCommerce > Status > Logs, making connection problems easier to diagnose.
- Various bug fixes and improvements.
- Fixed: the wrong IP address could be sent for orders created outside the normal checkout.
- Various bug fixes and improvements.
- Improved Facebook conversion matching and simplified how attribution data is stored in the browser.
- Various bug fixes and improvements.
- Google conversions are now sent from our servers instead of from the visitor's browser. They no longer depend on the shopper's browser allowing tracking, and the plugin no longer loads Google's gtag script on your storefront. Click IDs are still captured in the browser exactly as before.
- Fixed: the private key from the order URL — the one a customer uses to view their own order — was being sent to the ad platforms alongside the order. Order IDs are still sent, because deduplication needs them; the key is not.
- Fixed: two different shoppers could be treated as the same person, which could report one customer's purchase under another customer's identity. This affected events both while they waited in the queue and as they were sent.
- Fixed: stores using the WooCommerce block checkout sent no begin-checkout event and no attribution data at all.
- Fixed: signing up for a subscription was counted as two checkouts instead of one.
- Fixed: an event sent on a shopper's behalf could carry the attribution of whoever triggered the send rather than the buyer's own.
- Fixed: customer details were read from the signed-in WordPress user instead of from the order, which could attribute a guest checkout to whoever was logged in.
- Fixed: events the queue had dropped are now retried, and every event records the page it happened on.
- Every event now carries a stable ID, so a purchase reported by both your store and the shopper's browser is recognised as one conversion rather than two.
- Declared compatibility with WordPress 7.1.
- Added a secure endpoint so the FirePixel app can turn on event tracking automatically once your store is connected.
- Initial release.