Analytics
Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install openclaw-skills-analytics
Repository
Skill path: skills/ivangdavila/analytics
Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance.
Open repositoryBest for
Primary workflow: Analyze Data & AI.
Technical facets: Full Stack, Backend, DevOps, Data / AI, Security.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Analytics into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding Analytics to shared team environments
- Use Analytics for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: Analytics
description: Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance.
---
## Critical Implementation Gotchas
**Umami API timestamps**: Use milliseconds, not seconds. `Date.now()` in JS, `int(time.time() * 1000)` in Python.
**Plausible API v2**: Requires `site_id` parameter, NOT domain name. Get site_id from dashboard URL first.
**PostHog events**: Properties must be JSON serializable. Never pass DOM elements or functions.
**Rate limits**: Umami 600/hour, Plausible 600/hour, PostHog 1000/minute. Implement exponential backoff on 429.
## Environment-Specific Setup
**Development**: ALWAYS use separate project/site for local testing. Production data pollution is irreversible.
**Tracking domains**: Never hardcode. Use env vars to switch between localhost and production.
**Bot filtering**: Enable in settings. Privacy tools have weaker bot detection than Google Analytics.
## GDPR Compliance Gotchas
**EU visitors need explicit consent** even for privacy-first tools. Check IP geolocation before tracking.
**Data retention**: Set automatic deletion - Umami in Settings > Data, Plausible 30 days max, PostHog in project settings.
**Cookie-free warning**: Umami/Plausible don't use cookies but still need consent for EU visitors if collecting identifiers.
## Runtime Safety
**Verify script loads** before sending events. Check for `umami`, `plausible`, or `posthog` globals first.
**Never track PII** (email, names, IP) in custom events. Violates privacy principles.
**Batch PostHog events** via `/batch` endpoint. Umami/Plausible require individual requests.
## Authentication Patterns
**Store API keys in environment variables** only. Never hardcode.
**Umami**: Requires website ID + API key combination.
**Plausible**: Uses Bearer token authentication.
**PostHog**: Uses project-specific API key.
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### _meta.json
```json
{
"owner": "ivangdavila",
"slug": "analytics",
"displayName": "Analytics",
"latest": {
"version": "1.0.0",
"publishedAt": 1770667927313,
"commit": "https://github.com/openclaw/skills/commit/f8cb4b6dd9f3d273e479543724e7224343fae338"
},
"history": []
}
```