AGENTIC MEMORY

Skills

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

← Back to Skills

configuring-experiment-analytics

Configures the analytics side of a PostHog experiment — exposure criteria (server-resolved default exposure event vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with `retention_window_start` and `start_handling`), multivariate user handling ("Exclude from analysis" vs "Use first seen variant"), and how to read results once the experiment is live. Use when the user adds or edits a primary or secondary metric (e.g. "add a secondary metric tracking 'downloaded_file' per user"), sets up a ratio metric (e.g. "revenue from purchase_completed / pageviews"), sets up a retention metric (e.g. "$pageview → uploaded_file, 7-day window"), configures custom exposure (e.g. "only count users who hit /checkout"), changes multivariate handling, or asks "who is in the analysis?", "how do I measure impact?", "is this winning?", "what's the confidence level?", or "should I ship?".

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--configuring-experiment-analytics 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 · 4

references/metric-configuration.md · 120000

y array to detach all shared metrics.

To promote a one-off inline metric into a reusable shared metric:

  1. Call experiment-saved-metrics-create with the inline metric's query (the ExperimentMetric object) and leave out query.uuid. The API assigns the shared metric a new uuid and ignores one you send.
  2. In a single experiment-update call, attach the new metric through saved_metrics_ids as above, and resend metrics (or metrics_secondary) without the inline metric. If you leave the inline metric in place, the experiment measures the same thing twice.

Property filters

Any EventsNode can include property filters to narrow which events count. Filters never change aggregation — for that, use math / math_property.

{
  "kind": "EventsNode",
  "event": "purchase_completed",
  "properties": [
    {
      "key": "plan",
      "value": ["pro", "enterprise"],
      "operator": "exact",
      "type": "event"
    }
  ]
}