Analytics Tracking Pro

Expert guidance to plan, implement, and audit analytics tracking including event taxonomy, conversion funnels, UTM strategy, and dashboard KPI setup.

Security Scan

Instruction-only analytics guidance that is internally consistent with its stated purpose and requests no credentials or installs.

Purpose & Capability

The name, description, and SKILL.md all describe planning, implementing, and auditing analytics tracking; there are no unrelated requirements (no env vars, binaries, or installs) that conflict with the stated purpose.

Instruction Scope

Runtime instructions are limited to design and testing guidance, taxonomy, UTM strategy, funnels, and KPI templates. The SKILL.md does not instruct the agent to read local files, access secrets, call external endpoints, or perform system-level actions outside the analytics domain.

Install Mechanism

No install spec or code files are present; this is an instruction-only skill, which minimizes on-disk execution risk.

Credentials

The skill requests no environment variables, credentials, or config paths. This is proportionate for an advisory/tracking-plan skill.

Persistence & Privilege

always is false and the skill is user-invocable; autonomous invocation is allowed (platform default) but not combined with elevated privileges or credential access.

Assessment

This skill only provides written guidance and templates — it does not install software or ask for credentials. Before acting on any implementation suggestions: (1) do not paste production credentials, API keys, or full user data into the chat; (2) review any generated tracking code or GTM configurations for PII and privacy compliance before deploying; (3) ensure consent mechanisms are implemented for EU users as the skill recommends; and (4) if you want the agent to perform account-level changes (e.g., in GA4 or GTM), be cautious about providing access and prefer manual implementation or scoped service accounts. The skill appears coherent and low-risk, but always validate outputs before applying them in production.

Analytics Tracking Skill

Trigger

When the user wants to set up, improve, or audit analytics tracking and measurement.

Trigger phrases: "set up tracking", "GA4", "Google Analytics", "conversion tracking", "event tracking", "UTM parameters", "tag manager", "GTM", "analytics implementation", "tracking plan"

Process

1. Understand: Product type, key conversion actions, current setup
2. Design: Event taxonomy, conversion funnels, UTM strategy
3. Implement: Tracking code, GTM configuration, custom events
4. Verify: Testing plan to confirm data accuracy
5. Dashboard: KPI definitions and reporting structure

Output: Tracking Plan

# Tracking Plan — [Product]

## Key Conversions
| Event | Trigger | Parameters | Priority |
|-------|---------|------------|----------|
| sign_up | Form submission | method, source | P0 |
| purchase | Checkout complete | value, currency, items | P0 |
...

## Event Taxonomy
### Naming Convention
- Format: `[object]_[action]` (e.g., `button_click`, `form_submit`)
- Always lowercase, underscore separated
- Include: event name, category, label, value

### User Properties
| Property | Type | Description |
|----------|------|-------------|
| user_type | string | free / pro / enterprise |
| signup_date | date | Account creation date |
...

## UTM Strategy
| Campaign Type | Source | Medium | Campaign |
|--------------|--------|--------|----------|
| Newsletter | newsletter | email | [YYYY-MM-topic] |
| Social organic | twitter/linkedin | social | [topic] |
| Paid ads | google/meta | cpc | [campaign-name] |
...

## Conversion Funnels
### Primary: Visitor → Signup → Activation → Purchase
1. page_view (landing page)
2. cta_click (signup button)
3. sign_up (form submitted)
4. onboarding_start
5. key_action_complete (activation event)
6. purchase

## Dashboard KPIs
| KPI | Definition | Target |
|-----|-----------|--------|
| Conversion rate | signups / visitors | >3% |
...

Rules

• Always define events before implementing — plan first
• Use consistent naming conventions across all events
• Test every event in debug mode before going live
• Document everything — future you will thank present you
• GDPR: always include consent mechanism before tracking EU users