Skip to content

WooCommerce & WordPress · Meta · Google · TikTok

Every other plugin sends events. PixelCapi proves they arrived.

Server-side tracking (Conversions API) with deduplication you can verify — event by event, order by order. Built cache-proof, consent-first, EU-ready.

Check your tracking — free See pricing
Purchase fdf4dd5f-9c31-4e02-9a8d-1c7b2f0e0476 browser ✓ server ✓ Matched

You have probably said one of these out loud.

the four proofs

Every other plugin sends events. These four show you what arrived.

One question per proof, answered with evidence you can read yourself.

how it works

Three steps, and the third one is the point.

Cyan is the browser. Indigo is your server. The same event ID travels on both.

  1. step 1

    Paste your keys

    Pixel ID and access token per platform. No container, no tag manager, no second server to rent.

  2. step 2

    PixelCapi fires browser and server with one shared event ID

    The pixel fires in the visitor’s browser. Your WordPress server sends the same event to the platform’s API. Both carry the same event ID, which is how the platform knows they are one conversion, not two.

  3. step 3

    Watch the proof in your dashboard

    Dedup Doctor lists both copies of each event, compares the actual event IDs and shows the platform’s own trace IDs next to them.

under the hood

The parts that decide whether tracking survives contact with a real store.

  • Cache-proof by design

    No per-visitor event ID is ever baked into cacheable HTML. Byte-identical cached pages still produce unique matched pairs — including behind LiteSpeed Cache and other common page caches.

  • Purchase fires from the server first

    The Purchase event comes from your payment hooks, not from the thank-you page. A closed tab or a gateway that never redirects back no longer costs you the sale.

  • Verification that can fail

    The Verify button says what it can and cannot confirm for each platform. Google’s endpoint cannot authenticate credentials without OAuth, so we say that instead of showing a green check that means nothing.

  • Consent gates both halves together

    A denied choice stops the browser event and the server event. Google Consent Mode v2 is supported in basic and advanced modes, and consent is recorded on the order so webhook-time sends respect it.

how we differ

Four differences we are willing to be held to.

Not a comparison with anyone else — a description of how this one is built, and what that means for the numbers you end up trusting.

  • Your server is the server

    PixelCapi runs server-side from your own WordPress server — no GTM containers, no rented cloud hosting.

  • No add-ons at any tier

    Every platform and every capability is included. Tiers differ only by number of sites.

  • No product limits

    Your catalogue size does not decide what you pay or what you can track.

  • Delivery, not dispatch

    We prove delivery event by event. A sent event and a delivered event are not the same thing.

Why PixelCapi is built this way

pricing

One price per number of sites. Nothing else changes.

Everything included at every tier. No add-ons. No product limits. Tiers differ only by number of sites.

  • Solo

    1 site

    $99 / year

    One store you run yourself.

  • Business

    5 sites

    $199 / year

    A few stores, or a freelancer with a handful of clients.

  • Agency

    Unlimited sites

    $399 / year

    An agency running tracking for many client sites.

See what is included 14-day money-back guarantee

questions

The eight things people ask before they install.

Does it work with my cache plugin?

Yes. PixelCapi never bakes a per-visitor event ID into cacheable HTML, so two visitors served the byte-identical cached page still get their own matched pair. It works with LiteSpeed Cache and other common page caches, including a multi-layer REST cache bypass.

Do I need Google Tag Manager?

No. PixelCapi runs server-side from your own WordPress server, so there are no web or server GTM containers to build and no cloud hosting to rent.

Is PixelCapi GDPR-friendly?

Consent gates the browser event and the server event together, so a denied choice stops both. Google Consent Mode v2 is supported in basic and advanced modes, and the consent decision is recorded on the order so sends triggered later by a webhook respect it. Compliance also depends on your own consent tool and privacy notice, which is why we do not claim it for you.

What happens to my customers’ data?

Access tokens are stored server-side only and are never written to logs. Personal data is SHA-256 hashed per each platform’s rules before it leaves your server. IP address, user agent and click IDs are sent raw, because the platforms require them in that form.

Will tracking slow down my checkout?

No. Events go through an async queue with retries, so a slow or failing platform API never holds up a customer’s checkout.

Which platforms does it send to?

Meta via the Conversions API, Google via the GA4 Measurement Protocol and the Google Ads tag, and TikTok via the Events API. Each one gets that platform’s own hashing rules, including multibyte and diacritic case folding and the phone and geo differences between Meta and TikTok. Google Ads Enhanced Conversions is in development and is marked as such in the pricing table.

What is the difference between the free plugin and Pro?

The full side-by-side table is on the pricing page. The split between the free WordPress.org plugin and PixelCapi Pro is being confirmed before launch, so the table marks anything not yet decided rather than guessing.

Can I get a refund?

Yes. There is a 14-day money-back guarantee, handled by Freemius as the merchant of record.

Stop guessing. Start proving.

See what your site is sending right now — read-only, no signup — or go straight to pricing.

Check your tracking Get PixelCapi Pro