What metrics belong in a technical PLG dashboard?

A technical PLG dashboard should include Time-to-Value (TTV), activation rate by cohort, group-level retention, product qualified lead (PQL) velocity, feature adoption breadth, and expansion revenue rate — all tracked at the account level using tools like PostHog.

What is HogQL and how is it used in PLG dashboards?

HogQL is PostHog's SQL dialect for querying event data directly. In PLG dashboards, it is used to build custom metrics like TTV percentiles, multi-event activation funnels, and cohort-level retention curves that cannot be expressed through the standard PostHog UI.

Why should PLG dashboards track metrics at the account level rather than the user level?

B2B SaaS products are purchased and renewed at the account level. Tracking activation, retention, and expansion at the account or group level ensures the dashboard reflects the business unit that makes renewal decisions, not just individual user behaviour within those accounts.

What is a product qualified lead (PQL) and how should it appear on a PLG dashboard?

A PQL is a user or account that has reached a defined product usage threshold indicating readiness for a sales conversation. On a PLG dashboard, PQL velocity tracks how many accounts enter PQL status per week, which is a leading indicator of sales pipeline health.

What is the difference between a PLG dashboard and a standard SaaS metrics dashboard?

A standard SaaS metrics dashboard focuses on acquisition, MRR, and churn. A PLG dashboard is centred on product behaviour — how quickly users reach value, how deeply they adopt features, and how usage signals translate into expansion and retention outcomes.

The Technical PLG Dashboard Template: Measuring What Matters

TL;DR

Consolidate the Stack: PostHog replaces fragmented GA4, Segment, and Mixpanel pipelines, removing the "integration tax" that kills growth velocity.
Identity Resolution: Bridge the gap between individual users and B2B accounts using `posthog.group()` for account-level health and retention.
HogQL-Powered TTV: Use SQL queries to calculate the median Time-to-Value (TTV) based on behavioral milestones, not just logins.
Predictive PQLs: Define Product Qualified Leads using behavioral clusters (used 3+ core features in 48h) rather than simple activity counts.
Automation: Push high-intent behavioral data to Slack or CRM the moment a user hits the "Aha!" threshold.

1. The Death of the 'Integration Tax'

In 2026, the "modern data stack" has collapsed into "Product OS" platforms. Technical growth teams no longer tolerate the latency and fragility of syncing Segment to Amplitude to Vitally. This "Integration Tax" drains engineering resources and creates data silos where marketing knows who saw the ad, but product doesn't know if they ever reached the "Aha! Moment."

PostHog has emerged as the gold standard for PLG because it treats growth as an engineering problem. By combining web attribution, product analytics, and feature flags in one pipeline, you get a single source of truth for the entire customer journey.

PLG is not a marketing funnel. It is an engineering pipeline. If your data is fragmented, your growth is capped.

2. The 2026 PLG Metric Hierarchy

Most dashboards are too noisy. To drive action, you must prioritize the metrics that actually correlate with long-term retention. We use a three-tier hierarchy refined through our work with 50+ growth sprints.

Tier	The Metric	The Technical Spec
1. Activation	Time-to-Value (TTV)	HogQL: median time from `joined_at` to first `core_value_action`.
2. Expansion	PQL Velocity	Count of orgs hitting "Density Threshold" (e.g., 3+ active users).
3. Governance	Version Drift	% of multi-location accounts on outdated templates.

"The most powerful metric in SaaS isn't logins; it's TTSV—Time to Second Value. If a user achieves one win and then goes silent for 7 days, your activation model is incomplete."
— Jake McMahon, ProductQuant

3. Technical Foundation: Group Analytics

In B2B SaaS, the individual user doesn't churn—the **Organization** churns. Your dashboard must be built on **Group Analytics**. This allows you to aggregate behavioral data across all users in a practice or company.

Implementing the 'Identity Moat'

To bridge the anonymous-to-identified journey, you must correctly implement identity resolution. We enforce a strict standard for `posthog.identify()` and `posthog.group()` calls to ensure attribution persistency.

// Identify the User and the Org simultaneously posthog.identify('user_id_123', { email: '[email protected]', specialty: 'Dental' }); posthog.group('organization', 'org_id_456', { name: 'Northside Dental', seat_limit: 10, is_hipaa_verified: true });

4. Advanced Insights with HogQL

PostHog's SQL engine (HogQL) allows you to perform behavioral forensics that simple UI-based tools can't touch. We provide our clients with a "PQL Scorecard" built entirely in SQL.

HogQL: The 'Aha!' Correlation Query

This query identifies which actions in the first 48 hours most strongly predict 30-day retention. It allows the growth team to ignore the noise and focus on the "Retention Superpowers."

-- Calculate Median TTV in minutes for 'Activated' users
SELECT 
    median(dateDiff('minute', registration_date, first_action_date)) as median_ttv
FROM (
    SELECT 
        p.properties.joined_at as registration_date,
        min(timestamp) as first_action_date
    FROM events 
    WHERE event = 'signature_received'
    GROUP BY person_id
)
        

90% Cost Saving

By consolidating GA4, Mixpanel, and LaunchDarkly into a unified PostHog stack, we cut a Series B platform's software bill by 90% while increasing their experimentation velocity by 10x.

FAQ

How is this different from a standard GA4 dashboard?

GA4 is built for session tracking; this template is built for **Lifecycle Orchestration**. It connects the first ad click to the final enterprise expansion event in one searchable timeline. GA4 cannot track account-level (Group) health or trigger feature flags based on behavioral milestones.

Do we need a data engineer to set this up?

No. This template is designed for **Product Engineers** and **Growth PMs**. If you can write basic SQL and understand your product's "Aha! Moment," you can implement this in 2 weeks of part-time engineering.

What is 'Version Drift' health?

For multi-location SaaS (like healthcare groups), health is defined by **Standardization**. If 20% of your locations are using outdated form templates, that account is at higher risk of compliance failure and churn. We track this via Group Properties in PostHog.

Sources

About the Author

Jake McMahon is a PLG & GTM Growth Consultant who has migrated 1M+ events to PostHog and designed unified growth dashboards for Series A-C SaaS companies. He specializes in the technical instrumentation of PLG motions and HogQL-powered behavioral forensics.

Learn More Work with Jake