- Home
- Skills
- Marketing & SEO
- Analytics Tag Privacy Check
More screenshots
Works with the AI Agents you already use
Analytics Tag Privacy Check
gtag('event', 'sign_up', { email: user.email }) puts your customers' email addresses into Google Analytics, which Google's policies forbid.
$5
Analytics Tag Privacy Check
Example session with this skill installed
Check this project with analytics-tag-privacy-check.
- Read your context and instructions
- Compiled the analytics tag privacy
$ python3 scripts/check_analytics.py examples/risky
BLOCK shop/gtm/GTM-NOTREAL_workspace.json:21 T01 PII_SENT_TO_GOOGLE_ANALYTICS
{"type": "TEMPLATE", "key": "parameterValue", "value": "{{DLV - user email}}"}
Why: An email address, phone number, person's name, street address, birth date or ID number is sent to Google Analytics: in gtag event, config or set parameters (user_id, user_properties, page_location), a Firebase Analytics call, or a GA4 tag in a Tag Manager export. Google's Analytics policies forbid sending data that identifies a person, and the values end up in reports that everyone with access to the property can read.
Safer: Send an internal, non-personal ID (user.id) as user_id, keep personal data out of event parameters and page URLs, and pass contact details only through gtag('set', 'user_data', ...) for Google's user-provided data features, with consent.
BLOCK shop/public/index.html:13 T03 CONSENT_SET_AFTER_TAGS_FIRE
BLOCK shop/public/index.html:31 T01 PII_SENT_TO_GOOGLE_ANALYTICS
BLOCK shop/server/capi.py:5 T02 ANALYTICS_SECRET_EXPOSED
BLOCK shop/src/tracking.js:15 T02 ANALYTICS_SECRET_EXPOSED
REVIEW landing/index.html:7 T11 NO_CONSENT_DEFAULT
REVIEW landing/index.html:13 T14 UNIVERSAL_ANALYTICS_LEFTOVER
REVIEW shop/gtm/GTM-NOTREAL_workspace.json:30 T14 UNIVERSAL_ANALYTICS_LEFTOVER
REVIEW shop/public/index.html:12 T14 UNIVERSAL_ANALYTICS_LEFTOVER
REVIEW shop/public/index.html:13 T12 CONSENT_MODE_V2_FIELDS_MISSING
REVIEW shop/public/index.html:13 T13 CONSENT_DEFAULT_GRANTED_EVERYWHERE
REVIEW shop/public/index.html:20 T15 GA4_CONFIG_DUPLICATED
REVIEW shop/public/index.html:25 T16 SESSION_RECORDING_UNMASKED
REVIEW shop/src/tracking.js:3 T16 SESSION_RECORDING_UNMASKED
REVIEW shop/src/tracking.js:8 T17 PII_IN_EVENT_DATA
REVIEW shop/src/tracking.js:9 T17 PII_IN_EVENT_DATA
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with analytics tag content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
gtag('event', 'sign_up', { email: user.email }) puts your customers' email addresses into Google Analytics, which Google's policies forbid. A gtag('consent', 'default', ...) placed one line below gtag('config') does nothing for the first page view, and an api_secret in a sendBeacon call lets anyone send fake events into your reports. This skill finds those and seven other tracking privacy mistakes before release, and tells you how to fix each one.
Your agent runs a scanner on your pages and templates (HTML, Liquid, PHP, ERB, Nunjucks, Handlebars, Twig, Jinja, Vue, Svelte, Astro), JavaScript and TypeScript, server code that calls analytics APIs (Python, Ruby, Go) and Google Tag Manager container exports. It reads the Google tag (gtag.js), Tag Manager snippets and exports, Firebase Analytics, Meta Pixel, TikTok pixel, Segment, RudderStack, PostHog, Mixpanel, Amplitude and session recorders (Sentry Replay, LogRocket, rrweb, Hotjar, Clarity, FullStory). It reads scripts inside pages and inside Next.js Script template strings, follows template values such as {{ customer.email }}, knows the official channels for contact details (gtag user_data, Meta advanced matching, ttq.identify, identify calls) and hashed or redacted values, so it does not report them, and orders consent the way browsers run scripts (scripts held back until consent, module and Partytown scripts, Next.js Script strategies). It never runs your code or loads the tags. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach, and every rule links the official documentation behind it. Secrets are never printed. It is a technical check, not legal advice.
What it checks
BLOCK
- T01: emails, phone numbers, names, street addresses, birth dates or ID numbers sent to Google Analytics (gtag and sendGAEvent events, config, user_id, user properties, Firebase Analytics, GA4 tags in Tag Manager exports)
- T02: server-only analytics credentials in code or in browser scripts (Measurement Protocol api_secret, Meta Conversions API and TikTok Events API tokens, PostHog personal keys, Mixpanel and Amplitude secrets); browser tokens of other services such as Mapbox are not reported
- T03: consent defaults set after tags fire (gtag consent default after config, event or the Tag Manager snippet; fbq consent revoke after init or track)
REVIEW
- T11: the Google tag loaded with no consent default, consent banner or consent check in the project
- T12: consent defaults without the Consent Mode v2 fields ad_user_data and ad_personalization (Google infers only ad_user_data for EEA visitors)
- T13: consent granted to every visitor by default, with no regional default
- T14: Universal Analytics leftovers (UA- IDs, analytics.js, UA tags in Tag Manager exports, anonymize_ip)
- T15: the same GA4 measurement ID configured twice in one file
- T16: session recordings that capture typed input (masking turned off, LogRocket or rrweb defaults, data-hj-allow, fs-unmask, data-clarity-unmask on the page or a form)
- T17: personal data in dataLayer pushes, Meta and TikTok pixel events, and Segment, RudderStack, PostHog, Mixpanel or Amplitude event properties
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official documentation link for each rule
- A risky and a safe example project (a shop and a landing page), and the real report the scanner produces on the risky one
Limits It reads each file as written: values built at run time or in other files, tags set up only in the Tag Manager or vendor web interface, Tag Manager consent settings, server-side (sGTM) containers and mobile app SDKs are not checked. Whether consent is legally required depends on your visitors and your legal basis; this is not legal advice. NOT FLAGGED is not a guarantee.
Static check of tracking code text. Tags configured only in the Tag Manager or vendor web interface and what page URLs contain at run time are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert IDs and one fake token (not-a-real-...) for the scanner to find. It is never run.