AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

querying-posthog-data

Explains how to query PostHog data, defaulting to typed runners for supported product analytics. Read it before you write HogQL/SQL. Also read it before you call execute-sql against PostHog. Use it to find or aggregate PostHog entities. These entities include insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, warehouse data, and persons. Use it for trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, and LLM traces. Before you calculate a governed business or telemetry measure, check system.information_schema.metrics for an approved definition. Examples include MRR, activation, billable usage, active organizations, and failure rates. Use the approved definition before you derive a measure from raw events or use a typed domain tool. It also covers HogQL differences, system table schemas, functions, query examples, and schema discovery.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--querying-posthog-data at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 65

references/taxonomy-skipped-events.md

The team taxonomy query automatically excludes events that are not useful for analytics. These are events marked as system or ignored_in_assistant in PostHog's core taxonomy definitions.

Skipped events

Event | Reason $pageleave | Confuses LLMs — use $pageview instead $autocapture | Only useful with autocapture-specific filters $$heatmap | Internal heatmap data, doesn't contribute to event counts $copy_autocapture | Clipboard capture, too niche $set | Person property setting event, not an analytics event $opt_in | Analytics opt-in event, irrelevant for product analytics $feature_flag_called | Feature flag evaluation, not a user action $feature_view | posthog-js/react specific, niche $feature_interaction | posthog-js/react specific, niche $capture_metrics | Internal SDK metrics $create_alias | Identity management event $merge_dangerously | Identity management event $groupidentify | Group identification event

These events are filtered at the SQL level using a NOT IN clause, so they don't consume pagination slots.