English
English
English
English
SalesDash is built around five interconnected concepts. Understanding how they relate to each other is the foundation for any implementation.
| Concept | What it is |
|---|---|
| Agents | The people whose performance is tracked |
| Providers | The external systems that supply data |
| External Identities | The bridge between provider data and SalesDash entities such as agents |
| Activities | The raw events that metrics are built from |
| Metrics | The calculations that turn activities into numbers |
Step 1 — Connect a provider (configure once)
When a provider syncs data, SalesDash stores each record as an Activity. For every user, team, or project referenced in that data, SalesDash automatically creates an External Identity if one doesn't exist yet. You configure a provider once; it keeps running and ingesting data from that point forward.
Step 2 — Map external identities (monitor periodically)
External Identities arrive without knowing which internal Agent, Team, or Project they correspond to. You review the unlinked identities and assign each one to the correct SalesDash entity. Once linked, all activities from that identity — including those already stored — become attributed to the entity you linked it to.
This step requires periodic attention. Whenever a new agent joins or a new project is created in the external system, a new unlinked identity will appear. Unlinked identities are not attributed to anyone, so their data is not counted until you map them.
Step 3 — Define metrics (configure once)
A Metric defines what to count or sum and how to display the result. It is a reusable definition that competitions, goals, achievements, and widgets all reference. Each of those consumers applies its own scope — which agents, which time window, which filters.