Free WordPress plugin · Meta Pixel + Conversions API

Fire-once funnel events for Meta Pixel.

On quote, finance and enrolment forms that keep every step on one URL, reloads, the back button and second tabs make most pixel setups count one conversion several times. Pixelonce lets each event say how often it may fire — and shows you why it did or didn't.

  • Standard and custom events
  • No limits on events, pages or pixels
  • Consent first

WordPress 6.2+ · PHP 7.4+ · Get it on WordPress.org

A funnel with five steps. At step 1 a reload, at step 3 the back button and at step 4 a second tab each try to send the event again; Pixelonce stops all three. One clean event per step continues to Meta, which counts 1 conversion, not 4.

Works with

  • WP Consent API
  • IAB TCF
  • Cookiebot
  • Complianz
  • CookieYes
  • Borlabs Cookie
  • Google Consent Mode v2
  • Global Privacy Control
  • Multi-step forms on one URL
  • admin-ajax form plugins
  • fetch / REST submits
  • WooCommerce (template)

01 · The problem

One applicant. Four InitiateCheckout events.

Quote, finance, insurance and enrolment funnels keep five steps on one URL. To a pixel, a reload, the back button, a second tab and the next step all look the same.

So one application becomes several conversions. The ad platform optimises toward the wrong people, and every decision is made on inflated numbers.

example.com/apply — the same URL for every step
Step 1
Step 2
Step 3
Step 4
Step 5
  1. InitiateCheckoutstep 1 shown
  2. InitiateCheckoutreload
  3. InitiateCheckoutback from step 2
  4. InitiateCheckoutopened in a second tab
4 reported, 1 real.
Nothing errors. Your cost per lead just looks better than it is.
A naive pixel fires InitiateCheckout whenever step 1 is shown: on arrival, on reload, on coming back from step 2, and in a second tab — four events for one applicant.

02 · How it works

One visit, five steps, every event sent once.

Each event declares how often it may fire. Pixelonce remembers what was already sent for this page view, visit, session or visitor, so a repeat is stopped before it reaches the pixel.

  1. Step 1 · QuoteInitiateCheckout, once per session. A reload sends nothing new.
  2. Step 2 · Your detailsViewContent, once per visit.
  3. Step 3 · Loan termsCustomizeProduct, once per visit — the back button doesn't repeat it.
  4. Step 4 · Bank detailsAddPaymentInfo, once per visitor — not again in a second tab.
  5. Step 5 · SubmitLead, once per plan id, from the browser and the server under one event id.
example.com/apply/
  1. InitiateCheckout firedfired · step 1 · once per session
  2. InitiateCheckout suppressedsuppressed · reload · already sent this session
  3. ViewContent firedfired · step 2 · once per visit
  4. CustomizeProduct firedfired · step 3 · once per visit
  5. CustomizeProduct suppressedsuppressed · back button · already sent this visit
  6. AddPaymentInfo firedfired · step 4 · once per visitor
  7. AddPaymentInfo suppressedsuppressed · second tab · already sent for this visitor
  8. Lead firedfired · step 5 · plan car_finance · browser + server
5 sent to Meta, once each3 duplicates stopped
One applicant on one URL: five steps, a reload, the back button and a second tab. Five events reach Meta; the three repeats are stopped, each with its reason.

Events with all their details

One event, its parameters, and both copies.

Add value, currency, content ids or your own fields to any event. Pixelonce sends the same parameters to the browser pixel and the server copy, under one event id. Pick an example:

In Pixelonce

Lead standard event

Page
finance-step-3
How often
once per session
When
background submit succeeded
Parameters sent with Lead
ParameterValue
value120
currencyEUR
lead_typecar_finance
step3

event id sc_7f3c91e14a2b

Browser → Meta Pixel

fbq('track', 'Lead', {  value: 120,  currency: 'EUR',  lead_type: 'car_finance',  step: 3}, { eventID: 'sc_7f3c91e14a2b' });

same event id

Your server → Conversions API

{  "event_name": "Lead",  "event_id": "sc_7f3c91e14a2b",  "action_source": "website",  "custom_data": {    "value": 120,    "currency": "EUR",    "lead_type": "car_finance",    "step": 3  }}

Meta gets both copies with sc_7f3c91e14a2b and counts one Lead.

Editing an InitiateCheckout event in Pixelonce: fires when the page loads, once per browsing session, with extra data content_type vehicle, currency EUR and lead_type car_finance.
One event, its timing and its extra data: content_type, currency, lead_type.

03 · Connected to Meta

Two copies, one event id, counted once.

When an event fires, Pixelonce sends it to the Meta Pixel in the browser and posts a copy to your own site, which forwards it to Meta's Conversions API under the same event id. Meta keeps one of the pair, so nothing is counted twice.

If an ad blocker stops the browser copy, the server copy still arrives. Nothing is sent before the visitor gives consent, and the browser stays the only place that decides whether an event fires.

  1. Your website, running Pixelonce, waits for consent.
  2. After consent, the browser sends the event to the Meta Pixel.
  3. At the same time your server sends a copy to the Conversions API under the same event id.
  4. Meta receives both copies, keeps one and counts one Lead.
Pixelonce decides once, in the browser. Meta receives a browser copy and a server copy with the same event id and keeps one.

04 · Consent

No pixel, no cookies and no server copy before consent. Pixelonce reads the WP Consent API, IAB TCF, and Cookiebot, Complianz, CookieYes and Borlabs Cookie, and can also set Google Consent Mode v2.

Events that happen before the visitor decides are held, then sent on a grant or dropped on a refusal — and the fire-once decision was already made when they happened, so nothing doubles up.

● Consent granted · pixel loaded

Held before consent

Sent to Meta after Accept

PageViewViewContent
Before the visitor answers, the pixel is not loaded and events are held. On Accept they are released; on Decline they are dropped.

05 · Debug overlay

See why an event didn’t fire.

Add ?stepcount_debug=1 to any page. The overlay lists every event Pixelonce considered, whether it fired, and the exact reason when it didn't — so “is it tracking?” takes seconds, not an afternoon in Events Manager.

It opens for logged-in administrators on the live site and for anyone on staging, where events run in dry run and are never sent.

Pixelonce debug · /apply?step=2live host
  1. PageView — firedscope revisit · page apply-step-2
  2. InitiateCheckout — firedscope session · event id 7f3c…e1
  3. ViewContent — not firedsuppressed: reload or re-entry from the same rule (apply-step-2)
  4. InitiateCheckout — not firedsuppressed: already fired in this session
  5. Lead — firedbinding ajax:submit_application · success:true

06 · How often

Every event gets a “how often”.

Pixelonce asks a second question for each event: not only which event, but how often may it fire, and keyed on what?

  • Every time — fires on every view.
  • Once per page view — the default for clicks and submits.
  • Once per visit — a reload doesn't count; coming back from elsewhere does.
  • Once per session or once per visitor.
  • Once per thing — once per product, plan or vehicle id.
ViewContent on quote step 1 under four how-often settings
How oftenFirst arrival (car quote)ReloadLeave and come backNext day, car againNext day, van quote
Every time
always
✓fires✓fires✓fires✓fires✓fires
Once per visit
revisit
✓fires✕suppressed: reload✓fires✓fires✓fires
Once per session
session
✓fires✕suppressed: same session✕suppressed: same session✓fires✓fires
Once per thing
entity
✓fires✕suppressed: car already✕suppressed: car already✕suppressed: car already✓fires
One visitor, five moments, one ViewContent event — under four different settings.

07 · Bindings

Counts the submit that worked — not the one that returned 200.

Most application forms submit in the background. A binding watches for a named admin-ajax action (or any endpoint by URL) and fires your event when it succeeds — or when a thank-you panel appears.

No theme edits, no tracking code pasted into templates that the next redesign quietly drops.

POST admin-ajax.php action=submit_application200 {"success":false}✕ not counted
POST admin-ajax.php action=submit_application200 {"success":true}✓ Lead counted
WordPress ajax answers HTTP 200 even when validation fails. The binding fires only on success:true.

08 · Trigger health

Know when a theme update breaks tracking.

A renamed CSS class or a changed form action leaves an event that simply stops firing — and a dead trigger looks exactly like a page nobody used.

Pixelonce records when each click selector, submit selector and binding last matched, and flags the ones that went quiet. No personal data: a trigger key and a time.

Theme updated to 4.2
<button class="btn-apply-now">Apply</button>
TriggerLast matched
ajax: submit_application3 minutes ago
click: .btn-applystale · no match for 7 days
The theme renamed the button's class, so the click trigger stopped matching. The health check flags it as stale.

09 · Setup wizard

A working funnel in about ten minutes.

The first-run wizard is built for someone who has never seen Pixelonce: four steps, one question each, no docs required. Staging copies start in dry run, so you can rehearse safely.

  1. PixelPaste your pixel id. Pixelonce loads it and turns off automatic events.
  2. PagesDescribe each funnel step: a path plus optional query conditions.
  3. Server copyOptional: add a Conversions API token.
  4. TestWalk the funnel with the debug overlay open.
Pixel → pages → server copy → test. Each step asks for one thing and says where to find it.

Inside WordPress

See it on a real funnel.

A car finance form in three steps, priced in euros. Click any screen to see it full size.

Pixelonce's Pages screen in WordPress: one row per funnel step, each with its URL match and the events it fires, with how often each may fire.
Pages: each funnel step, what it matches, and the events it may fire.
The Pixelonce debug overlay on step 1 of a car finance form: consent info, InitiateCheckout skipped because it already fired this session, Schedule fired with step, market de and lead_type car_finance, PageView fired, and ViewContent fired with content_ids hy-440, value 24990 and currency EUR.
Debug overlay: every event on the page, fired or skipped, and why.
Pixelonce trigger health: each click, submit and background-submit trigger with the time it last matched; one trigger is flagged as not seen for 7+ days.
Trigger health: when each trigger last matched, and which went quiet.
Pixelonce server event log: recent events sent to Meta's Conversions API, each with its event id, pixel and result: sent, a retried error, and one dry run on a non-live host.
Server log: every Conversions API send, its event id and Meta's answer.
Pixelonce settings: events sent elsewhere as standard-event checkboxes, live hostnames, and consent options: follow the consent tool, keep events until the visitor decides, set Google Consent Mode v2, and honour Global Privacy Control.
Settings: consent first, with Google Consent Mode v2 and Global Privacy Control.
The Pixelonce setup wizard, step 1 of 4 (Pixel, Pages, Server copy, Test): it asks for the Meta pixel id and explains where to find it.
Setup wizard: pixel, pages, server copy, test. One question per step.

Free, all of it

Everything a funnel needs to report one event per step.

  • Once per step

    Reloads, the back button and second tabs no longer add events. Each event says how often it may fire.

  • Conversions API copy

    A server copy under the same event id. Still counts when an ad blocker stops the pixel; Meta keeps one.

  • Event parameters

    Value, currency, content ids and your own parameters — fixed, or read from the URL or the clicked element.

  • Consent first

    Nothing loads before consent. Reads your consent tool and can set Google Consent Mode v2.

  • Debug overlay

    Every event on the page, fired or not, and the exact reason. Add ?stepcount_debug=1 (the plugin's original name).

  • Trigger health

    Flags buttons and forms that stopped matching after a theme or form change.

  • Background-submit bindings

    Count the admin-ajax or fetch submit that succeeded, not the one that only returned 200.

  • Page caches cleared

    Change a setting and Pixelonce clears the page caches, so visitors get the new rules at once.

  • Setup wizard

    Pixel, pages, server copy, test. One question per step, about ten minutes.

  • Templates

    Starting points for application funnels and WooCommerce. Change anything after.

  • Event log

    Every server send with its event id and Meta's answer. No IP addresses or visitor data.

Free now · Pro coming soon

Start free. Add GA4 and more ad platforms later.

Free

Free

Standard and custom Meta events, with no limits on events, pages or pixels. Conversions API, consent, debug overlay and the rest.

Download free

Pro coming soon

Pricing announced at launch

A separate add-on: Google Analytics 4, priority support, and more ad platforms:

  • TikTok
  • Google Ads
  • LinkedIn
  • Pinterest
Join the Pro waitlist

FAQ

Questions

Something else? Ask us or read the docs.

Who is Pixelonce for?

Sites whose most valuable conversion is an application, not a cart: quote, finance, insurance, loan, booking and enrolment forms, usually with several steps on one URL. It works in any country and any currency.

Is Pixelonce free?

Yes. Install it from the WordPress.org plugin directory (in your dashboard: Plugins → Add New, search "Pixelonce"), or download the zip from this site. It covers all of Meta's standard events and your own custom events, with no limits on events, pages or pixels: the fire-once rules, the Conversions API copy, consent handling, the debug overlay, trigger health, bindings, the setup wizard, templates and the event log.

What will Pro add, and what will it cost?

A separate add-on with Google Analytics 4 and the same fire-once engine for more ad platforms (TikTok, Google Ads, LinkedIn, Pinterest), plus priority support. The free plugin stays complete. Pricing is announced at launch. Join the waitlist to hear first.

Why would my events fire more than once?

Most tracking setups fire an event whenever a page or step is shown. On a multi-step form, a reload, the back button, a second tab or a step loaded in the background all look like a new arrival, so one application can report several InitiateCheckout or Lead events.

Does it work with Meta's Conversions API?

Yes. Each browser event can be copied to Meta's Conversions API from your server under the same event id, so Meta keeps one of the pair. If an ad blocker stops the browser copy, the server copy still counts. The browser stays the only place that decides whether an event fires.

What about consent?

Nothing loads before consent. Pixelonce reads WP Consent API, IAB TCF, Cookiebot, Complianz, CookieYes, Borlabs Cookie, honours Global Privacy Control, and can also set Google Consent Mode v2. You choose whether to follow a consent tool, always require consent, or switch consent handling off where it does not apply.

Do I need to edit my theme or form plugin?

No. Bindings fire events from background form submits that succeed, or when an element appears, without touching templates. You can also fire an event from your own code with StepCount.emit('Lead') — the plugin's JavaScript API keeps its original name.

Can I try it on a staging site first?

Yes. Any host that is not in your live-hostnames list runs in dry run: every event is checked and shown in the debug overlay, but nothing is sent.

Trust the numbers your ads optimise on.

One URL, five steps, one event each, and the reason whenever one does not fire.