Home / Connectors / PostHog
Connector

PostHog connector: datasets and metric definitionsBeta

Bring in PostHog traffic, signups, activation, retention and feature usage by day, channel and page. Updates daily.

7 datasets19 metric definitionsRead-onlyRefreshes 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

DatasetWhat it holds
[PostHog] Traffic by daySessions, 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 monthPage 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 monthSessions, 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 usersDistinct 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 cohortsOne 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 dayEvents 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 monthPeople 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

MetricHow it is calculatedDated byNotes
PostHog sessionsSum of sessionsdateSessions, by day and channel. Matches PostHog Web analytics.
PostHog page viewsSum of pageviewsdatePage views, by day and channel.
PostHog bouncesSum of bouncesdateSessions with one page view, no clicks and under the bounce time set in PostHog.
PostHog session secondsSum of session_secondsdateTotal session time in seconds; divide by sessions for the average.
PostHog signupsSum of signupsdateSignup events (the event chosen in Connectors > PostHog > Events) in the sessions of each row. 0 until a signup event is chosen.
PostHog bounce ratePostHog bounces ÷ PostHog sessionsdateBounced sessions per session, as a decimal (0.4 = 40%).
PostHog average session durationPostHog session seconds ÷ PostHog sessionsdateAverage session length in seconds.
PostHog signup ratePostHog signups ÷ PostHog sessionsdateSignup events per session, as a decimal.

[PostHog] Signup cohorts

MetricHow it is calculatedDated byNotes
PostHog cohort signupsSum of signupscohort_weekPeople whose first signup was in that week. Each person is counted once, so weeks add up.
PostHog activated within 7 daysSum of activated_7d, where weeks_observed >= 1cohort_weekCohort 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 weekSum of signups, where weeks_observed >= 1cohort_weekCohort signups, only cohorts at least one full week old.
PostHog retained week 1Sum of retained_w1, where weeks_observed >= 1cohort_weekCohort members active in the first full week after their signup week. Only cohorts old enough.
PostHog retained week 4Sum of retained_w4, where weeks_observed >= 4cohort_weekCohort members active in the fourth full week after their signup week. Only cohorts old enough.
PostHog cohort signups observed 4 weeksSum of signups, where weeks_observed >= 4cohort_weekCohort signups, only cohorts at least four full weeks old.
PostHog paid signupsSum of paidcohort_weekCohort members who ever did the paid event (chosen in Connectors > PostHog > Events).
PostHog 7 day activation ratePostHog activated within 7 days ÷ PostHog cohort signups observed 1 weekcohort_weekShare of signups who activated within 7 days, as a decimal. Cohorts at least one full week old.
PostHog week 1 retentionPostHog retained week 1 ÷ PostHog cohort signups observed 1 weekcohort_weekShare of signups active in week 1 after signup, as a decimal.
PostHog week 4 retentionPostHog retained week 4 ÷ PostHog cohort signups observed 4 weekscohort_weekShare of signups active in week 4 after signup, as a decimal.
PostHog paid conversion ratePostHog paid signups ÷ PostHog cohort signupscohort_weekShare of signups who did the paid event, as a decimal.

Works with other connectors

Questions to ask

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?
No. The PostHog connector is read-only. Quiriz reads the data into datasets and never writes back to PostHog.
How often does the PostHog data refresh?
Once a day. Each dataset shows when it was last updated, and answers use the latest refresh.
Can I change how a metric is calculated?
Yes. The definitions are added to Company Context, where an admin can edit the formula, the filter or the date it uses. A daily refresh never overwrites a definition someone has changed.
Can I combine PostHog with other sources?
Yes. An admin can also define a metric from metrics on different datasets. See cross-source metrics.

All connectors: Quiriz connectors. Definitions on this page are generated from the product’s own connector code.