Custom metrics & dashboards

Connect a partner's systems, and PartnerOS turns the event stream into insight. Define custom metrics — count, sum, or unique — over any event, then compose dashboards of metric, time-series, and event-list widgets, rendered at whatever partner level you choose.

app.partneros.com/dashboards
Dashboards /Acme Corp · custom
N
DashboardMetricsWidgets
Activations
1,204+18%
Revenue events
$84.2k+11%
Active users
3,918+6%
Uptime
99.9%
Unique active users · 30dmetric: unique
Activations · count
Revenue · sum
Recent events
feature_usedexport
checkout$1,240
feature_usedapi_call
signupseat +1
feature_usedreport
The problem

Every partner wants different numbers, and you can't hand-build them all

One partner cares about activations, another about usage, another about revenue events. Building bespoke reporting for each is impossible — so everyone gets the same generic dashboard that fits no one.

How it works

The flow, end to end

01

Connect

A partner's system sends events to the ingest rail; they land on the customer's stream.

02

Define

You define a metric — count of activations, sum of revenue, unique active users.

03

Compose

Add metric and chart widgets to a dashboard and save it.

04

View

Render it per partner. Operators see across levels; a partner sees only their own slice.

Capabilities

What's in the box

Event ingestion

Push customer events over a machine rail — resolve by id or email — or record them in-app.

Custom metrics

Operator-defined count / sum / unique metrics computed over the event stream.

Any scope

Compute a metric at partner, customer, or all-partners scope, with time windows and grains.

Custom dashboards

Compose metric, time-series, and event-list widgets into a saved dashboard.

Per-partner rendering

Render the same dashboard at a chosen partner level — operators build, partners self-view.

Operator builds, partner views

Cross-partner reporting with a hard isolation guard

An operator defines a metric or dashboard once and views it at any partner level; a partner viewing the same dashboard is forced to their own slice, with a leak guard proven in tests. One definition, safely shared.

  • count / sum / unique aggregations over arbitrary event payloads
  • Day / week / month / quarter windows with time-series grains
  • Managing-operator visibility without exposing sibling partners
app.partneros.com/dashboards
Dashboards /Acme Corp · custom
N
DashboardMetricsWidgets
Activations
1,204+18%
Revenue events
$84.2k+11%
Active users
3,918+6%
Uptime
99.9%
Unique active users · 30dmetric: unique
Activations · count
Revenue · sum
Recent events
feature_usedexport
checkout$1,240
feature_usedapi_call
signupseat +1
feature_usedreport
From event to insight

One ingest rail feeds every metric you define

Customer events arrive over a machine-key rail — resolved by id or email — or are recorded in-app. From that single stream you define count, sum, or unique metrics over any payload field, then window and grain them however each partner needs, and drop them onto a saved dashboard.

  • Ingest by machine key; resolve the customer by id or email
  • count / sum / unique over arbitrary event payloads
  • Day / week / month / quarter windows and time-series grains
app.partneros.com/dashboards
Dashboards /Acme Corp · custom
N
DashboardMetricsWidgets
Activations
1,204+18%
Revenue events
$84.2k+11%
Active users
3,918+6%
Uptime
99.9%
Unique active users · 30dmetric: unique
Activations · count
Revenue · sum
Recent events
feature_usedexport
checkout$1,240
feature_usedapi_call
signupseat +1
feature_usedreport
3
metric types: count, sum, unique
5
widget kinds per dashboard
1
definition, rendered at any partner level
0
chance a partner sees a sibling's slice

Ready to run your partner program in one place?

Book a walkthrough and see recruitment, PRM, automation, payouts, CX, and dashboards working together — on one platform.