Study guide

14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs

Dynatrace Certified Associate Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Overview, Deployment Models & Architecture

1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub 1.2 SaaS vs. Dynatrace Managed Architecture & Security 1.3 Core Telemetry Components: OneAgent, ActiveGate & Grail Lakehouse 1.4 Licensing Models: Dynatrace Platform Subscription (DPS) & Davis Data Units (DDUs)

2 Chapter 2: ActiveGate Architecture & Network Topologies

2.1 ActiveGate Types: Environment vs. Cluster ActiveGates 2.2 ActiveGate Capabilities: Proxying, Private Synthetic, Cloud Integrations & Extensions 2.3 Network Zones, Multi-DC Routing & Firewall Traversal

3 Chapter 3: OneAgent Deployment, Configuration & Management

3.1 OneAgent Architecture, Components & Automatic Injection 3.2 Host Installation on Linux, Windows & Containerized Hosts 3.3 Cloud-Native Deployment: Dynatrace Operator on Kubernetes & OpenShift 3.4 Kubernetes Observability: Clusters, Nodes, Namespaces, Workloads & Events

4 Chapter 4: Monitoring Modes, Process Groups & Infrastructure Observability

4.1 Monitoring Modes: Full-Stack vs. Infrastructure-Only vs. Discovery 4.2 Process Groups, Process Instances & Custom Process Group Detection Rules 4.3 Host Groups, Host Naming Rules & Environmental Metadata Extraction 4.4 Infrastructure & Operations: Host Health, Disk, Network & Availability Analysis 4.5 Database Observability: The Databases App, Connection Pools & Storage Latency

5 Chapter 5: Smartscape Topology & Service Flow

5.1 The 5-Layer Smartscape Topology: Datacenter to Application 5.2 Service Detection: Web Services, Background Tasks & Custom Services 5.3 Service Flow, Backtrace Analysis & Horizontal/Vertical Dependency Mapping

6 Chapter 6: PurePath Distributed Tracing & Code-Level Diagnostics

6.1 PurePath Architecture, Distributed Tracing & Request Context Propagation 6.2 Method Hotspots, CPU Profiling & Memory Allocation Thread Analysis 6.3 Database Service Diagnostics, Slow Queries & Exception Analysis

7 Chapter 7: Davis AI Engine, Baselining & Causation

7.1 Davis Deterministic Causation Engine vs. Pure Correlation 7.2 Automated Dynamic Baselining, Percentiles & Traffic Seasonality 7.3 Event Ingestion, Event Types & Event Hierarchy in Problem Evolution

8 Chapter 8: Problem Lifecycle, Root Cause Analysis & Alerting

8.1 Problem Lifecycle, Severity Categories & Root Cause Cards 8.2 Alerting Profiles, Delay Filters & Management Zone Routing 8.3 Problem Notification Integrations: Webhooks, Slack, ServiceNow & ITSM

9 Chapter 9: Digital Experience Monitoring: Synthetic Monitoring

9.1 Synthetic Monitors: HTTP, Single-Step Browser & Multi-Step Clickpaths 9.2 Private Synthetic Locations, ActiveGate Engines & Credential Vault 9.3 Outage Detection, Performance Baselining & Maintenance Suppression

10 Chapter 10: Digital Experience Monitoring: Real User Monitoring (RUM)

10.1 RUM Architecture, OneAgent Script Injection & Mobile/OpenKit Telemetry 10.2 User Actions: Load vs. XHR/Fetch Actions, Visually Complete & Speed Index 10.3 Apdex Performance Ratings, User Sessions & Session Replay Masking

11 Chapter 11: Log Management and Analytics on Grail with DQL

11.1 Log Management on Grail: Storage, Ingestion Pipelines & Log Masking 11.2 Dynatrace Query Language (DQL): Fetch, Filter, Fields & String Operations 11.3 DQL Aggregations: Summarize, MakeTimeseries, Sorting & Visualizations

12 Chapter 12: Platform Governance, OpenTelemetry & Automation

12.1 Management Zones: Scoping Observability, Dashboards & Access Control 12.2 Tagging Strategies: Automated Rule-Based Tags, Manual Tags & AWS/K8s Metadata 12.3 OpenTelemetry Ingestion, OpenPipeline & Dynatrace Workflows Automation

13 Chapter 13: Cloud Integrations & Agentless Infrastructure Ingestion

13.1 AWS, Azure & Google Cloud Integrations 13.2 VMware vSphere, Extensions & Other Agentless Ingestion Paths

14 Chapter 14: Business Analytics & Business Events

14.1 Business Events: Capture, Ingestion & the bizevents Grail Table 14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs

15 Chapter 15: Notebooks, Dashboards & Data Visualization

15.1 Notebooks: Section-Based Investigation & Shareable Analysis 15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring 15.3 Choosing Visualizations: Data Explorer, Chart Types & Metric Selection

16 Chapter 16: Reporting, Metrics & User Behavior Analysis

16.1 Metrics on Grail: Built-in Metrics, Granularity & Retention 16.2 Dashboard Reports, Subscriptions & Exporting Data via APIs 16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals 16.4 Session Segmentation, User Journeys & Funnel Drop-Off Analysis

17 Chapter 17: Security, Vulnerability Analytics & Application Protection

17.1 Platform Security: Data Privacy, Encryption & Access Control 17.2 Third-Party Vulnerabilities, the Davis Security Score & Security Advisor 17.3 Code-Level Vulnerabilities, Attacks & Runtime Application Protection 17.4 Security Investigator, Notifications & the Remediation Workflow

14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs

Key Takeaways Explain This Topic AI

Business Analytics connects application performance and user experience to business metrics so business and IT teams collaborate through shared real-time perspectives.

The core analytical move is joining a technical problem window to business event data over the same timeframe to quantify impact in currency or conversions.

Funnel analysis over business events exposes which step of a multi-stage journey loses customers, which pure technical metrics cannot show.

Business KPI deviations can trigger Davis events and Workflows, so a revenue drop becomes an alert rather than a month-end discovery.

Segmenting business events by customer tier, region, payment method, or channel is what turns an aggregate number into an actionable finding.

Last updated: September 2026

Section 14.1 got business events into Grail. This section is about what the exam actually asks: what business question does this data answer, and how?

Dynatrace's positioning is that Business Analytics connects application performance and user experience to business metrics, enabling business and IT teams to collaborate through shared real-time perspectives , and that it simplifies critical, real-time business decisions with precision, speed, and context . Translated into exam terms: Business Analytics is what lets one system answer both "was the service degraded?" and "what did that degradation cost?"

Pattern 1: Quantifying Incident Impact

This is the highest-value use case and the one most likely to appear as a scenario.

A Davis problem opens at 14:05 and closes at 14:47 on the payment service. The technical answer is "42 minutes of elevated failure rate." The business answer requires comparing the same window against a healthy baseline: fetch bizevents, from: -7d

  • | filter event.type == "order.completed"
  • | makeTimeseries revenue = sum(order.amount), interval: 5m

Overlay the problem window and the shortfall is directly readable. A more targeted version compares the incident window to the same window on prior days: fetch bizevents, from: now() - 1h

  • | filter event.type == "order.completed"
  • | summarize revenue = sum(order.amount),
  • orders = count(),
  • by: { payment.method }
  • | sort revenue desc

Because business events are not sampled (14.1), the resulting figure is a real number rather than an estimate — which is what makes it usable in an executive incident report.

Pattern 2: Funnel and Drop-Off Analysis

A multi-step journey — browse, add to cart, enter address, enter payment, confirm — emits a business event at each step. Counting events per step produces the funnel: fetch bizevents, from: now() - 24h

  • | filter event.provider == "checkout"
  • | summarize sessions = countDistinct(session.id), by: { funnel.step }
  • | sort funnel.step asc

The insight lives in the ratios between steps , not the absolute numbers. A funnel that holds 92%, 89%, and 91% between stages and then collapses to 34% at the payment step localizes the problem precisely. Crucially, this is invisible in technical metrics: if the payment page returns HTTP 200 in 300 ms every time, availability and latency both look perfect while the business bleeds.

That contrast — healthy technical signals, failing business outcome — is the signature scenario for this topic. The answer is always business events or RUM conversion analysis, never a service metric.

Pattern 3: Segmentation

An aggregate figure hides the finding. The same query grouped by a business dimension exposes it:

  • Segment by Reveals
  • customer.tier Whether high-value customers are disproportionately affected
  • geo.region A regional CDN, payment provider, or datacenter issue
  • payment.method A single failing payment processor
  • channel (web/mobile/API) A broken release on one client platform only
  • product.category A pricing, inventory, or catalogue defect

Worked example: total conversion is down 4% — small enough to ignore. Segmented by payment.method , one provider has dropped 71% while the others are flat. The aggregate number would never have prompted an investigation; the segmented one names the vendor to call.

Pattern 4: Alerting on Business KPIs

Business events do not have to be read retrospectively. Because they live in Grail alongside everything else:

A DQL-based metric or event can be derived from business event volume or value.

Davis can apply anomaly detection to that signal, so an unexplained drop in completed orders raises a problem the same way a latency regression does.

A Workflow (Chapter 12) can act on it — notify a business channel, open a ServiceNow ticket, or trigger a rollback.

The operational shift the exam wants you to recognize: a revenue anomaly becomes an alert in minutes instead of a discovery at month-end reporting.

Pattern 5: Shared Context Between Teams

The collaboration argument is a genuine exam point rather than marketing. Because business events, traces, logs, and infrastructure metrics share Grail and Smartscape:

A business analyst filters completed orders by region in a Notebook and sees the drop.

The same Notebook holds the Davis problem and the PurePath for the failing requests.

Nobody exports a CSV, and nobody argues about whose numbers are correct, because there is one dataset.

What Business Analytics Is Not

Two boundaries commonly tested:

It is not RUM. RUM measures experience — load times, Apdex, errors, user actions. Business Analytics measures outcomes — value, conversions, counts. They are complementary, and both feed the DEM picture, but a question asking for order value is not answered by Apdex.

It is not a replacement for a data warehouse. Business Analytics excels at real-time, operational business questions with technical context. It is not positioned as the system of record for year-over-year financial reporting.

Loading diagram... From Technical Signal to Business Outcome: The Business Analytics Loop