> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Feature Flag Rollout Status, PostHog

> Feature Flag Rollout Status for PostHog stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Feature Flag Rollout Status** is a feature-flags table tracked from PostHog data. It lists each active flag with its current rollout percentage, so you can see at a glance which flags are at 100%, which are mid-rollout, and which are stuck partway. This is a PostHog-distinctive view: it turns the flag estate into a board you can govern, catching flags that were meant to ramp gradually but quietly sit at a fixed percentage forever.

|                       |                                                                                                                                                                             |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | Each active feature flag and its current rollout percentage.                                                                                                                |
| **Sample type**       | Backend API data from PostHog feature-flag definitions, refreshed on the standard data refresh.                                                                             |
| **Why it matters**    | Flags stuck mid-rollout, or fully on when they should be gradual, change who sees what on your storefront. This table makes the whole rollout posture visible in one place. |
| **Reading the value** | Scan for flags far from 0% or 100%. A flag parked at, say, 50% for weeks usually means a rollout was forgotten.                                                             |
| **Currency**          | percent                                                                                                                                                                     |
| **Time window**       | `RT`                                                                                                                                                                        |
| **Alert trigger**     | `-`                                                                                                                                                                         |
| **Sentiment key**     | `ph_feature_flag_rollout`                                                                                                                                                   |
| **Roles**             | owner, marketing                                                                                                                                                            |

## Calculation

Calculated automatically from your PostHog data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

*A representative reading of **Feature Flag Rollout Status** for a typical merchant on PostHog.* Suppose the table shows `new-checkout` at 25%, `pdp-redesign` at 100%, and `free-shipping-banner` at 10%. The `new-checkout` flag was meant to ramp to 100% over two weeks but has sat at 25% since 04 Apr 26, which means three quarters of shoppers never saw the new flow. The table surfaces that stall instantly. Cross-reference Stale Feature Flags to find the ones at 100% that can now be retired. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

## Sibling cards merchants should reference together

| Card                                                                                            | Why merchants reach for it                         |
| ----------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| [`ph_active_feature_flags`](/nerve-centre/kpi-cards/posthog/active-feature-flags)               | Feature Flags sibling: how many flags are live.    |
| [`ph_stale_feature_flags`](/nerve-centre/kpi-cards/posthog/stale-feature-flags-90d-100-rollout) | Feature Flags sibling: flags ready to retire.      |
| [`ph_funnel_conversion`](/nerve-centre/kpi-cards/posthog/primary-funnel-conversion)             | Funnels sibling: did a rollout move conversion.    |
| [`ph_dau`](/nerve-centre/kpi-cards/posthog/daily-active-users)                                  | Executive sibling: the audience a rollout reaches. |
| [`ph_health_score`](/nerve-centre/kpi-cards/posthog/posthog-tracking-health-score)              | Executive sibling: overall tracking health.        |

## Reconciling against the vendor's own dashboard

**Where to look in PostHog's own dashboard:**

Open the Feature Flags list in PostHog. Each flag shows its release condition and rollout percentage. The percentages there should match this table. Note that a flag can target by percentage of users or by property cohort, and a cohort-targeted flag shows differently from a simple percentage rollout.

**Why the Vortex IQ value may legitimately differ:**

| Reason                                                                                             | Direction | What to do                                |
| -------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------- |
| **Cohort targeting.** A flag released to a cohort, not a percentage, has no single rollout number. | Variable  | Inspect the release condition in PostHog. |
| **Multivariate flags.** Flags with multiple variants split the percentage across variants.         | Variable  | Check the variant distribution.           |
| **Recent edit.** A rollout changed minutes ago may not have refreshed.                             | Marginal  | Force a manual refresh.                   |

**Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

## Known limitations / merchant FAQs

**Q: How often does Feature Flag Rollout Status update?**
The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

**Q: A flag shows 100% but only some users see the feature. Why?**
The flag may also carry a property or cohort condition on top of the percentage, so 100% applies only within the targeted segment. Check the full release condition in PostHog.

**Q: What does a flag stuck at a partial percentage mean?**
Usually a forgotten rollout. The team ramped to a partial percentage during testing and never completed or reverted it, leaving a fraction of users on the variant indefinitely.

**Q: Can I customise the alert threshold?**
Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust to match your business baseline rather than relying on the generic default.

***

### Tracked live in Vortex IQ Nerve Centre

*Feature Flag Rollout Status* is one of hundreds of KPI pulses Vortex IQ tracks across PostHog and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.
