Overview
When you're trying to understand why a tag or request fired on your page, there are actually two different questions you might be asking and ObservePoint answers one of them, not the other.
What put this tag on the page? - This is a question about the Load Chain (also called a loader). It asks which technology is responsible for deploying the tag in the first place.
What caused this specific network request to fire? - This is a question about the Initiator Tree. It asks what triggered the request at the moment it happened.
These sound similar, but they answer different things. ObservePoint reports on initiators, not loaders, so it's important to know which question you're actually asking before you go looking for the answer.
| Load Chain (Loader) | Initiator Tree |
Question it answers | What put the tag on the page? | What triggered this request? |
What it shows | The technology responsible for deploying a tag (e.g., a tag management system) | The chain of scripts, requests, or actions that caused a request to fire, as reported by Chrome |
Does ObservePoint report this? | No, not definitively | Yes |
Think of it like a row of dominoes: the loader is whoever set the dominoes, while the initiator is whoever tipped over the first domino. Knowing which domino got tipped doesn't always tell you who set up the row, and that's exactly the gap between these two concepts.
What ObservePoint's Initiator Data Shows You
ObservePoint's initiator data can tell you:
What initiated a network request: the specific script, request, or action that caused it to fire.
The chain of requests leading up to that request: the sequence of parent dependencies that shows how the request came to exist, in the order Chrome observed them.
Chrome's initiator relationships: the same initiator/request relationships you'd see in Chrome DevTools' Network tab, surfaced directly in your Audit or Journey data.
Whether a tag is hardcoded on the page: by running a Blocked Tags audit scan against your tag management system, you can identify tags that are firing outside of that TMS.
ObservePoint's initiator data cannot definitively tell you which system loaded a tag, or confirm whether GTM, Adobe Launch, Tealium, or another TMS deployed it. This is a byproduct of how ObservePoint gathers data: it observes what happens in the browser, in real time, the same way Chrome does, without visibility into a TMS's own configuration or container, so it can describe what fired and what triggered it, but not which system loaded it in the first place.
Questions You Can Answer With Initiator Data
Because ObservePoint reports on initiators rather than loaders, it's best suited to answering questions like:
What fired this request: a specific script, another request, or a user action?
What's the full chain of parent requests behind this request being on the page?
Is this tag piggybacking on another vendor's script?
Did this tag fire straight from the page's HTML, or was it called by another script downstream?
Is this tag hardcoded outside your tag management system? (Check with a Blocked Tags audit scan.)
Where to Find This Data in ObservePoint
Initiator and Load Chain data live in the Initiators section of the Page Details Report, which distinguishes between the two directly:
Initiator (the "Trigger"): a real-time snapshot of the specific action that fired the request.
Load Chain (the "Ancestry"): the request's structural family tree, showing the sequence of parent dependencies.
You can view this data in both Chart View and List View, and export it for further analysis.
Conclusion
Initiator Trees and Load Chains answer two different questions: what triggered a request, versus who put the tag on the page. Knowing which one you're looking at and reading ObservePoint's initiator data with that question in mind will keep your governance conclusions accurate.