about
Built by someone who got burned by broken tracking.
PixelCapi did not start as a product idea. It started as a store owner discovering that the ad platform and the shop had been telling two different stories for months — and that every tool in the stack was reporting success while the numbers quietly disagreed.
The uncomfortable part was not that tracking broke. It was that nothing anywhere said so. A pixel that stops firing looks exactly like a quiet week. A duplicated event looks exactly like growth. A green “connected” badge looks exactly like proof, right up until you check. That is the gap PixelCapi was built to close: not sending more events, but showing you what actually arrived.
Everything in the product follows from that. The event ID comparison exists because “deduplication is enabled” is a setting, not evidence. Purchase fires from payment hooks because a thank-you page is the least reliable part of a checkout. The verification button is allowed to say no because one that cannot fail tells you nothing.
TODO(owner) — this section needs your specifics: your name, a short bio, the store, and what the actual discovery was. It should read as one person’s account, not a company voice. A photo is optional; a stock photo is not an option.
how we work
Five rules this site is held to
These are checkable. If you find this site breaking one of them, that is a bug, and we want to hear about it.
- rule 1
No social proof we did not earn
No testimonials, no star ratings, no user counts, no client logos and no “as seen on” badges appear anywhere on this site. When there are real WordPress.org reviews, they will be quoted word for word with attribution, and the rating in our structured data will mirror the real number.
- rule 2
No numbers we cannot show you
You will not find a claim that PixelCapi recovers some percentage more conversions. We do not have that number for your store, and inventing one would be the same trick the rest of the category plays.
- rule 3
The roadmap is labelled as a roadmap
Capabilities still in development carry a badge on every surface where they appear — feature cards, feature pages and the pricing table — and their pages are written in “is designed to”, not “does”. Selling the roadmap as the product is how trust gets spent early.
- rule 4
Verification that is allowed to fail
A check that always turns green is decoration. PixelCapi states what it can and cannot confirm per platform — including that Google’s endpoint cannot authenticate credentials without OAuth — instead of showing a checkmark that would pass either way.
- rule 5
Comparisons are dated and sourced
When we publish a side-by-side against another plugin, every fact about it carries the date it was verified, and the page says who should choose the other product. Comparisons written any other way are advertising wearing a lab coat.
The fastest way to judge us is to use us.
Run the free checker on your own store, then decide whether anything here is worth paying for.