---
description: Test whether consent choices really control what tags, pixels and cookies send
argument-hint: [site, region or consent issue]
---

Use the consent-debugging skill for this task: $ARGUMENTS

Read martech-context/ first if it exists, especially stack.md, decisions.md and the tracking plan.
If $ARGUMENTS is empty or vague, ask for the site and journeys, the regions in scope, the approved consent spec and read access to GTM and the CMP.
Write the expected behaviour for each region and choice before testing anything.
Follow the skill's procedure in order and check the result against its acceptance checks.
Stay read-only. Stop for written approval before any test conversion or any change to GTM, the CMP, the site or a vendor account.
Hand back the filled test matrix, the evidence per case, the pass or fail write-up with graded findings and a change list for the owner.

If the consent-debugging skill is not installed, install it with: npx skills add https://www.martechdevs.com --skill consent-debugging -a claude-code
