Configure Analytics

Configures Plausible, PostHog, and GA4 environment variables for local and Railway production.

25|7|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill configure-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Configure Analytics
Source: https://github.com/IgorGanapolsky/ThumbGate/tree/main/skills/configure-analytics
Command: npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill configure-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of configuring Plausible, PostHog, and GA4 so your analytics work consistently across local development and your Railway production deployment.

Core Features & Use Cases

  • Key gathering from dashboards: Guides you to retrieve the correct Plausible API key, PostHog API key, and GA4 Measurement ID (or decide when to skip GA4 if the property isn’t ready).
  • Environment variable setup: Ensures you write the needed values into your local .env and then mirror them into Railway production variables.
  • Verification checks: Provides simple health and instrumentation verification commands to confirm the tracking is live.

Quick Start

Tell the AI to configure Plausible, PostHog, and GA4 environment variables for both local .env and Railway production, then verify the setup using the provided health and checkout checks.

Frequently Asked Questions about Configure Analytics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Plausible, PostHog, and GA4 environment variables for Railway production?

To configure analytics keys for Railway, you must gather the correct Plausible API key, PostHog API key, and GA4 Measurement ID, write them to your local .env file, and then mirror them into Railway production variables via CLI or dashboard.

What's the best way to set up analytics instrumentation across local development and Railway?

The best way to set up analytics instrumentation is to sync environment variables across both environments by writing analytics keys to your local .env and mirroring them to Railway production, ensuring tracking works consistently during web deployment.

Why does my GA4 tracking fail after creating a new property in my web deployment?

GA4 tracking fails when the new Measurement ID is missing from your environment variables, requiring you to update your local .env and Railway production variables to apply the newly generated GA4 property keys.

Do I need to verify analytics instrumentation after rotating API keys?

Yes, after rotating any analytics API key you must update the environment variables in your local .env and Railway, then verify the tracking is live using the provided health and instrumentation verification endpoints.

Can I skip GA4 setup if the property isn't ready but still configure Plausible and PostHog?

You can skip GA4 setup if the property isn't ready, allowing you to independently configure Plausible and PostHog environment variables for your local .env and Railway production deployment.