Network request capture
To understand data sharing on your site, you need to know how technologies load, and which domains they talk to. Tagmaps captures every single network request, giving you the most granular details possible.
Your website code does not paint the whole picture
The HTML of your site will show you what you're loading. But what about a tool that loads another tool? Or a tool that changes it's URLs over time? A single JavaScript file you add for marketing, could load and share data with an unlimited number of other 3rd-parties.
The only way to see everything is to load it, and watch. Tagmaps does exactly that, recording every single network request, so you can see exactly where data is going.
How network request capture works
The page loads in a real browser
Tagmaps opens each page the way a visitor would, so scripts run and load whatever resources they would on a user's device.
Every request is recorded
As the page loads, Tagmaps captures each request: the domain, the type, the timing, and the response.
The initiator chain is traced
Tagmaps records how each network request is made, capturing the details on how every object gets loaded.
The requests are visualized
Network requests are visually laid out on a map, showing you a hierarchy that allows you to track which tools load other tools.
What gets recorded for every network request
Metadata about the request can tell us almost as much as the domain.
- The domain each request was sent to, and whether it is first or third-party
- What initiated the request, identifying what you added to your site versus what was piggybacked
- The HTTP method, telling us if data is being sent or received from a domain
- The type of request, such as a script, a page, an image, an API, and more
- The HTTP status, which can identify broken code, or requests used for tracking purposes
Network request capture FAQs
Why load the page in a real browser?
Many requests only happen when scripts actually run. A page loaded in a real browser fires those requests the way a visitor would trigger them, so Tagmaps records what really happens rather than guessing from the source code.
How can I see the results?
Tagmaps will visually represent all network requests on the Initiator Map, to clearly lay out how each request is made, and the initiator chains. Additionally, the results are presented in a table format.
What detail is captured for each request?
For every request Tagmaps records the domain, initiator, first or third-party, request type, HTTP method, HTTP status, and more.
Are there any network requests that Tagmaps doesn't capture?
No. Everything is recorded.