Measurement

How to make a cookie and tracker inventory for a small business website

Identify the technologies your website uses, their purposes and the choices visitors should receive.

By Graphic Core   /   Published
Monthly guide series: September 2023

Translucent browser-shaped panels linked by circular tokens beside a shield-shaped paper cutout.

Know what the site actually uses

A cookie banner is only one part of managing website privacy. Start by identifying the technologies your website and its suppliers actually use, what they do and whether they store information on or access information from a visitor's device. This can include cookies, local storage, pixels, tags and some embedded services; the label a supplier gives a tool does not settle the question.

An inventory helps the person responsible for the site understand what changes when a booking form, map, video, analytics tool or advertising service is added. The ICO's current guidance covers storage and access technologies more broadly than traditional cookies. Where personal data is involved, data protection requirements may apply as well.

List services, purposes and providers

Create a table with the service name, provider, purpose, technology, duration or expiry, where it runs and any third parties receiving information. Identify the owner responsible for checking each entry. Ask the hosting, security, web development and marketing suppliers what their components do, and check whether an embedded service introduces its own technologies.

Be precise about purpose. A security control and a personalised advertising tag may use similar technical methods but serve different purposes. A tool described as 'essential for marketing' is not automatically strictly necessary to provide the service a visitor requested. Record uncertainty and investigate it rather than filling the inventory with assumptions.

Check the applicable rules and exceptions

The ICO explains that storage and access generally require consent unless a relevant exception applies. Its current guidance describes several exceptions, including a statistical purposes exception with specific conditions and an objection requirement. Do not assume every analytics tool qualifies: review exactly what is collected, why it is used, who receives it and whether the conditions are met.

Advertising or profiling uses may fall outside that exception, and a technology used for multiple purposes needs particular care. If consent is required, obtain a valid choice before the relevant technology is used and explain the purposes and third parties. Review the current ICO guidance and obtain specialist advice where the setup is unclear.

AT A GLANCE

Review a website technology

  • What is used?List the technology and provider
  • Why is it used?Record the precise purpose
  • What rule applies?Check consent or an exception
  • Does the choice work?Test the real implementation
Use the current ICO guidance for the actual configuration.

Check the experience a visitor sees

Where choices are needed, describe them in plain language and make the available options easy to find and use. Test a first visit, acceptance, refusal, changes to a choice and any route for withdrawing or objecting where applicable. The controls need to affect the actual technology; a visual banner alone does not prove that a tag has stopped.

Check on different browsers and devices and after clearing previous choices, following a documented test plan. Some provider behaviour can change with configuration or updates. Ask the person implementing the site to verify both what is visible and what loads, while avoiding collection of real visitors' personal data during testing.

Keep the notice accurate

A cookie or privacy notice should reflect the actual providers, purposes, durations and choices for the live setup. Avoid copying a generic list from another business or claiming a third party receives no information before checking. Link to relevant provider information where it helps a reader understand what happens.

Update the notice and controls when a new feature is introduced, not only during the initial website build. Give the business a named owner for the inventory and a process for approving changes. Search Console by itself is different from adding a visitor analytics tag; check the technologies installed rather than assuming every Google service has the same effect.

An illustrative inventory

Imagine a small company uses hosting, a consent-choice storage item and an embedded booking service. The site owner asks each supplier what is stored or accessed, lists the purpose and duration, and checks whether the booking embed loads before the visitor makes any relevant choice. If the answer is unclear, the team resolves it before enabling that feature.

This is an invented scenario, not a statement that a particular provider is compliant. The correct treatment depends on the actual configuration, purpose and current law. Keep a dated record of the check and retest if the booking provider or its scripts change.

A sample inventory row and release check

For each technology, use a row with a descriptive name, provider, precise purpose, where it loads, storage duration, recipient and the person who verified it. Add a column for the relevant choice or exception and the date of the check. If the supplier cannot yet explain a third-party embed, mark the row as unresolved instead of describing it as necessary by default.

For example, a hypothetical booking widget may appear on a contact page and load code from a separate provider. The business should ask what it stores or accesses before and after interaction, whether any information is shared, and whether the control settings affect it. A screen label alone will not answer those questions. The appropriate rules depend on the real configuration and current ICO guidance.

Before enabling a new service, compare the inventory with the privacy notice and test the relevant accept, refuse, withdrawal or objection route. The ICO's statistical-purposes exception has specific conditions; it is not a blanket exemption for all analytics or advertising. Keep a dated record of the test and repeat it when the supplier changes its implementation.

Include scripts loaded by a tag manager and assets brought in by embedded maps, videos or booking tools. Ask whether the code starts before the visitor interacts with it and whether a third party receives information. If a provider changes its script or purpose, the previous assessment may no longer describe the live site; repeat the check and update the inventory and notice as needed.

Review after a change

Before launch or a significant update, compare the live site with the inventory, confirm who has checked each item and test the actual choice mechanism. Look for tags added through a page builder, marketing platform or third-party embed as well as those in the main site code. Check that a visitor can find the notice and relevant settings.

Schedule a repeat review when suppliers, purposes or tools change. Record the version checked and any issue that needs specialist input. A small accurate inventory that is maintained is more valuable than a long copied list that no longer describes the site.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION