revenuecat-charts

Accessing RevenueCat charts

When querying a RevenueCat chart, follow this workflow:

1. Use get-chart-options-schema to discover a chart's available options.
2. Use get-chart-data with the right options to retrieve the chart data.
3. Analyze the data, using scripts for any non-trivial arithmetic.

Via the rc CLI (see the revenuecat-cli skill): rc charts list to list charts, rc charts options <chart> for the schema, and rc charts show <chart> for the data.

In general, to avoid clogging the context, start with defined timeframes and larger resolution, then narrow down.

1. Discover chart options with get-chart-options-schema

• Treat get-chart-options-schema as the source of truth for each chart before calling get-chart-data. It returns the chart's supported resolutions, filters, segments, and user_selectors. Always call this tool with "realtime": true. Later get-chart-data calls must use string IDs exactly as returned here.
• filters are the dimensions you may later constrain in get-chart-data.
  • Each filter has:
    • an id to later use as the filter name.
    • a value_mode that tells you how to choose valid values:
      • inline_enum means you must use the id of one of the returned options. Resolve user-supplied names first with the matching list tool, such as list-products, list-offerings, list-apps, etc.
      • inferred_standard means use the standard code from value_source such as an ISO country code.
      • dynamic means values come from observed project data and must match exactly.
  • Do not pass display names, store product identifiers, bundle IDs, or guessed values unless the schema says they are valid values.
• segments are the dimensions you may later group by in get-chart-data using segment.
  • A segment entry directly gives the dimension id to use. It does not list segment values because the chart will group by it and show all values in the output.
  • Filters and segments are separate per-chart lists, so never assume a filterable dimension is segmentable. For example, conversion_to_paying may support product_id and offering_identifier as filters but not as segments.
• user_selectors are chart-specific switches that change what metric or window the chart returns. Each selector is keyed by the selector ID to pass in get-chart-data's selectors JSON object and usually includes allowed option IDs plus a default. For example, the revenue chart may use revenue_type (revenue, revenue_net_of_taxes, proceeds), while conversion charts may use conversion_timeframe and default to 7_days. State non-default selector choices when presenting results.
• resolutions list the supported time granularity and their string IDs for get-chart-data. You must always pass one of these resolution IDs (such as "0" for day or "2" for month) when later calling get-chart-data.