Usage analytics

Usage analytics shows how your brand has used Mirror Panel over the last week, month, quarter, or year: pulses submitted per day, how much of your included allowance is left, and where the brand's shared paid pulses went. The same numbers are available to an AI assistant connected to Mirror Panel, so you can also ask it.

Open usage analytics

Go to Brand Settings › Usage analytics. Every member of the brand can see it. The figures always belong to the brand selected in the top bar, and switching brands switches the numbers.

Usage analytics sits in Brand Settings, between Slack and Billing & usage.

Pick a time range

Choose 7 days, 30 days (the default), 90 days, or 12 months. Every range ends today. Days are UTC calendar days. The 12-month view groups days into weeks so the bars stay readable.

In the 12-month view the bar chart counts pulses per week.

The summary tiles

Four tiles along the top summarise the range:

• Brand pulses: every pulse submitted in this brand, by anyone.
• Your pulses: the pulses you submitted yourself.
• Included allowance: how many of your included pulses in this brand are left, with a meter for how much you have used. It reads Unlimited when no cap applies to you.
• Paid pulses: the brand's shared paid pulse balance, with how many paid pulses were used and added in the range. It appears only when billing is turned on for your workspace.

Pulses submitted per day

Each bar is one day. Hover a bar to see how many pulses the brand submitted that day and how many of them were yours. The bar under your pointer is highlighted.

• Each new pulse or rerun counts once, and so does each Ensemble Lab run. These are the submissions your allowance or the brand's paid pulses pay for.
• Follow-up iterations and competitor comparison runs are part of the pulse that started them, so they don't add to the count.
• Pulses shared with your brand from another brand are not counted. They were run and paid for there.
• Deleting a pulse doesn't give back its allowance slot, so a deleted pulse still counts on the day it was submitted.

Hover a day to see the brand's total and your share.

Allowance and paid pulse draw-down

Two step charts show how much was left at the end of each day. Your included allowance remaining counts down from your allowance in this brand; the dashed line marks the cap. It is hidden when your allowance is unlimited. Brand paid pulse balance follows the paid pulses every member of the brand shares: it goes up when a plan renews or a purchase lands, and down as pulses are run. Refunds and reversed charges show up too. It is shown only when billing is turned on.

The value labelled "now" at the end of each line always matches Billing & usage.

Both lines end on today's live figures, the same ones Billing & usage shows and that decide whether a new pulse can run. If older history is incomplete, for example for pulses from before usage tracking began, the difference shows up earlier in the chart. Today's number is never affected.

Read it as a table

Open Show as table under the charts for every day in the range, newest first: pulses, your pulses, allowance left, paid pulses used, paid pulses added, and the paid balance. Use it to copy exact figures, or with a screen reader.

The table holds the same data as the charts, one row per day (per week for 12 months).

When your allowance runs out

When you have used all of your included allowance in a brand, Usage analytics says so. With billing on, new pulses then draw on the brand's paid pulses, and the notice links to Billing & usage. With billing off, ask a brand admin to raise the brand's pulse quota.

Internal brand adoption view

Mirror Panel operators with Ops admin access can open Ops Console → Brands to see a separate cross-brand adoption view. On phones, use the Ops section picker above the active panel. The view tracks saved Pulse defaults, custom persona attributes, external invitations or members, whether the brand has submitted a Pulse, and whether an external member's Cognito account has received a token since joining. Token refreshes count, so this is not a count of interactive logins. The rate denominator is all non-demo brands, including personal workspaces. A time series chart lets operators select a KPI and inspect each dated sample's rate and exact count; a table lists all five rates together. Restored historical database samples are marked as such. Historical Cognito token status and external sharing classification are unavailable for restored dates. Older deleted Pulses may also be missing where no durable usage record or quota counter existed. This internal view is separate from the brand's Pulse usage and allowance shown above.

Ask your AI assistant

If you have connected Claude or ChatGPT to Mirror Panel, your assistant can read the same analytics. Claude uses mirror_get_usage_analytics; ChatGPT's focused connector uses mirror_get_brand_usage. Ask something like "How many pulses has our brand run this month, and how many paid pulses are left?" or "Which week in the last year was our busiest?". Both actions only read: neither can run a pulse or spend a paid pulse. They cover your active brand, and you can ask about another brand you belong to by name.

• days: 7, 30 (default), 90, or 365.
• The answer includes a short summary (totals, your allowance, the paid pulse balance, how many days had activity, and the busiest day) plus one row per day with the same fields as the table.
• The action reads the same API route the page uses, GET /v1/usage/pulses, so the assistant and the page always agree.

mirror_get_brand_usage { "days": 30 }

{
  "days": 30,
  "start_date": "2026-08-26",
  "end_date": "2026-09-24",
  "totals": { "pulses": 28, "my_pulses": 1, "credits_granted": 10, "credits_spent": 3 },
  "personal_allowance": { "used": 1, "limit": 3, "remaining": 2 },
  "credit_balance": 9,
  "points": [ { "date": "2026-08-26", "pulses": 3, "my_pulses": 0, ... } ]
}

Usage analytics only reads. Nothing on this page changes your allowance or spends a paid pulse. To buy pulses or change plan, open Billing & usage.