Dashboard navigation
Find every screen, choose the right scope, and follow detail flows.
Download this chapterOn this page
The dashboard is a project- and app-scoped view of verified purchase data and configuration. Begin by checking the project/app switcher. A filter or detail URL does not authorize access to another project.
Every screen at a glance
| Screen | What you do there | Typical next step |
|---|---|---|
| Overview | Inspect recent health, revenue by currency, activity, and setup signals | Open a chart or a recent record |
| Charts | Choose a metric, range, filters, comparison, visualization, and currency | Inspect the series, save it, or export |
| Saved views | Open/edit reusable customer, transaction, or event filters | Drill into a current result |
| Customers | Search app-user identities and open access/purchase history | Inspect a transaction or add a support note |
| Transactions | Filter current store transaction projections | Open the transaction and its customer |
| Event stream | Inspect normalized immutable observations and changes | Trace the related transaction/customer |
| Product sets | Create/edit the ordered packages presented by the SDK | Mark a set current and read it from the client |
| Products | Register store IDs and inspect store facts/mappings | Add the correct access mapping |
| Access levels | Define stable feature access and inspect mapped grants | Check a customer's resulting access |
| Apps | Create, inspect, select, and edit store app identities | Connect a store or obtain SDK keys |
| API keys | Create and revoke app secret/publishable keys | Update backend or client configuration |
| Integrations | Enter store setup or webhook configuration | Verify a purchase or inspect delivery |
| Account | Manage your password and signed-in sessions | Revoke an old session or sign out |
| Project settings | Rename the project, manage team invitations/roles, read activity | Invite a teammate or review a change |
| Setup guide | Follow the app/access/test-purchase checkpoints | Open the relevant configuration screen |
The public marketing pages explain use cases. The documentation center is the detailed operating reference; it does not require a dashboard login.
Find the right scope
The switcher chooses both the project and reporting app. App detail pages can be inspected without changing the active app; their selection action explicitly changes the wider context. Some detail links carry an app identifier to avoid ambiguity when two apps have the same store product ID.
On tablets/phones, navigation rails collapse or scroll. Use the navigation control to reach sections; horizontal chart/filter strips can be scrolled where needed. A hidden management action under View access is a role restriction, not a loading failure.
Filter and drill down
Search, platform, environment, status/type, time ranges, and sort controls vary by dataset. Filters are reflected in URLs where supported. Opening a detail and returning should preserve the originating list's filter/tab state.
Pagination applies to the filtered dataset. If the chosen page no longer has results after a filter change or deletion, return to the first page or clear the restrictive filter. An empty result is different from a request failure; use the displayed retry/error state when data could not be loaded.
Overview versus detailed reports
Overview provides a bounded recent history (up to 180 UTC days) and summaries for orientation. Charts provide metric-specific windows and deeper analytical controls. For complete normalized raw history, queue a durable export rather than assuming a chart response contains every source row.
A saved chart is a saved analytical configuration. A saved view is a saved live dataset query. They are separate tools; saved views and exports explains the difference.
Configuration workflows
After creating an app or API key, copy one-time secrets before dismissing the result. A successful store credential upload means it was accepted for storage; check the next steps for notifications and a real sandbox purchase. Product mapping and product presentation are also separate checkpoints.
A settings change that fails validation should be corrected from the error shown. A session expiration returns you to sign-in with the local destination preserved. If a resource disappears because membership/app scope changed, reselect the intended project instead of reusing an old link as authority.
Use the dedicated guides
For investigation, read Customers and Transactions and events. For analysis, read Charts, Metrics, and Cohorts. For configuration, follow Quickstart and the store/catalog guides.
Import an existing catalog
Open Migration in the Configure navigation group, or Products → Import from store. Choose RevenueCat, CSV/JSON, App Store, or Google Play. Store imports load a complete product selection; file imports validate a portable catalog. The preview separates additions, existing entries, and conflicts. Managers apply the plan, download its report, and inspect recent import history.
A successful screen says Catalog imported. Customer migration is a distinct verified-purchase step; opening an import report is not evidence that all prior purchases or historical analytics have moved. The migration guide covers that follow-up, Google base-plan policy, source credentials, and CLI checkpoints.