CHYP.ai · ORBIT // Cloudy_Day Security Suite

★ CHYP.AI TAG INSPECTOR · INVESTIGATE

Tag Investigator — did it fire?

Import a browser network capture (HAR file) of your page to see which tags actually ran: loaders, fallback iframes and event requests, with where they went.

HAR files can contain sensitive data. This page reads it only in your browser.

How to save a HAR file (Chrome, Firefox, Safari)

Use a fresh private window for each capture, load your page once, wait a few seconds, then save. For a consent comparison make three captures of the same page: one without touching the banner, one after Reject, one after Accept.

  • Chrome / Edge: open DevTools (F12) → Network, tick Preserve log, load the page, then click the download arrow (Export HAR (sanitized)).
  • Firefox: open DevTools (F12) → Network, load the page, then right-click any request → Save All As HAR.
  • Safari: enable Settings → Advanced → Show features for web developers, open Web Inspector → Network, load the page, then click Export.

Even sanitized captures can include URLs and page content: keep them private.

Advanced: exact page and first-party collector paths

Matching requests show as first-party collector candidates. A capture can’t show where your server forwards them.

What it shows & its limits

For Google Tag Manager, Google tag, GA4, Google Ads/Floodlight and Meta Pixel it shows each request’s destination host and path, method, HTTP status, tag ID, standard event name, parameter names and the script that started it (when the browser records it), and links tag IDs back to what the page’s HTML declares.

As soon as a file is opened it is reduced to those facts: cookies, headers, request bodies, response bodies and other query values are dropped (the page’s own HTML is read once for tag declarations, then discarded). Nothing is uploaded or stored, and the export contains only the minimized report.

A request in a capture doesn’t prove data was collected or that consent rules were met. The exact GTM firing rule needs access to your container, and a capture can’t see server-side forwarding from a first-party collector. Consent labels are the ones you choose.