Before you add another analytics tool, map the data it will collect
Before adding website analytics or consent tools, map what information each tool collects, why it is needed and where it goes. Assign responsibility for the configuration, privacy review and reporting. A banner is one part of that system; it does not establish that the underlying collection is appropriate or correctly configured.
Put the advice into practice
Give your next major prospect a clearer reason to choose you
Plan the content, design and enquiry pathways around the work you want to win.
Discuss your website projectStart with a data map, rather than a plugin list
A website can accumulate analytics, advertising pixels, chat tools, booking software and form integrations through separate projects. Each addition may have a reasonable purpose, while nobody retains a complete view of what is collected. Begin by listing the tools currently present and the decisions they are meant to support.
Separate business questions from available measurements. “Which service pages produce suitable enquiries?” is a decision-oriented question. Recording every available interaction is a collection strategy, and may include information that is unnecessary for that decision.
Include systems beyond the page itself. A form may send data to email, a CRM and an automation platform. A scheduling tool may introduce another provider. The map should follow the actual path so the responsible team can review it.
Create a tool and purpose register
| Tool or collection | Purpose and information | Owner and review question |
|---|---|---|
| Analytics | Understand page use and defined enquiry events | Marketing: which events are needed for actual decisions? |
| Advertising pixel | Measure or support agreed advertising activity | Campaign owner: which pages and fields must be excluded? |
| Contact form | Receive the information required to assess an enquiry | Operations: who receives it, where is it stored and for how long? |
| Booking tool | Arrange a suitable conversation | Customer team: which information is necessary before the meeting? |
| Consent platform | Manage choices and communicate configured categories | Privacy and developer: does the implemented behaviour match the notice? |
Add provider, account owner, access permissions, storage location where known, retention setting and removal process. Record uncertainty explicitly. A supplier’s broad description of its product does not show which options are enabled on your website.
Keep this register available when commissioning new functionality. It provides a starting point for technical and privacy review, rather than requiring the next team to reconstruct the system.
Review collection in the context of your organisation
The Australian privacy position depends on the organisation, the information and the collection circumstances. Do not assume every business has identical obligations, or that a familiar overseas banner configuration resolves Australian requirements.
The OAIC’s tracking-pixel guidance discusses due diligence, limiting collection, notification and risks involving sensitive information. Use it to inform an appropriately scoped review of the actual implementation. Pages or forms concerning health and other sensitive matters need particular care.
Give the reviewer a concrete inventory: page types, form fields, event names, outgoing destinations and the proposed notices and choices. This is more useful than asking whether “Google Analytics is compliant” without describing how it is used. Obtain professional advice where the review requires a legal conclusion.
Test what happens before and after a choice
Agree the intended behaviour before configuring the consent tool. Identify which tools should operate at each stage, how a visitor changes a choice and what happens to data already collected. The developer can then test the implementation against that specification.
- Open a clean test session and record the initial behaviour.
- Check each available choice and the relevant network activity using appropriate inspection tools.
- Test forms, bookings and confirmation screens without using real sensitive information.
- Check whether changing a choice affects the intended tools.
- Confirm that important website functions still work and the notice matches the tested behaviour.
Retain a short test record with the configuration version and unresolved questions. Revisit it when a plugin, marketing platform or website integration changes.
Keep privacy and measurement quality connected
A technically firing event is not necessarily a useful business outcome. An outbound click, form start and submitted enquiry represent different actions. Label reports accordingly, and agree how an accepted enquiry becomes a qualified opportunity in the business process.
The conversion data audit guide provides a separate way to review reporting definitions. This matters when collection choices or tool changes alter the data available: the team should understand the practical reporting limits.
Finish with ownership. Someone needs authority to approve new tools, remove unused ones, manage access and review the register. That responsibility makes the system easier to maintain as the website and marketing programme develop.
For a new website or integration, include the data register and agreed measurement purposes in the website brief. They affect forms, tools, testing and the handover.
