CSV import
Feeds: Partner roster and usage data
Not every system worth pulling from has an API you can reach, and waiting for an integration is a bad reason to delay scoring your ecosystem.
CSV import is deliberately first-class rather than a fallback. Bring in a partner roster from a PRM, an account-mapping export, a spreadsheet somebody has been maintaining for three years, or usage history from a warehouse. It lands the same way an API-backed connection does and feeds the same scores.
It is also the fastest way to get a real answer in front of your team. Most ecosystems are already in a spreadsheet somewhere.
What you get
Roster or usage, same path
Import the partners themselves, or period-by-period usage figures for partners you already track.
Matched, not duplicated
Rows match on name against what you already have, so a re-import updates rather than creating a second copy of everything.
Source is recorded
Every row carries where it came from, so you can tell at a glance which figures are API-backed and which were imported by hand.
Setting it up
- 1
Download the template so the column names line up.
- 2
Upload it. Rows are matched on name against your existing roster.
- 3
Score as normal. Imported data feeds the same dimensions an integration would.
Scores from this connection feed the six RADIUS dimensions and the activation gap. You can override any generated score.
Put your CSV import data to work.
RevRadius isn't open yet. Leave your email and we'll let you know the moment it is.