This is a common and understandable question.
Sealmetrics uses a very simple and strict conversion pixel:
If the pixel is called, it counts. If it’s not called, it doesn’t.
That means:
Every time the conversion pixel URL is triggered, we count a conversion.
We don’t filter for deduplication, user uniqueness, or match it with backend validations.
We don’t access your ERP or checkout system—we only record the pixel event.
Common reasons for discrepancies:
Duplicate pixel fires
If a user refreshes the thank-you page, the pixel may fire again. This will count as a second conversion.
Multiple user visits to confirmation pages
If users revisit the confirmation URL (via email links, bookmarks, or back button), the pixel fires again.
Pixel placed on the wrong URL(s)
If the pixel is not exclusively on the final “thank you” page, it might be firing on other pages as well, leading to overcounting.
Lack of server-side validation
Unlike your ERP, we don’t verify payment success or customer info. If someone abandons the cart but still loads the confirmation page, we’ll count the conversion.
How to fix it:
Make sure the pixel is placed only on a unique, non-cacheable “thank you” page.
Use server-side conditions (e.g., only firing the pixel if the order is confirmed).
Consider firing the pixel only once per session using logic on your side.
Sealmetrics will always show exactly what is triggered, nothing more, nothing less. If the ERP shows fewer conversions or revenue, it’s likely because the pixel is firing more often than it should.