Troubleshooting

DNS never verifies

• Check the record exists: dig CNAME track.yourdomain.com (or an online DNS checker) should show prism.binarybloom.dev.
• Cloudflare users: the record must be DNS only (grey cloud). Proxied records break certificate issuance for the tracking hostname.
• Typos: the host is track (not track.yourdomain.com.yourdomain.com — some providers append the domain automatically).
• Propagation: allow up to an hour; the dashboard re-checks automatically.

DNS verified, but no events ("Snippet installed" stays amber)

• Is the snippet actually on the page? View source and search for prism.js. On WordPress, check the page wasn't cached before the snippet was added (purge caches).
• Check the browser console for errors on https://track.yourdomain.com/prism.js — a 404 means the client ID in the snippet URL is wrong; a certificate error means DNS/SSL isn't done issuing yet.
• Rocket Loader (Cloudflare): make sure the script tag keeps data-cfasync="false", otherwise Rocket Loader defers it and click IDs on the landing URL can be missed.
• Content-Security-Policy: if the site sends a CSP, allow https://track.yourdomain.com in script-src and connect-src.
• Consent managers: if the snippet is gated behind consent, no events fire until consent is given — test with consent accepted.

Events arrive, but Meta shows fewer (delivery gap)

The client page's Event delivery card compares what Prism sent against what Meta reports. Common causes for a gap:

• Restricted ad category — Meta silently drops standard event names (Lead, Schedule, …) for special-category advertisers. Fix: remap to custom event names in the dashboard. Prism's diagnostics flag this case.
• Invalid or expired access token — surfaced as an Integration Health error; regenerate the token in Events Manager and reconnect.
• Deduplication — if the site also runs a Meta pixel, deduped events are expected and not a problem.

Conversions missing in Google Ads

• Auto-tagging off or a redirect stripping gclid from the landing URL — check that ad clicks land with ?gclid=... present.
• Event not mapped — only events mapped to a conversion action in the wizard are uploaded.
• Reporting lag — Google attributes uploaded conversions to the click date, and reporting can lag a few hours.

Testing without polluting data

Append ?prism_test=TEST12345 (your code from Meta Events Manager → Test events) to any page URL — every event from that browser tab routes to Meta's Test Events instead of the live dataset. See Verifying your install.

Still stuck?

Your agency can run Prism's full diagnostic suite from the client page (Integration Health → Run checks), which tests credentials, dataset reachability, category restrictions, and more with specific remediation links.