Tracking Pixels: What Is Your Website Sharing?

A tracking pixel can take minutes to install and much longer to explain properly. What information leaves the site? Which pages trigger it? Who receives it? Tracking pixels deserve those questions before someone ticks the box in an advertising platform and moves on to the next launch task.

This article is general information only, not legal, privacy or regulatory advice. Obligations depend on the organisation, industry, jurisdiction, technology and circumstances. Check current regulator guidance and obtain independent professional advice where appropriate, particularly where sensitive information may be involved.

Give tracking pixels a defined purpose

Ask the team to finish one sentence: we need this tool to help us decide what. A clearer reporting question may reveal that a less intrusive approach could meet the need. Installation should follow a reviewed purpose, not stand in for one.

Do not install a pixel simply because it appears in a platform setup checklist. Ask whether the intended benefit is clear, whether a less intrusive approach could answer the question and who will own the configuration after launch.

For a hypothetical service business, the initial need may be a reliable count of suitable enquiries. That does not automatically establish a need to share detailed browsing behaviour with multiple advertising providers.

Map what the website actually sends

A website tracking audit needs to establish what happens in practice. Memory is not a reliable inventory. A tool may arrive through a tag manager, an embedded service or an integration someone added months ago. Ask a technical specialist to examine the implementation and explain the information flows.

Ask the relevant specialists to identify:

• The pages and events where each tool operates.
• The information included in requests to other services.
• The recipients and intended uses of that information.
• The settings that change what is collected or shared.
• The person responsible for configuration and review.

Pay attention to page addresses, event names and free-text fields. Depending on the implementation, seemingly ordinary technical information can reveal more about a visitor than the team expects.

Bring technical and privacy review together

Bring the technical findings and the privacy review into the same conversation. A policy can say one thing while the configuration does another. The people assessing obligations need an accurate account of the site, and the people implementing changes need a clear, reviewed set of requirements.

Review the purpose, relevant notices, any consent requirements and the handling arrangements that apply to the specific situation. Do not assume that adding a banner, using a server-side setup or changing a platform setting resolves every issue.

For services involving health or other sensitive circumstances, the nature of the page itself may be important. Review the context as well as the obvious form fields before deciding whether a tool should operate there.

Test the agreed behaviour

Ask for evidence of the agreed behaviour before launch. If the setup includes choices or restrictions, test those states too. This should sit inside the campaign launch process, so the review is not squeezed into the last few minutes before media starts.

Record the approved configuration and the date of review. Include checks after significant site changes or new integrations. A tool that was configured appropriately at one point may behave differently after an update or an added feature.

If a review identifies an unexpected information flow, investigate it promptly with the appropriate technical and professional support. Avoid making an immediate claim of compliance or non-compliance without understanding the circumstances.

Assign ongoing ownership

Name the person who coordinates changes, even when the decisions involve several specialists. Without that ownership, a reviewed setup can become an undocumented one as new tools are added. Keep the inventory somewhere the next person working on the site can find it.

Understand the information flow before launch

Start by asking for a current list of tracking tools, their purposes and their owners. Then identify what remains unknown about the information each sends. That gives technical and professional advisers a concrete starting point for review, rather than a vague request to confirm that the website is fine.

Allow time for the review within the wider rollout by building a practical 90-day marketing plan. Explore our AI and technology services for support with the technical side of the implementation, alongside appropriate independent professional advice.