For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
      • Components of a metric
      • Choosing a metric type
        • Page viewed conversion metrics
        • Clicked or tapped conversion metrics
        • Custom metrics
      • Creating metrics from traces
      • Managing metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Related content
Metrics and eventsCreating metrics

Choosing a metric type

Was this page helpful?
Previous

Page viewed conversion metrics

Next
Built with

Overview

The topics in this category help you understand the different types of LaunchDarkly metric so you can choose the correct metric for an experiment or guarded rollout.

You can use any of the metric event types to create conversion metrics, which aggregate and analyze events when an end user takes an action based on a feature flag they encounter. You must use custom events to create numeric metrics, which measure and analyze numerical values against a baseline that you set.

You can use any metric types to create an A/B experiment or A/A test, or to use as a release guardrail in a guarded rollout or release policy. You can add certain conversion metrics to a funnel metric group for use in experiments, guarded rollouts, or release policies.

This table includes examples of different different metric types and their common analysis units, and shows which metrics can be used experiments, funnel metric groups, and guarded rollouts:

Metric typeExample measurementExample uses
Page viewed conversion

How many times do end users view a blog post?

Example analysis unit: user

A/B experiment
Funnel metric group
Guarded rollout

Clicked or tapped conversion

How often do customers click a “Save” button?
How many times do customers click on a link?
When is the best point during a process to display a sign-up invitation?

Example analysis unit: user

A/B experiment
Funnel metric group
Guarded rollout

Custom conversion count

How many purchases did a customer make?
How many times per quarter do customers contact Support?

Example analysis unit: user or organization

A/B experiment
Guarded rollout

Custom conversion binary

Do customer searches call a particular service?
Do customer payments succeed?
Do customers contact customer service within a set period of time?
Do customers renew their contract within 30 days?
Does this process generate an error?

Example analysis unit: user or organization

A/B experiment
Funnel metric group
Guarded rollout

Custom numeric

How much do customers spend per transaction in my store?
How much do customers spend in total?
How many items do customers purchase per transaction?
How many items do customers purchase total?
How much time do customers spend on a page?
How long does it take for a server to respond to a request?
How long until the time to first byte (TTFB)?

Example analysis unit: user, guest, or request

A/B experiment
Guarded rollout

You should choose a metric type that correctly measures the effect of a change on your customers or codebase. If you are unsure of what metric type to use, begin by determining what kind event you are trying to measure. For additional examples of common metrics and how to configure them, read Example metrics.

When you create a metric, you must also decide how you want to handle its metric and unit analysis. To learn more, read Metric aggregation and analysis.

Related content

The following sections describe how to create each metric type:

  • Page viewed conversion metrics
  • Clicked or tapped conversion metrics
  • Custom conversion count metrics
  • Custom conversion binary metrics
  • Custom numeric metrics