[WordPress] 外掛分享: Pixelonce

首頁 › 外掛目錄 › Pixelonce
WordPress 外掛 Pixelonce 的封面圖片
全新外掛
安裝啟用
—
尚無評分
4 天前
最後更新
—
問題解決
WordPress 6.2+ PHP 7.4+ v1.0.1 上架:2026-11-17

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.1) 或搜尋安裝

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

原文外掛簡介

Pixelonce – fire-once funnel events for Meta Pixel and Meta’s Conversions API. Not affiliated with or endorsed by Meta.
Multi-step forms often live on one URL: a quote, a finance or insurance application, an enrolment. To most pixel setups, a reload, the back button or a second tab all look like another conversion. One applicant becomes four leads, and your ads optimise toward the wrong people.
Pixelonce lets every event declare how often it may fire — every time, once per page view, once per visit, once per session, once per visitor, or once per thing (a product, plan or vehicle id) — and shows you why an event did not fire.

Standard and custom events. Lead, Purchase, InitiateCheckout, ViewContent and the rest of Meta’s 18 standard events, each usable as a campaign objective — plus your own custom events (QuoteRequested, DocumentsUploaded…), as many as you need.
Fire once, on purpose. Per-event “how often” rules, and one rule per step even when every step shares a URL.
See why. A debug overlay (?stepcount_debug=1) lists every event and the reason it fired or not.
Server-side copy. Sends each event to Meta’s Conversions API as well, under the same event id, so Meta keeps one copy and still counts events an ad blocker stopped.
Consent first. Nothing loads before marketing consent. Works with the WP Consent API, IAB TCF v2, Cookiebot, Complianz, CookieYes and Borlabs Cookie, can send Google Consent Mode v2 signals, and honours Global Privacy Control (the browser “do not sell or share” signal several US states require).
Event parameters. Value, currency, content ids, content type and your own parameters — fixed, or read from the page.
Background submits. Fire an event only when an AJAX or fetch form submit succeeds, without editing the theme.
Trigger health. Flags buttons and forms that stopped matching after a theme or form change.
Setup wizard, starter templates, import and export, and an event log.

Everything above is included, with no limits on events, custom events, pages or pixels.
For developers

?stepcount_debug=1 opens the debug overlay (administrators on a live site; anyone on a dry-run staging copy).
StepCount.emit('EventName') fires an event set to “When the site signals it”.
StepCount.consent({marketing: true}) tells the plugin about consent from a tool it does not read itself.
Filters: stepcount_request, stepcount_config, stepcount_enabled, stepcount_debug_allowed, stepcount_purge_page_caches.

External services
Pixelonce sends data only to the services you configure, and only after the visitor has given consent when a consent tool is active.
Meta Pixel (when you enter a pixel id). The visitor’s browser loads https://connect.facebook.net/en_US/fbevents.js and sends the events you declare to Meta, with the parameters you set and the data Meta’s pixel collects (page URL, browser details, Meta cookies). Meta Terms · Meta Privacy Policy · Meta Business Tools Terms
Meta Conversions API (only when you add a Conversions API access token). Your server sends a copy of each event to https://graph.facebook.com/ with the event name, event id, page URL, the parameters you set, the visitor’s IP address and user agent, and Meta’s _fbp / _fbc cookie values when present. Same terms and policy as above.
The plugin itself does not send anything to its authors: no tracking and no remote updates.

延伸相關外掛

文章
Filter
Mastodon