Debug
Pixel not firing: stop starting in Ads Manager
Empty Events Manager is a site problem first. View source, then the network tab, then duplicates. Caply’s scanner does the first two.
If Events Manager is empty, do not rebuild the campaign. Open the site.
1. View source — not DevTools Elements
Look for the Pixel script. A cookie banner that injects Pixel after consent looks “missing” on first paint. The public scanner reads HTML; Pro deep scan uses a real browser for apps that paint late.
2. Network filter: Pixel requests
Tag in the page, no request: consent, an ad blocker, or a JavaScript error before the Pixel fires.
3. Count Pixel IDs
Two IDs on one page split diagnostics. The scanner lists them.
After the Pixel works
Turn on server-side tracking with the same checkout ID. A healthy Pixel with no server events still under-reports iOS. Scan the URL, then connect the Pixel in Caply.
Developers: install details live in /docs.
Caply
Match Forecast on every purchase. Tracking radar on competitor storefronts. Managed server-side tracking without a tagging server.
Start 14-day trial