Consent is a user decision, not a banner
A banner does not make measurement responsible by itself. The plan must explain which purposes exist, which technologies are involved, what choices a person can make, and how the system honors those choices. Essential, analytics, and marketing tags may need to behave differently; grouping them under one generic button makes consent harder to understand and control. Implementation should follow the requirements that apply to the specific case and remain consistent with the published disclosures.
The marketing team should not treat this article as legal advice. Legal basis, transparency, sharing, retention, rights and contracts need to be validated with qualified professionals. The ANPD publishes official guidance that helps structure the right questions, but it does not replace an analysis of the organization and its specific purposes. Record the approved decision and its source so the technical configuration does not become an unsupported interpretation. Validation should include third-party code outside the tag manager because its container does not control everything loaded on the page or through external services.
- List purposes and technologies before choosing the interface.
- Separate essential, analytics, and marketing tags according to the approved policy.
- Document consent, refusal, changes, and withdrawal where applicable.
- Submit the design for review by the appropriate legal professional.
Map each purpose, tag, and data point
Create a matrix connecting each purpose, tag, event, provider, data point, destination, and retention period. The goal is not to produce a decorative list, but to explain what each technology does and why it is active. Include direct scripts, pixels, chat tools, testing and server-side integrations. If a tag has no owner or justification, place it under review before allowing it to load by default. The technical configuration needs to reflect this documented decision, without expanding the collection because a platform offers an additional resource or a more convenient report.
The same action can feed tools with different uses. A form event may be needed to confirm functionality and may also be used separately for advertising. Do not assume that authorization for one purpose is valid for all. The documentation should show firing conditions, the assigned category, parameters sent, and the mechanism for stopping collection. The simpler the matrix, the more likely it will be maintained after launch. Validation should include third-party code outside the tag manager because its container does not control everything loaded on the page or through external services.
- Link purpose, tag, supplier, data and destination.
- Include direct scripts and integrations outside the container.
- Separate functional use from analytical or advertising use.
- Assign owner and review for each technology.
Make your tools honor the user's choice
Technically, the user's preference must reach the triggers before conditional tags fire. Test first visit, refusal, partial acceptance, subsequent change, expiration and return. Watch network, cookies, storage, data layer and destinations. The interface copy must match actual behavior: do not offer separate categories if the container treats them as one authorization. The technical configuration needs to reflect this documented decision, without expanding the collection because a platform offers an additional resource or a more convenient report.
Validation must also cover pages and vendors the team does not consider part of marketing. A script loaded by the CMS may fire before the tag manager; an external domain may not receive the preference; and a server-side tag may continue processing an event blocked in the browser. Record what the team controls, what depends on a third party, and which risks remain. If a user's choice cannot be honored on a route, fix or remove the integration.
- Test refusal, partial acceptance, change and return.
- Check direct tags, container, network and server-side integrations.
- Compare interface language with observed behavior.
- Correct or suspend paths that do not respect the choice.
Governance makes measurement sustainable
Consent must be part of the change-management cycle. Every new campaign, tool, page, or partner can change the purposes, data collected, and destinations. Include a review before publication, a test after change and an updated inventory. Define who can request, approve, implement and audit the change. Company-controlled access, logs, and a rollback plan help prevent sales urgency from undoing established safeguards. The technical configuration needs to reflect this documented decision, without expanding the collection because a platform offers an additional resource or a more convenient report.
When the choice prevents a certain signal, the report should show the absence without silently estimating what was not observed. The team can analyze aggregate trends using the available data as long as it clearly describes the limitations. Retain configuration evidence for the period defined by the approved governance policy and review the design with legal guidance. The commitment is to measure what is necessary, explain the process and respect the person, not pursue artificial coverage. Validation should include third-party code outside the tag manager because its container does not control everything loaded on the page or through external services.
- Include consent review in the workflow for new campaigns.
- Maintain the inventory, logs, accountable owners, and rollback plan.
- State in the report when a missing signal results from the user's choice.
- Consult official ANPD guidance and obtain legal review for the specific case.
Reference sources
- ANPD — Guides and Guidelines — accessed on 6 September 2026.
- Google Tag Manager — consent mode — accessed on 6 September 2026.
- Google Analytics — consent and privacy — accessed on 6 September 2026.