# Conversion Leak Report

Scan any site's conversion tracking for free: which ad pixels fire, which wait for consent, which keep sending after Reject, and which networks reach a server.

The Conversion Leak Report scores how much conversion signal a site loses before its ad platforms see it, and lists the fixes worth the most.

It is free, reads the page only and changes nothing on the site.

## What it checks

- **Pixels.** Which ad networks the site tracks (Meta, Google Ads and GA4, TikTok, LinkedIn, Pinterest, Snapchat, Reddit, X, Microsoft and more), and which are installed but never fire.
- **Server-side path.** Whether each network also receives conversions from a server, through a conversions API, a server-side Tag Manager or the Zernio tag.
- **Consent.** The scan loads the site in a real browser, answers the cookie banner, and reports pixels that fire before it is answered and tracking that keeps sending after Reject.
- **Cookie life.** How long Safari keeps the tracking cookies, and whether the tag loads from a path of the site's own domain.

Visitors who decline consent are never counted as lost.

## Scan a site

On the web, enter a domain at [is-bleeding.com](https://is-bleeding.com). Each homepage scan that could read the site's pixels becomes the host's public page, such as `is-bleeding.com/yourshop.com`.

In a terminal:

```bash
npx is-bleeding yourshop.com
```

`--prompt` prints only the fix prompt, ready to pipe into a coding agent, and `--json` prints the raw response.

```bash
npx is-bleeding yourshop.com --prompt | claude
```

Over the API, [`GET /v1/conversion-audit`](/conversion-audit/audit-conversion-tracking) runs the same scan. The key is optional; without one, an IP address gets 20 scans a minute.

```bash
curl "https://zernio.com/api/v1/conversion-audit?url=yourshop.com" \
  -H "Authorization: Bearer $ZERNIO_API_KEY"
```

[`GET /v1/conversion-audit/latest`](/conversion-audit/get-latest-conversion-audit) reads a host's stored report without scanning again. Through the [MCP server](/mcp/tools), the tools are `conversion_audit_audit_conversion_tracking` and `conversion_audit_get_latest_conversion_audit`.

## Watch a domain

Choose **Watch this domain** on a report, or call [`POST /v1/conversion-audit/monitors`](/conversion-audit/create-conversion-audit-monitor) with `url`. Zernio rescans the homepage every day and emails you when tracking breaks:

- the score drops 5 points or more
- an ad network stops tracking or stops firing
- a pixel starts firing before the cookie banner is answered
- a server-side path disappears

A second scan confirms the break before any email goes out. The email lists what changed and the prompt to fix it.

An account watches up to 25 domains, listed in the dashboard under Conversions, then Watched sites, and with [`GET /v1/conversion-audit/monitors`](/conversion-audit/list-conversion-audit-monitors).

## Audit Meta from the inside

The public scan only sees the browser. Once a Meta ad account is connected, [`GET /v1/conversion-audit/meta-audit`](/conversion-audit/get-meta-conversion-audit) reads what Events Manager recorded for the pixel over the last 7 days:

- volume per event, its daily trend and when each was last seen
- the share sent from a server
- Event Match Quality, with the coverage of each customer key
- deduplication coverage (`event_id`, `external_id`, `fbp`)
- Meta's own diagnostics and failed dataset checks

Each finding carries its fix and who makes it: Zernio, you or Meta. The dashboard shows the same under Conversions, then Destinations, on each Meta connection.

## Fix what it finds

The report's fix prompt and [Fix conversion tracking with an agent](/products/server-side-tracking/fix-with-agent) take a site from leaking to verified.

The agent connects the ad accounts, installs the Zernio tag, serves it from your own domain, forwards each network's conversions and rescans.

A network turns `good` once the site's events reached its pixel in the last 7 days.

## How it behaves

- **Public reports.** A homepage scan that could read the site's pixels replaces the host's public report.
- **Rendered or not.** When the page cannot be rendered, the scan falls back to the page source and says so; a fallback scan is never compared with a rendered one when watching a domain.
- **Limited visibility.** `report.visibility: "limited"` means some pixels load through a tag manager or store platform, so part of the setup cannot be seen from outside. It does not mean tracking is missing.

## Related

- [Fix conversion tracking with an agent](/products/server-side-tracking/fix-with-agent)
- [Server-side tracking](/products/server-side-tracking)
- [Consent](/products/server-side-tracking/consent)
- [Serve the tag from your own domain](/products/server-side-tracking/own-domain-path)