> ## Documentation Index > Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt > Use this file to discover all available pages before exploring further. # Metrics > Configure journey metrics, connect PostHog or Stripe, manage goals and thresholds, and troubleshoot live metric behavior. Use this page when you need to create, configure, sync, or troubleshoot metrics in Custory. For the generic definition of metrics and how they relate to touchpoints, insights, opportunities, and solutions, read [Items](/items#metrics). ## What you can configure A metric can stay manual or pull live values from PostHog or Stripe. Metric setup can include: * metric type * unit * baseline * current value * target * direction * evaluation period * live data source * linked opportunities or solutions Use `Baseline`, `Target`, and `Direction` to make the decision clear. Use live sync when the current value already exists in PostHog or Stripe. ## Metric cards Metric items have dedicated cards in grid view. Each card shows: * the metric title * a chart for the recent trend * a goal line when a target is set Open grid view on the **Metrics** tab in a journey or in [Building blocks](/building-blocks) to scan metrics visually instead of reading fields row by row. `Add screenshot of metric cards in grid view here` ### Card states A metric card tells you what still needs setup: * **No source** - the metric is not connected yet. * **Waiting for first sync** - the source is configured, but the chart appears after the first sync completes. * **Broken** - the metric is unreliable, stale, disconnected, or not usable. Click a card to open the full metric record, configure the source, run sync, or review linked items. ## Create a metric 1. Open the opportunity or solution you want to measure. 2. Click **Add item** and choose **Metric**. 3. Name the metric clearly. 4. Set `Metric type`, `Unit`, `Baseline`, `Current`, `Target`, and `Direction`. 5. Open **Details** -> **Data source** if the metric should stay connected to PostHog or Stripe. 6. Save it and link it to the opportunity or solution it supports. You can also create the metric in **Building blocks** and attach it to the right journey step later. This is useful when one metric should appear across multiple journeys. ## Configure the data source Open a metric item, then go to the **Details** tab and find **Data source**. From there you can: * choose a provider * configure the measure and evaluation logic * save the source * run **Sync now** * remove the connection when the metric should go back to manual values Connected sources currently support **Count** and **%** metrics. Metric data sources use the metric's evaluation period. Available periods are daily, weekly, monthly, quarterly, and yearly. The current value uses the latest complete period, so a monthly metric shows the latest complete month instead of a partial in-progress month. ## PostHog options Use PostHog when product behavior should drive the metric. Configure: * **Measure** - event count, unique users, or event ratio for percentage metrics * **Event** - the PostHog event that represents the outcome * **Numerator** and **denominator event** - for ratio-based percentage metrics * **Ratio basis** - events or unique users * **Calculation** - total, average, median, or peak * **Period** - inherited from the metric's evaluation window ## Stripe options Use Stripe when commercial movement should drive the metric. Available Stripe measures include: * canceled subscriptions * new subscriptions * net subscription delta * payment failures * refunds * subscriber churn rate Stripe payment failure and refund event metrics support daily, weekly, and monthly periods. Use subscription metrics such as new subscriptions, canceled subscriptions, net subscription delta, or subscriber churn rate when you need quarterly or yearly evaluation. ## Multiple projects or accounts If the workspace has more than one active integration for a provider, choose the right **Project** or account before saving. If PostHog or Stripe is not connected yet, use **Connect PostHog** or **Connect Stripe** to open **Manage Integrations** for the current workspace. `Add screenshot of the metric data source panel here` ## Goals and thresholds Use these fields to make the chart readable: * `Baseline` is where the team started. * `Current` is the latest known value. * `Target` is where the team wants the metric to land. * `Direction` tells the team whether higher or lower is better. When a source is connected, treat the chart and synced value as the live current reading. Keep target and direction filled in so the team knows what counts as progress. ## Sync behavior Connected metric cards update from their saved source configuration. Use **Sync now** when you have just changed setup or want to check the latest value immediately. The displayed current value uses the latest complete evaluation period. This avoids showing a partial in-progress period as if it were final. ## Permissions Your workspace role controls whether you can create metrics, edit fields, connect data sources, or remove a source. If you can see a metric but cannot change the source, ask a workspace owner or editor to update the integration or metric configuration. ## Limitations Keep these limits in mind: * Live data sources currently align best with `Count` and `%`. * Payment-failure and refund metrics do not support quarterly or yearly evaluation periods. * Quarterly and yearly Stripe evaluation works best with subscription measures. * A connected source updates the value and chart, but the team still needs to set target and direction. * A metric with no source is still usable, but the current value must be maintained manually. ## Troubleshooting Open the metric details and configure a PostHog or Stripe source, or keep the metric manual and maintain the current value yourself. Run **Sync now** from the data source panel. If the chart still does not appear, confirm the provider, project, event, measure, and evaluation period. Check whether the source is still connected, whether the selected event or Stripe measure still exists, and whether the current period is complete. Mark the status as `Broken` until the source mapping, integration, or manual value is corrected. ## Next step Read [PostHog and Stripe](/posthog-and-stripe) for integration setup. Read [Item details and fields](/item-fields) for the broader item detail reference.