No signup, nothing stored. Checking somebody else's site is fine: this only reads what every visitor's browser already downloads.
This checks the page your address serves to a normal visitor, the same way a browser would, and it opens any Google Tag Manager container it finds and reads inside it. Nothing is stored, no signup is asked for, and the answer is the same one you would get by opening the page source yourself with more patience than most people have.
What counts as a conversion event
PageView means a human loaded a page. Lead, Contact, Schedule, Purchase and Submit Application mean a human did the thing you are paying to make happen. Only the second group can train the ad platform or answer what a booked job costs. A campaign running on PageView alone is being optimised for people who open pages, and there is an endless supply of those.
How to check it yourself in two minutes
Open Meta Events Manager, pick your pixel, open Test Events, then fill in your own form on your own site while watching that screen. Whatever appears is what Meta actually receives. If only PageView appears after you submit, the form submission is not being reported no matter what the setup documentation says. Google Ads has the same thing under Tools, Conversions, where the status column reads No recent conversions when a tag has quietly stopped.
The failure that hides for months
Conversion tags break silently. A form plugin is updated and the thank you page URL changes, so the trigger listening for the old URL stops firing. Nothing errors, nothing alerts, and the ads account keeps spending. The first sign is usually cost per lead climbing for no visible reason, months after the actual break. Checking after every site change is the cheap habit that prevents it.
Why your inbox holds more leads than your ads account reports
Browser side tracking loses conversions to ad blockers, tracking prevention and people who decline cookies. The platform then undercounts, you judge campaigns as worse than they are, and you turn off ads that were actually working. Reporting the same conversion from your server as well, through the Conversions API, is what closes that gap, and it is the single upgrade with the clearest effect on reported results.
Common questions
What does this actually detect?
Whether the page fires any Meta event other than PageView. It reads the page and, when a Google Tag Manager container is present, reads inside the container too. It cannot see events that only fire after a click, so a form that reports on submission may show as no here while still being correctly set up. Meta's own Test Events screen is the definitive check for that case, and it takes two minutes.
My agency says conversion tracking is set up. Why does this say otherwise?
The most common reason is that it is set up on the thank you page only, which is correct, while you checked the home page. Check the page people actually land on after converting. If that page also reports nothing, the setup is worth a second look.
Does this work for Google Ads conversions too?
This page reports whether Google Ads tags and a tag manager are present, but the conversion event detail here is Meta specific. For Google, the reliable check is Tools, Conversions in the ads account, where each action carries a status.
Is a conversion event the same as a goal in Analytics?
They are related but separate. A GA4 key event tells you what happened on your site. A conversion event sent to Meta or Google Ads tells the ad platform, which is what lets it optimise. Having one does not give you the other.