Give us a domain and an email, and confirm from the link we send there. We fetch your home page the way a visitor loads it, run the nine checks below, and email you what we found. No account, no card, no Facebook login, and no call.
What it is not: an audit of your ad account. Reading a Meta ad account needs OAuth, which needs an account. Nothing in the report is a claim about your campaigns, your spend or your results, because nothing here has seen them.
All of them are read from one public page fetch. Where a check cannot be answered from outside, the report says so rather than guessing.
Meta Pixel
Whether the pixel is in your page source, or behind a tag manager where a page fetch cannot see it.
Something to convert on
A form, a cart, a booking link. An ad landing on a page with none of those has nowhere for the spend to go.
Mobile viewport
Most paid social traffic is on a phone. No viewport tag means desktop-width rendering and an instant bounce.
HTTPS
Meta will not run traffic to an insecure destination.
Page weight
The size of the HTML document and how long our server waited for it.
Page title
The first thing a click lands on and the first thing a model reads when it summarises you.
Meta description
What a search engine or an assistant quotes when it decides whether to send you the click.
Link preview tags
What your link looks like when it is shared, and what an ad's destination preview shows.
Server-side conversions
Whether the page carries the event id a paired Conversions API setup puts on browser events.
Because it is the half nobody audits. Media buyers rebuild creative for months while the page it lands on drops half the traffic before the offer renders, or fires no pixel so the campaign optimises on clicks and never learns what a sale looks like. Those are cheap to fix, and you do not have to give anyone access to your account to find them.
The other half needs your ad account, and that is what AutoAdy is for. If the report is useful, connecting Meta takes one click and the real audit runs against live data.
No. No account, no card, no Facebook login. You give a domain and an email, confirm from the link we send to that address, and the report arrives by email. That is the whole exchange.
No, and it cannot. Reading a Meta ad account needs OAuth, which needs an account. Anyone offering an ad-account audit from a domain alone is describing something they did not do. This reads one public page: your home page, exactly as a visitor loads it.
The page your ads land on decides whether the spend converts, and it is the half of the funnel most advertisers never audit. A missing pixel means Meta optimises on clicks rather than sales. A missing viewport tag means every phone bounces. Those are cheap to fix and expensive to miss, and you do not need to give anyone access to find them.
We are not going to give you a number we cannot yet keep. The work itself is one page fetch and takes seconds; what decides the wait is how often the queue is worked, and we would rather say that than publish a deadline and miss it. Once you confirm, you get one email with the report, when it is done.
Send you a link to confirm the request, then the report. Nothing runs until you confirm, so nobody can have a report sent to an address they do not read. You are not added to a list and there is no sequence behind it. If you want the real thing afterwards there is one link in the email, and ignoring it costs you nothing.
Not on the same domain from the same address while one is queued or already delivered. You would get the same report, and sending it twice is not a service. A different domain is fine, up to five a day from one connection.