💡 Build Your Own Automated Insights
GermainUX allows organizations to create real-time insights tailored to their applications, business processes, users and operational priorities.
You can define what should be measured, which conditions should be detected, how results should be analyzed and visualized, and what action should occur when an important condition is found.
This makes it possible to extend GermainUX beyond its preconfigured insights without building a separate monitoring or analytics solution for every use case.
📦 What You Can Build
Custom insights can help answer organization-specific questions such as:
|
Question |
|
|---|---|
|
1 |
Which users are unable to complete a critical workflow? |
|
2 |
Which products, pages or application features create the most friction? |
|
3 |
Where is employee time being lost? |
|
4 |
Which errors affect the greatest number of users? |
|
5 |
Which customer journeys are abandoning? |
|
6 |
Which application versions or technology components are underperforming? |
|
7 |
When should a team be alerted or an approved remediation action begin? |
⚙️ From Measurement to Action
A custom automated insight can combine several GermainUX capabilities:
Collect → Measure → Detect → Analyze → Visualize → Alert or Automate
|
Capability |
Purpose |
|---|---|
|
KPI |
Define the business, user-experience, workflow or technology condition to monitor |
|
Rule |
Detect specific events, patterns or conditions and apply logic to monitored data |
|
Measures and pivots |
Calculate results and break them down by relevant dimensions |
|
Dashboard |
Visualize trends, impact, segments and supporting evidence |
|
Custom data table |
Store additional organization-specific data required for analysis |
|
Automation |
Alert, report, execute a script, run an RPA workflow or initiate another approved action |
These capabilities can be used independently or combined into a complete automated insight.
📋 Create a Custom KPI
A KPI defines what GermainUX should monitor and how its health or business significance should be evaluated.
Custom KPIs can represent:
|
Type |
|---|
|
User behavior |
|
Business-process milestones |
|
Adoption and feature usage |
|
Conversion and abandonment |
|
Productivity and time lost |
|
Errors and exceptions |
|
Application performance |
|
Infrastructure availability and capacity |
|
Customer feedback or conversation outcomes |
|
Organization-specific business events |
A KPI can include measures, dimensions, SLAs, thresholds, relationships and drilldown behavior according to the required analysis.
⚖️ Create a Rule
Rules define how GermainUX recognizes, enriches, categorizes or responds to specific conditions in monitored data.
A rule can be used to:
|
Use |
|---|
|
Detect a known event or pattern |
|
Apply business-specific conditions |
|
Categorize or enrich collected data |
|
Identify a workflow milestone |
|
Associate an event with a user, application or business process |
|
Trigger further analysis or automation |
Rules are appropriate when the condition can be expressed through deterministic logic. Statistical or AI-assisted analysis can complement rules when the pattern is less explicit.
📊 Add Measures and Pivots
Measures determine which values are calculated. Pivots break those values down by meaningful dimensions.
Examples of measures include:
|
Measure |
|---|
|
Count or occurrence rate |
|
Average, median or percentile duration |
|
Total lost productivity |
|
Conversion or completion rate |
|
Revenue or business impact |
|
Error frequency |
|
A custom numeric value |
Examples of pivots include:
|
Pivot |
|---|
|
Application and environment |
|
Page, screen or feature |
|
User, role or team |
|
Business process and milestone |
|
Product, campaign or customer segment |
|
Device, browser or version |
|
Region or location |
|
Error, component or dependency |
Combining measures and pivots helps teams understand not only whether an issue exists, but also where it is concentrated and who is affected.
Learn how to add measures and pivots to a portlet.
🖥️ Create a Dashboard
Custom dashboards present the insight to the teams responsible for understanding or acting on it.
A dashboard can display:
|
Display |
|---|
|
Current health and trends |
|
Comparisons with a previous period or baseline |
|
Affected users, sessions or transactions |
|
Business-impact measures |
|
Breakdowns by relevant dimensions |
|
Related KPIs and correlated conditions |
|
Drilldowns to individual events, traces or Session Replay |
Dashboards can be tailored for business, product, support, engineering or executive audiences so each team sees the evidence relevant to its role.
Learn how to create a dashboard.
💾 Store Custom Data
Some automated insights require data that is not part of the standard GermainUX model. Custom database tables can store organization-specific reference or analytical data used by KPIs, rules, dashboards and automation.
Examples can include:
|
Example |
|---|
|
Business targets and thresholds |
|
Product or service reference data |
|
Organizational mappings |
|
Workflow definitions |
|
External classifications |
|
Custom analytical results |
Custom data should be modeled and governed according to its intended purpose, retention requirements and access restrictions.
.
🤖 Add Automation
Once an insight is detected, GermainUX can notify the appropriate team or initiate an approved response.
Automation options can include:
|
Option |
|---|
|
Real-time alerts |
|
Scheduled or event-driven reports |
|
Script execution |
|
RPA workflows |
|
HTTP or system actions |
|
Dynamic investigation actions |
|
Approved remediation workflows |
Automation should be used when the detection logic and required response are sufficiently understood. Actions that could affect users, business data or production systems should include appropriate safeguards and authorization.
Learn more about GermainUX automation.
🔍 Example: Detect and Resolve a Slow Workflow
A custom insight for a slow business workflow could include:
|
Component |
|---|
|
A KPI measuring workflow completion time |
|
A rule identifying the workflow’s start, milestones and completion |
|
Measures for duration, occurrences and lost productivity |
|
Pivots by application, team, user and workflow stage |
|
A dashboard showing trends, affected groups and supporting sessions |
|
An alert when the SLA is violated |
|
An approved automation that initiates investigation or remediation |
This creates a complete workflow from monitoring and detection to evidence, prioritization and action.
✨ AI-Assisted Custom Insights
Custom prompts can also analyze monitored data using natural language. Depending on the use case, AI can help:
|
AI Capability |
|---|
|
Summarize sessions, transactions or conversations |
|
Categorize recurring friction |
|
Explain relationships across KPIs |
|
Identify the users or segments most affected |
|
Generate investigation guidance and recommendations |
|
Produce stakeholder-specific reports |
AI-generated findings should support—not replace—appropriate business and technical review.
🔒 Security and Governance
Custom insights should follow the organization’s data-security, privacy and operational-governance requirements.
Before deployment, confirm:
|
Check |
|---|
|
Which data is required and permitted |
|
Who may view the resulting insight |
|
How long custom data should be retained |
|
Whether sensitive information must be masked or excluded |
|
Which alerts and automated actions are authorized |
|
How changes will be tested and validated |
🤝 Get Help
GermainUX can help design custom KPIs, rules, data models, dashboards and automation for your specific use case.
Service: Analytics
Feature Availability: 8.6.0 or later