Technology stack
The technology stack view detects what is actually running on your domain — the CMS serving your pages, the analytics and martech tags firing on them, the JavaScript frameworks behind them, the CDN in front of them, and the server software underneath. It is the fastest way to confirm what you think is deployed is really deployed, and to spot what is deployed that shouldn’t be. Detections come from VisibilityIQ and are grouped first by technology group, then by category, so you can scan the whole stack at a glance.
What you’ll need
Section titled “What you’ll need”- A project with a verified domain.
- Available monthly data budget — a detection scan consumes from the project’s included budget.
How to use
Section titled “How to use”Open the project, go to Domain Intel → Technologies, and click Detect stack. VisibilityIQ scans the domain and returns every technology it identifies, organized by group and category. The scan is on-demand: nothing runs until you trigger it, and the same button refreshes a stale result later. Each detection records when the technology was last seen so you can tell a fresh finding from one carried over from an earlier scan.
How to read the results
Section titled “How to read the results”Detections are grouped by technology group (for example, Analytics, CMS, or CDN), then split into categories within that group. Each row names the specific technology and shows when it was last seen on the domain.
| Field | What it tells you |
|---|---|
| Group | The high-level family — Analytics, Advertising, CMS, JavaScript framework, CDN, web server |
| Category | The narrower role within the group |
| Name | The specific product or library detected |
| Last seen | When the most recent scan confirmed it on the domain |
Read the list for three things. First, confirmation: is the tag or framework you expect present everywhere it should be — for example, is your analytics tag actually firing site-wide? Second, surprises: third-party scripts you didn’t authorize or forgot about often show up here, and each one is weight that can slow your pages. Third, intelligence: run it against a competitor’s domain to see the stack they chose. A detection is an observation, not a verdict — confirm anything unexpected against your own deployment.
Refreshing the data
Section titled “Refreshing the data”Click Detect stack again to re-scan. A refresh pulls current data and consumes from the project’s monthly budget, so refresh when something has changed — a migration, a new tag manager container, a CDN switch — rather than on a schedule. The last-seen timestamps make it clear which detections came from the latest scan.