A tracking inventory records the services a website loads, where they are installed, and their observed behavior. Include analytics, advertising, chat, video, forms, and other embeds rather than checking cookies alone.
Before you begin
Agree on the pages, visitor locations, account states, and privacy requirements to review. Technical observations should support the requirements approved for your business, not substitute for legal advice.
What to do
- List known tools from the theme, plugins, apps, tag manager, and external accounts. Record an owner and business purpose for each.
- Inspect representative pages during a fresh visit. Note requests, cookies, local storage, and embedded frames that appear before any preference is selected.
- Exercise relevant interactions, such as opening chat, playing video, submitting a form, or entering checkout. Some services load only after an action.
- Map each observed service to its installation route and intended category. Flag unknown or duplicate sources for investigation rather than assuming every request has the same purpose.
- Record the test conditions, date, evidence, and gaps. Revisit the inventory after installing an app, changing a theme, or adding an integration.
How to check the result
A useful inventory connects observed behavior with an accountable tool and configuration. A clean result on one page does not establish that the entire website or every region behaves identically.
If you need help
Send selected URLs, tool names, and redacted observations when requesting a review. Network captures can contain session identifiers or personal information, so share them only through an approved private route.
Related help
- Test what happens when a visitor accepts or rejects cookies
- Understand what Google consent mode does in a website setup
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
