Study guide
16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals
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
16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals
Key Takeaways Explain This Topic AI
User analytics track metrics such as bounce rates, top landing pages, top exit pages, and conversion rates to reveal how users actually behave.
The Top 3 bounces view compares the duration and JavaScript errors of bounced actions against the same actions in sessions that did not bounce, isolating performance as a cause.
The first page load or XHR action of a session is effectively the landing page, and the last one is the exit action.
Inspecting the Apdex rating on exit actions shows whether a poor experience is driving users away.
Conversion goals turn behavioural analysis into a measurable target that can be tracked and alerted on.
Last updated: September 2026
Chapter 10 covered how RUM measures experience — user actions, Visually Complete, Speed Index, Apdex. The Reporting and Analysis topic goes one step further and asks what users did : where they arrived, where they left, and whether they converted. Dynatrace's own framing is that user analytics provide valuable data on how users interact with applications, tracking metrics like bounce rates, top landing pages, exit pages, and conversion rates.
This is the bridge between technical performance and business outcome, and exam scenarios in this area almost always hinge on connecting the two.
Bounce Rate
A bounce is a session containing a single user action — the visitor arrived and left without further interaction. Bounce rate alone is ambiguous: a documentation page with a high bounce rate may be doing its job perfectly, while a product page with the same rate is failing.
What makes the Dynatrace treatment diagnostic rather than descriptive is the comparison built into the Top 3 bounces view. It shows which user actions have the most bounces and lets you compare the duration of bounced actions with the same user actions in sessions where those actions did not bounce , and it does the same for JavaScript errors .
That comparison is the whole trick, and it is highly testable:
Bounced instances are much slower than non-bounced instances of the same action → performance is driving people away. Fix the page.
Bounced instances carry JavaScript errors that non-bounced instances do not → a client-side defect, possibly browser-specific, is breaking the page for a subset of users.
Duration and errors are identical either way → performance is not the cause. The problem is content, relevance, pricing, or acquisition — send the finding to marketing or product, not to engineering.
That third outcome is the one candidates get wrong. A high bounce rate with no performance differential is not an engineering problem, and answers proposing a caching or CDN change in that situation are the distractor.
Landing Pages
The first page load or XHR action of a session is effectively the landing page, and Dynatrace directs you to watch the trend of that first action . Landing actions deserve disproportionate attention for two reasons:
They are a first impression with no accumulated goodwill and no warm cache.
They are frequently the slowest actions in the session , because nothing is cached, the connection is cold, and the full asset payload is fetched.
A landing action that has degraded is a leading indicator of a bounce-rate rise, which is why the two views are read together.
Exit Pages
The mirror image: watch the action duration of the last page load or XHR action of your users so that you can identify whether they leave your application because of performance problems. And crucially — inspect the Apdex rating on the exit actions to see if a bad experience is leading users to exit.
That instruction gives you a clean decision rule:
- Exit action Apdex Interpretation
- Frustrated / poor Users are leaving because of the experience — an engineering problem
- Satisfied / good Users are leaving for a non-performance reason — content, price, or they simply finished
And one important nuance: a high exit rate on the order-confirmation page is success, not failure. Exit analysis must always be read against journey intent. Exam scenarios sometimes present a "worrying" exit rate on a terminal page precisely to see whether you apply that judgment.
Conversion Goals
A conversion goal defines what a successful session looks like — reaching a URL, completing a named user action, or firing a specific event. Once defined, Dynatrace tracks the conversion rate and lets you review overall metrics related to your conversion goals or analyze progress toward specific goals .
Conversion goals matter for three reasons:
They make a business outcome a first-class, chartable measurement , so it can appear on the same dashboard as latency.
They enable the correlation that justifies performance work: sessions with satisfied Apdex convert at 4.1%, sessions with frustrated Apdex convert at 0.9%. That single sentence funds more optimization work than any latency chart.
A conversion drop can be alerted on rather than discovered at month-end.
Segmentation Is Mandatory
Aggregate behavioural numbers hide the finding, exactly as they do for business events (Section 14.2). Dynatrace lets you segment user behavior analytics by satisfaction, device, location, app version, operating system and many more.
Worked example: overall bounce rate rises from 22% to 26% — plausibly noise. Segmented by app version , the previous release sits at 21% and the new one at 58%. Segmented further by operating system , the increase is confined to one mobile browser. That is now a specific, actionable defect rather than a statistic, and it took two segmentations to find.
The Analysis Order That Answers Exam Scenarios
Is the behavioural metric actually anomalous versus the same period previously?
Segment by version, device, OS, geography, and satisfaction until the change concentrates.
Compare bounced against non-bounced instances of the same action for duration and JavaScript errors.
Check Apdex on the exit action to decide whether experience is the cause.
If no performance differential exists, hand it to product or marketing — and say so. That is a legitimate, and frequently correct, answer.