PostHog connector: datasets and metric definitionsBeta
Bring in PostHog traffic, signups, activation, retention and feature usage by day, channel and page. Updates daily.
When you connect PostHog, Quiriz imports the datasets below and adds the metric definitions to Company Context, the one place your company’s definitions live. Every answer that uses one of these metrics uses the same definition, in the app, in Slack and in the Excel, Sheets, PowerPoint, Slides, Word and Docs add-ins. An admin can edit any of them.
DatasetsMetric definitionsWorks withQuestionsFAQ
Datasets
| Dataset | What it holds |
|---|---|
| [PostHog] Traffic by day | Sessions, page views and bounces per day, channel, referring domain and UTM values, in the project time zone; the same numbers as PostHog Web analytics. Signups, activations and paid conversions count the events chosen in Connectors > PostHog > Events, in the sessions of each row; until a signup event is chosen the signups column is 0. Referring domains and UTM values keep the top 100 per month and the rest are "(other)". Unique visitors are not here because they cannot be added across days: see [PostHog] Active users.19 columnsdate, channel_type, referring_domain, utm_source, utm_medium, utm_campaign, sessions, pageviews, bounces, session_seconds, signups, activations, paid_conversions, key_event_1, key_event_2, key_event_3, key_event_4, key_event_5, project_name |
| [PostHog] Pages by month | Page views per path per month, plus the sessions (and bounces) that entered on that path and how many of them signed up. Top 5,000 paths per month by page views; the rest are left out, so totals are less than [PostHog] Traffic by day.7 columnsmonth, pathname, pageviews, entry_sessions, entry_bounces, entry_signups, project_name |
| [PostHog] Audience by month | Sessions, page views and signups per month by country (ISO code) and device type, read from the events themselves.7 columnsmonth, country, device_type, sessions, pageviews, signups, project_name |
| [PostHog] Active users | Distinct people active in each period: one row per day, week or month. Filter on is_day, is_week or is_month and never add periods together, because a returning person counts once in each. Only complete weeks and months are here; day rows cover the last 90 days. If the project uses cookieless tracking, user counts are approximate and weekly or monthly counts overstate.7 columnsperiod_start, is_day, is_week, is_month, active_users, new_users, project_name |
| [PostHog] Signup cohorts | One row per signup week and first-touch channel; counts add across rows because each person is in exactly one row. retained_wN is blank until N full weeks have passed after the signup week, so filter weeks_observed >= N before dividing. Without a signup event chosen in Connectors > PostHog > Events, the cohort is the week a person was first seen. If the project uses cookieless tracking, counts are approximate.13 columnscohort_week, first_channel, signups, activated_7d, activated, paid, weeks_observed, retained_w1, retained_w2, retained_w4, retained_w8, retained_w12, project_name |
| [PostHog] Events by day | Events per day: custom events plus page views, screens, autocaptured clicks and exceptions. Top 200 events per day.4 columnsdate, event, events, project_name |
| [PostHog] Event users by month | People and events per calendar month for each event. Do not add months together: a returning person counts once in each month. Top 200 events per month.5 columnsmonth, event, people, events, project_name |
Metric definitions
Each metric is a total over the period you ask about. A metric built from other metrics, such as a rate, divides the totals for the whole period; it does not average daily rates. Dated by is the date column that decides which period a row belongs to.
[PostHog] Traffic by day
| Metric | How it is calculated | Dated by | Notes |
|---|---|---|---|
| PostHog sessions | Sum of sessions | date | Sessions, by day and channel. Matches PostHog Web analytics. |
| PostHog page views | Sum of pageviews | date | Page views, by day and channel. |
| PostHog bounces | Sum of bounces | date | Sessions with one page view, no clicks and under the bounce time set in PostHog. |
| PostHog session seconds | Sum of session_seconds | date | Total session time in seconds; divide by sessions for the average. |
| PostHog signups | Sum of signups | date | Signup events (the event chosen in Connectors > PostHog > Events) in the sessions of each row. 0 until a signup event is chosen. |
| PostHog bounce rate | PostHog bounces ÷ PostHog sessions | date | Bounced sessions per session, as a decimal (0.4 = 40%). |
| PostHog average session duration | PostHog session seconds ÷ PostHog sessions | date | Average session length in seconds. |
| PostHog signup rate | PostHog signups ÷ PostHog sessions | date | Signup events per session, as a decimal. |
[PostHog] Signup cohorts
| Metric | How it is calculated | Dated by | Notes |
|---|---|---|---|
| PostHog cohort signups | Sum of signups | cohort_week | People whose first signup was in that week. Each person is counted once, so weeks add up. |
| PostHog activated within 7 days | Sum of activated_7d, where weeks_observed >= 1 | cohort_week | Cohort members who did the activation event within 7 days of signing up. Only cohorts at least one full week old. |
| PostHog cohort signups observed 1 week | Sum of signups, where weeks_observed >= 1 | cohort_week | Cohort signups, only cohorts at least one full week old. |
| PostHog retained week 1 | Sum of retained_w1, where weeks_observed >= 1 | cohort_week | Cohort members active in the first full week after their signup week. Only cohorts old enough. |
| PostHog retained week 4 | Sum of retained_w4, where weeks_observed >= 4 | cohort_week | Cohort members active in the fourth full week after their signup week. Only cohorts old enough. |
| PostHog cohort signups observed 4 weeks | Sum of signups, where weeks_observed >= 4 | cohort_week | Cohort signups, only cohorts at least four full weeks old. |
| PostHog paid signups | Sum of paid | cohort_week | Cohort members who ever did the paid event (chosen in Connectors > PostHog > Events). |
| PostHog 7 day activation rate | PostHog activated within 7 days ÷ PostHog cohort signups observed 1 week | cohort_week | Share of signups who activated within 7 days, as a decimal. Cohorts at least one full week old. |
| PostHog week 1 retention | PostHog retained week 1 ÷ PostHog cohort signups observed 1 week | cohort_week | Share of signups active in week 1 after signup, as a decimal. |
| PostHog week 4 retention | PostHog retained week 4 ÷ PostHog cohort signups observed 4 weeks | cohort_week | Share of signups active in week 4 after signup, as a decimal. |
| PostHog paid conversion rate | PostHog paid signups ÷ PostHog cohort signups | cohort_week | Share of signups who did the paid event, as a decimal. |
Works with other connectors
- PostHog + Stripe: Signups to revenue. PostHog signups and activation next to what Stripe collected. Read the guide.
Questions to ask
- How many sessions and page views did we get this week compared with last week?
- Did our launch bring signups or just visits? Show sessions and signups by referring domain by day.
- Which channel brings the most signups, and which channel converts best?
- What percent of last month's signups activated within 7 days?
- What is our week 4 retention for each signup week?
- Which pages bring visitors who sign up?
Related guides
- PostHog AI: Ask Your Product Data Questions in Plain English
- PostHog Dashboard: Six Tiles Worth Having, Beyond the Built-in Insights
- From PostHog Signups to Stripe Revenue: What You Can and Cannot Connect
Ask PostHog in plain words
Try the questions on sample data with no signup, then connect PostHog read-only and ask your own.
Try Quiriz free →Frequently asked questions
Does Quiriz change anything in PostHog?
How often does the PostHog data refresh?
Can I change how a metric is calculated?
Can I combine PostHog with other sources?
All connectors: Quiriz connectors. Definitions on this page are generated from the product’s own connector code.