| 开发者 | rapidooze09 |
|---|---|
| 更新时间 | 2026年11月19日 01:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
?stepcount_debug=1) lists every event and the reason it fired or not.?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.stepcount_request, stepcount_config, stepcount_enabled, stepcount_debug_allowed, stepcount_purge_page_caches.?stepcount_debug=1 added to the URL to see each event fire once.Open the page with ?stepcount_debug=1 while logged in as an administrator. Every event is listed with the reason it fired or not.
No. The browser and the server send the same event id, and Meta keeps one of each pair.
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.
No. Events are set up in Pixelonce: by page, by click or submit on a CSS selector, or by a background submit that succeeded.
Yes. Staging copies run in dry run: everything is evaluated and shown in the debug overlay, and nothing is sent.
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.
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.
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.
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.