01 / What is settled today
Planned, not available
This capability is specified and not built yet. There is no date and no separate price.
Mapping
- Data source
- Planned
- Result in your workspace
- Not possible yet
Product analytics · Planned
How your product is used,
tracking plan first, data second.
Product analytics for SaaS teams is planned: usage events from your own product are meant to reach Peak Analytics through a planned interface. Today there is no tracking SDK and no API for that; Peak Analytics reads no usage from your product. What you can do today: write a tracking plan and evaluate feedback tasks in Peak Task.
Today: set up a tracking planPlanned, not available. No tracking SDK, no API. In the preview you evaluate tasks, goals, orders, receipts and files.
Your Peak appsFrom the sourcePeak AnalyticsIn the evaluationPeak Analytics · data source
One field up close
01 / Your Peak appsEvent from your product (planned, interface)
02 / Fictional sample value“Report exported” (fictional)
03 / Peak Analytics
eventA readable path, for illustration. The connection is planned; nothing is transferred here.
View all 4 mappings
| Your Peak apps | Peak Analytics property |
|---|---|
| Event from your product (planned, interface) | event |
| Account (planned) | account_id |
| Time (planned) | timestamp |
| Today: tasks · Peak Task (preview) | tasks |
Planned
Not built yet
Not built yet
This connection is planned and not available yet. This page connects, fetches and transfers nothing.
One concrete sourcePeak AnalyticsEvaluation in Peak AnalyticsNot built yet
Understand fields. Keep permissions.
Peak AnalyticsEvaluation in Peak AnalyticsNot built yetThe mapping shows the planned path. Only the built product will show that data arrives this way.
How it is planned
Plan, connect, evaluate.
Three steps, and the first one is already your job today.
- 01 / Write a tracking plan
Write a tracking plan
Possible today, without Peak Analytics: you define events, what they mean and the questions behind them. The guide shows how.
How many new accounts export a report in their first week?Event “report exported” (planned, interface)Rows start week, count of accountsToday: define it in the tracking plan - 02 / Connect events
Connect events
Planned: through an interface, events from your product are meant to arrive with account and time. There is no SDK or API for this yet.
Which areas produce the most bug reports?Tasks from Peak Task, board “Feedback”Rows area, columns week, countCan be evaluated in the preview - 03 / Evaluate usage
Evaluate usage
Planned: events per account and week in a pivot. Today you evaluate feedback and bug reports as tasks in Peak Task by board, status and week.
Are our product goals for this quarter on track?Goals from Peak GoalsRows level, columns status, countAt-risk goals via “Check”
Honest about the status
What this page promises and what it does not.
Mapping02 / Your control
Fictional examples
Businesses and numbers on this page are made up and marked as examples. None of it is a measurement or a customer result.
- वर्कस्पेस
- Not connected
- Permissions
- Stay with you
03 / The clear limit
What works today
Peak Analytics is available as a preview: pivot evaluations over orders, receipts, tasks, goals and files, CSV export and sharing.
- Preview
- Example
- Needs approval
- Planned
Your next step
A good plan is half the dataset.
Set up your tracking plan with the guide. It helps with any tool and is the groundwork for the planned product analytics.
Today: set up a tracking plan→An example is not a result. What your data really shows you only see in your workspace.
Frequently asked questions
Can I use this in Peak Analytics yet?
No. This capability is planned and not built yet; there is no launch date. Available today is the Peak Analytics preview: pivot evaluations over orders, receipts, tasks, goals and files with CSV export and sharing.
Is there an SDK for my product?
No. There is no tracking SDK and no API today; Peak Analytics reads no usage from your product. API and SDK are planned.
What can a product team evaluate today?
Feedback and bug reports kept as tasks in Peak Task by board, status and week, and product goals from Peak Goals by status.
Why a tracking plan first?
Because events without a clear meaning don't make honest numbers. The plan helps with any tool and is the groundwork for the planned product analytics.