analytics-tracking

What This Skill Does

The analytics-tracking skill serves as a comprehensive framework and expert guide for setting up, auditing, and optimizing data measurement strategies within digital products and marketing environments. It transforms the often overwhelming task of analytics implementation into a structured process by prioritizing actionable business questions over raw data collection. This skill helps users define clear tracking plans, establish standardized naming conventions, and implement best practices across platforms like GA4, GTM, and product analytics tools. It ensures that every event tracked—from button clicks to complex conversion funnels—serves a specific business purpose, ultimately improving data quality and the reliability of your insights.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/bobdevibecoder/bobagent-analytics-tracking Ensure you have the required permissions to install skills in your OpenClaw workspace.

Use Cases

• Establishing a Tracking Plan: Create a systematic map of events before a new product launch.
• GA4 Migration & Setup: Transition from legacy tracking to GA4 while cleaning up event structures.
• Conversion Optimization: Audit current funnel events to identify where users drop off and why.
• Marketing Attribution: Standardize UTM parameter application across campaigns for better channel reporting.
• Product Usage Analysis: Define core events to measure feature adoption and onboarding success.

Example Prompts

1. "I need to create a tracking plan for our new SaaS onboarding flow. Can you help me define the key events and property requirements?"
2. "We are seeing high traffic but low signups. Can you help me audit our current GTM tags to ensure our conversion tracking is firing correctly?"
3. "What is the best way to name our button events across our marketing site to ensure we have consistent data in Google Analytics?"

Tips & Limitations

• Tip: Always start with the business questions. If you cannot explain why you need an event, do not track it. This prevents 'data bloat' and keeps your dashboard clean.
• Tip: Use consistent naming conventions, such as the Object-Action format (e.g., 'signup_completed'), to ensure your data is intuitive for other team members to read.
• Limitation: This skill provides architectural and strategic advice. It does not automatically execute code changes in your codebase or GTM container; you will need to implement the suggested tags or data layer pushes within your development environment.