Help us improve
Share bugs, ideas, or general feedback.
From vanguard-frontier-agentic
Reviews whether GPC opt-out signals actually suppress ad tags, server-side forwarding, and conversion APIs through the tag stack and CMP. Catches cosmetic compliance and pre-first-visit gaps.
npx claudepluginhub raishin/vanguard-frontier-agentic --plugin vanguard-frontier-agenticHow this skill is triggered — by the user, by Claude, or both
Slash command
/vanguard-frontier-agentic:marketing-gpc-signal-honoring-reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill reviews the technical signal path by which a Global Privacy Control (GPC) opt-out travels from the browser header through the consent management platform (CMP) and tag manager to determine whether ad tags, server-side conversion forwarding, and conversion API calls actually cease firing. GPC is a legally recognized opt-out signal under CPRA (Cal. Civ. Code §1798.135) and the Californ...
Reviews marketing site consent and data-collection posture — CMP banners, tag-manager containers, Google Consent Mode, cookie policies — for GDPR/CCPA/ePrivacy compliance and dark patterns.
Integrates Global Privacy Control (GPC) signals with cookie consent platforms by detecting HTTP headers and JavaScript API, triggering opt-outs, and ensuring CCPA, CPA, CTDPA compliance.
Implements CPRA Section 1798.135 opt-out preference signals like GPC: detects HTTP/JS browser signals, automates honoring, ensures cross-device consistency, resolves signal-choice conflicts.
Share bugs, ideas, or general feedback.
This skill reviews the technical signal path by which a Global Privacy Control (GPC) opt-out travels from the browser header through the consent management platform (CMP) and tag manager to determine whether ad tags, server-side conversion forwarding, and conversion API calls actually cease firing. GPC is a legally recognized opt-out signal under CPRA (Cal. Civ. Code §1798.135) and the California CPPA enforcement sweeps of September 2025 confirmed that acknowledging GPC in the CMP UI while failing to suppress downstream tag execution constitutes a violation. The review distinguishes between cosmetic compliance (the CMP reads the GPC header and sets a cookie) and substantive compliance (the GPC state variable gates every ad tag firing rule and every server-side forwarding path). It also catches the pre-first-visit gap: users who set GPC before arriving for the first time receive no opt-out cookie and are therefore not suppressed. Artifact inputs: tag-manager container export and CMP opt-out configuration, annotated with which firing rules reference the GPC/opt-out variable.
Load these only when needed:
Return, at minimum: