Skip to main content

​
Overview

Features are the foundational units of monetization in Metrifox. They represent monetizable functionality, resource or value in your product, enabling flexible pricing, packaging, and usage tracking. Once you integrate Metrifox with your codebase, you can create and monetize unlimited features, without additional engineering work. This lets you experiment with pricing, packaging, and easily track its usage, control who has access to it, and include it in different pricing plans, add-ons or single purchases entirely from the Metrifox dashboard. Think of features as the core components you use to build your pricing models. Instead of just creating a plan for “premium,” you can break down your product into individual features like:
  • Boolean features: A simple on/off function, such as “access to analytics dashboard.”
  • Metered features: A function that is tracked by usage or outcome, such as “500 API calls per month”, “monthly active users” or “qualified lead”

​
Creating a feature

  1. Navigate to the Catalog section in Metrifox.
  2. Open the Features sub-section.
  3. Click the “Create a Feature” button.

​
Feature details

Fill out the following fields in the modal:
FieldDescriptionNotes
NameA clear, descriptive name for the feature (e.g., “API Calls per Month”).Use customer-friendly naming for internal clarity.
Description (Optional)Additional context about the feature’s purpose or usage.Helpful for cross-team alignment (e.g., finance, product).
KeyA unique identifier auto-generated by Metrifox. You can override this.Used to reference the feature in your application code (e.g., api_calls_monthly).
Feature TypeDefines how the feature is tracked and billed.Options:
- Boolean: On/off access (e.g., “Premium Support”).
- Meter: Usage, outcome, (e.g., “API Calls”).

​
Metered Features

1

Select Feature Type

  • Choose “Meter” as the feature type when creating a new feature.
2

Configure Metering

Metered features require the following settings:1. Usage Type (Required)Defines how usage is recorded and reset:
  • PER USE
    • Discrete, event-based actions (e.g., API calls, emails sent).
    • Usage resets at the end of each reset period.
  • PERSISTENT USE
    • Ongoing usage that accumulates (e.g., storage, seats).
    • Does not reset; capacity limits can be adjusted.
2. Event Name (Required)
  • A unique label to send usage data or outcome event for metering e.g., image_generated, api_request.
3. Aggregation Metric (Required)How raw events are calculated for billing:
MetricUse CaseExample
SUMTotal usage (e.g., bytes stored).SUM(storage_bytes)
COUNTNumber of events (e.g., API calls).COUNT(api_requests)
COUNT_UNIQUEUnique instances (e.g., users).COUNT_UNIQUE(user_id)
MIN/MAXPeak/floor values (e.g., temperature).MAX(concurrent_connections)
LATESTLast recorded value.LATEST(account_balance)
AVERAGEMean value over time.AVERAGE(cpu_usage)
4. Custom Dimensions (Optional)Key-value pairs for granular filtering (e.g., region: us-east, model_type: gpt-4).
3

Define Units

  • Singular/Plural Labels:
    • Used in invoices/dashboards (e.g., “1 GB” vs. “10 GBs”).
    • Examples:byte (singular) → bytes (plural).
4

Add Metadata (Optional)

  • Flexible key-value pairs for internal logic (e.g., tier: premium, product: ai).
5

Complete Creation

  • Click “Create a Feature” to finalize. Example Configuration
    FieldValue
    Usage TypePER USE
    Event Nameapi_call_executed
    AggregationCOUNT
    Unitscall (singular), calls (plural)

​
Managing Features

​
Editing Feature Details

  1. Locate the Feature
    • Navigate to the feature list in the Catalog section
    • Select the row of the feature you want to modify
  2. Update Fields
    • Edit any editable fields (name, description, units, etc.)
    • Note: Certain properties like the Feature Key cannot be modified after creation or if the feature is in use.
  3. Save Changes
    • Click ”Save changes” to apply your updates.
  • Cannot modify the Feature Key, Feature Type, Event Name and Agreggation Type once created
  • Changes propagate to all existing plans and add-ons using the feature

​
Archiving Features

When a feature is no longer needed for new customers but may still remain active for existing ones:

​
What Happens When You Archive a Feature?

  • Removed from selection lists: Won’t appear when creating new plans/add-ons.
  • Existing access preserved: Current customers keep access through old plan or add-ons versions
  • Usage analytics disabled: No longer available in the analytics dashboard
  • Feature key remains reserved: Cannot be reused for new features

​
How to Archive a Feature

  1. Click the ⋮ menu icon on the feature’s row
  2. Select “Archive”
  3. In the confirmation modal:
    • Click “Archive feature”

​
Prerequisites for Archiving

  • The feature must not be used in any published plans or add-ons
  • If in use:
    1. Create new versions of affected plans/add-ons without the feature
    2. Publish the new versions
    3. Then archive the feature