Linux 软件免费装
Banner图

Pixelonce

开发者 rapidooze09
更新时间 2026年11月19日 01:31
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

tracking funnel consent meta pixel conversions api

下载

1.0.1

详情介绍:

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. Everything above is included, with no limits on events, custom events, pages or pixels. For developers

安装:

  1. Install the plugin and activate it.
  2. Open Pixelonce → Setup and follow the four steps: your pixel id, a starting template, optionally a Conversions API token, then a test.
  3. Walk through your funnel with ?stepcount_debug=1 added to the URL to see each event fire once.

屏幕截图:

  • An event with parameters: value, currency, content ids and your own.
  • The debug overlay: every event, and why it fired or not.
  • Trigger health: triggers that stopped matching.
  • The server-side event log.
  • The setup wizard.
  • Consent settings.

升级注意事项:

1.0.1 Renamed to Pixelonce; custom events; security hardening; clears page caches when settings change.

常见问题:

Why did my event not fire?

Open the page with ?stepcount_debug=1 while logged in as an administrator. Every event is listed with the reason it fired or not.

Will I count the same conversion twice with the Conversions API?

No. The browser and the server send the same event id, and Meta keeps one of each pair.

Do I need a cookie banner?

If your visitors are in a region that requires consent for marketing cookies (for example the EU, the UK or Brazil), yes. Pixelonce waits for consent from your consent plugin; it is not a banner itself.

Do I need to edit my theme or form plugin?

No. Events are set up in Pixelonce: by page, by click or submit on a CSS selector, or by a background submit that succeeded.

Can I try it on a staging site first?

Yes. Staging copies run in dry run: everything is evaluated and shown in the debug overlay, and nothing is sent.

Can I use my own event names?

Yes. Pick "Custom event…" and type the name: letters, digits and underscores, starting with a letter, at most 40 characters (Meta's rule). Custom events are sent with the same fire-once rules and the same server-side copy as standard ones. Meta does not let custom events be campaign objectives; use them for custom conversions and reporting.

I use a page cache. Do I need to clear it after changing settings?

No. Saving any Pixelonce setting clears the page caches of WP Super Cache, W3 Total Cache, LiteSpeed Cache, WP Rocket, WP Fastest Cache, SiteGround Optimizer and Autoptimize, so cached pages pick up the new configuration. Other caches (a CDN, a host's own cache) may need clearing by hand.

How is the server-side endpoint protected?

The browser posts each server-side copy to an endpoint on your own site. It is public, because visitors are not logged in and pages are often cached, but it only accepts requests from your own pages (same origin) carrying a signed token printed into the page, valid for 7 days; only events and pixels your configuration declares, with consent; and it is rate-limited per visitor. If a page stays in a cache for more than 7 days, its browser events still fire but their server-side copies are refused until the page is refreshed in the cache.

What does the diagnostic file contain?

Your Pixelonce configuration, versions of WordPress, PHP, theme and plugins, consent status, trigger health and recent server-side sends. Never your Conversions API token or anything about your visitors.

更新日志:

1.0.1 1.0.0