generated from mintlify/starter
-
Notifications
You must be signed in to change notification settings - Fork 7
Add Product use case #290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tothmano
wants to merge
7
commits into
main
Choose a base branch
from
mano/ai-product-use-cases
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add Product use case #290
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
6af7056
Add AI and Product use cases
tothmano 14ecfe0
Update ai-machine-learning.mdx
tothmano 97b8511
First fixes
tothmano b273fd1
Merge branch 'main' into mano/ai-product-use-cases
tothmano a4006f0
Update learn-about-axiom.mdx
tothmano 2857167
Merge branch 'main' into mano/ai-product-use-cases
tothmano ecbfc75
Address feedback
tothmano File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
--- | ||
title: "Axiom for product analytics" | ||
description: "This page explains how Axiom helps you leverage timestamped event data for product analytics purposes." | ||
sidebarTitle: Product analytics | ||
--- | ||
|
||
Axiom helps you leverage the power of timestamped event data. Axiom believes that event data reflects a broad range of interactions, crossing boundaries from engineering to product management, security, and beyond. For a more general explanation of event data in Axiom, see [Events](/getting-started-guide/event-data). | ||
|
||
This page explains how you can leverage the power of event data for the product analytics use case. | ||
|
||
In product analytics, the ability to harness and interpret data effectively can determine the success of a product. Axiom allows product analytics to leverage the power of timestamped event data and easily read every single event. This unique capability enables organizations to gain actionable insights, optimize user experiences, and drive product innovation. | ||
|
||
## Why event data matters in product analytics | ||
|
||
Event data captures the actions and interactions users have with a product over time. From button clicks and page views to error events and feature usage, every timestamped event tells a story about user behavior. Axiom’s platform is specifically designed to process and analyze these granular datasets, making it an indispensable tool for product teams aiming to do the following: | ||
|
||
- **Understand user behavior:** By tracking and analyzing event streams, Axiom provides a clear picture of how users engage with your product. | ||
- **Identify trends and patterns:** Time-series analysis reveals emerging trends, helping teams anticipate user needs and adjust strategies proactively. | ||
- **Optimize product features:** Pinpoint which features drive the most value and identify friction points that need improvement. | ||
|
||
## Key features of Axiom for product analytics | ||
|
||
The following key features make Axiom perfect for product analytics: | ||
|
||
- **Real-time event monitoring:** Axiom’s ability to ingest and process data in real-time means you can monitor user activity as it happens. This empowers product managers to act quickly in response to anomalies or unexpected usage patterns, reducing downtime and improving user satisfaction. For example: | ||
|
||
- Track whether feature flags are toggling as expected. | ||
- Watch for broken signup flows or onboarding drop-offs immediately after a deploy. | ||
- Monitor if newly launched features are generating engagement. | ||
|
||
- **Unified data platform:** Axiom eliminates data silos by integrating event data from diverse sources into a single, cohesive platform. Axiom stores system telemetry alongside product analytics data. This eliminates the traditional separation between “user behavior” tools and “engineering” tools, and this convergence unlocks powerful debugging and insight scenarios: | ||
|
||
- Correlate frontend feature usage with backend latency. | ||
- View conversion funnel stages alongside HTTP error logs. | ||
- Link user drop-off to infrastructure anomalies. | ||
|
||
- **Advanced query capabilities:** With a robust query language, Axiom enables product teams to dive deep into data analysis. Perform detailed segmentation, drill down into specific user journeys, and uncover insights that would otherwise remain hidden. | ||
- **Custom dashboards and visualizations:** Intuitive dashboards and customizable visualizations make it easy for product managers to communicate insights to stakeholders. Axiom’s visual tools enhance collaboration and decision-making. | ||
- **Scalable infrastructure:** As your product grows, so does the volume of event data. Axiom’s architecture is built to scale effortlessly, ensuring that your analytics remain robust and reliable, even with massive datasets. | ||
|
||
## Standard patterns for product data: Segment compatibility | ||
|
||
Axiom supports event ingestion via widely adopted patterns such as the [Segment specification](https://segment.com/docs/connections/spec/): | ||
|
||
- **`identify`** associates events with known users. | ||
- **`track`** records user interactions like button clicks or page views. | ||
- **`group`** associates users with organizations or accounts. | ||
|
||
Axiom is compatible with these conventions used by popular tools like Mixpanel, Amplitude, June, and RudderStack. | ||
|
||
This approach gives product teams a familiar and low-friction way to onboard their analytics events, and the foundation for querying user behavior via APL (Axiom Processing Language). | ||
|
||
For example, the APL query below filters tracked events by name: | ||
|
||
```kusto | ||
['segment-frontend-prod'] | ||
| where event == "Button Clicked" | ||
| summarize count() by userId, bin(_time, 1h) | ||
``` | ||
|
||
## Enhance product analytics with Axiom | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While this section is surely relevant, unless we provide a working examples of relevant APL I’m not sure how much confidence this would give me as a product person considering Axiom |
||
|
||
Axiom helps you make the most of your event data in the following product analytics use cases, among others: | ||
|
||
- **Feature adoption analysis:** Understand how new features are adopted by users and identify which aspects require improvement to maximize engagement. | ||
- **Retention and churn analysis:** Leverage event data to identify patterns in user retention and predict potential churn, enabling proactive interventions. | ||
- **Funnel optimization:** Analyze user journeys through critical funnels, such as sign-ups or purchases, to pinpoint drop-off points and optimize conversion rates. | ||
- **A/B testing:** Compare user interactions across different test groups to validate hypotheses and make data-driven decisions. | ||
|
||
## Use cases: from funnels to retention | ||
|
||
Here are some ways product teams use Axiom: | ||
|
||
### Feature adoption tracking | ||
|
||
Measure which users are engaging with newly released features. | ||
|
||
```kusto | ||
['segment-frontend-prod'] | ||
| where event == "Feature Used" and properties.featureName == "AI Chat" | ||
| summarize count() by userId, bin(_time, 1h) | ||
``` | ||
|
||
### Retention and churn analysis | ||
|
||
Analyze returning users over time: | ||
|
||
```kusto | ||
['segment-frontend-prod'] | ||
| where event == "Logged In" | ||
| summarize sessions = count(), users = dcount(userId) by bin(_time, 1w) | ||
``` | ||
|
||
### Funnel diagnostics | ||
|
||
Trace where users drop off between signup, onboarding, and first value. | ||
|
||
```kusto | ||
['segment-frontend-prod'] | ||
| where event in ("Signed Up", "Completed Onboarding", "Created Project") | ||
| project userId, event, _time | ||
| sort by userId, _time | ||
``` | ||
|
||
### A/B test measurement | ||
|
||
Compare experiment cohorts based on downstream engagement: | ||
|
||
```kusto | ||
['segment-frontend-prod'] | ||
| where properties.experimentGroup == "variant_a" | ||
| where event == "Clicked Upgrade" | ||
| summarize conversions = dcount(userId) | ||
``` | ||
|
||
## Why choose Axiom for product analytics | ||
|
||
Axiom’s focus on timestamped event data makes it perfect for product analytics. By crossing boundaries from engineering to product management and security, Axiom empowers cross-functional teams to collaborate effectively. Its comprehensive feature set ensures that organizations can unlock the full potential of their data, driving smarter decisions and fostering innovation. | ||
|
||
In competitive markets, understanding your users is paramount. With Axiom, you gain a trusted partner in turning event data into actionable insights that propel your product to new heights. Experience the future of product analytics with Axiom and transform how you build, analyze, and optimize your product. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a shame to publish content on product analytics and not touch on what has become something of a standard in Segment’s spec https://segment.com/docs/connections/spec/
Identify
,track
, andgroup
calls provide the rich foundation for event analytics, and it’s pretty common at this point for vendors to accept Segment events or services like RudderStack which follow the identical pattern because of it. Indeed, we ourselves use this in staging >segment-frontend-prod
andsegment-core-prod
so you can see the schema there withsegment-frontendprod | getschema
.Examples:
https://docs.mixpanel.com/docs/tracking-methods/integrations/segment
https://amplitude.com/docs/data/source-catalog/segment
https://help.june.so/en/articles/5988266-segment-setup
If nothing else, it would give a fairly approachable foundation in this material to then provide sample APL that is directionally sound for product folks.
Excited about this content - I think this could be a big win!