diff --git a/docs/apm/getting-started.asciidoc b/docs/apm/getting-started.asciidoc
index 1d77dbb405fe..357f694453f4 100644
--- a/docs/apm/getting-started.asciidoc
+++ b/docs/apm/getting-started.asciidoc
@@ -6,6 +6,24 @@
Get started
++++
+// Conditionally display a screenshot or video depending on what the
+// current documentation version is.
+
+ifeval::["{is-current-version}"=="true"]
+++++
+
+
+
+++++
+endif::[]
+
For a quick, high-level overview of the health and performance of your application,
start with:
diff --git a/docs/apm/service-maps.asciidoc b/docs/apm/service-maps.asciidoc
index a3ac62a4c834..99a6205ae010 100644
--- a/docs/apm/service-maps.asciidoc
+++ b/docs/apm/service-maps.asciidoc
@@ -8,14 +8,34 @@ requests per minute, and errors per minute.
If enabled, service maps also integrate with machine learning--for real time health indicators based on anomaly detection scores.
All of these features can help you quickly and visually assess your services' status and health.
+// Conditionally display a screenshot or video depending on what the
+// current documentation version is.
+
+ifeval::["{is-current-version}"=="true"]
+++++
+
+
+
+++++
+endif::[]
+
+ifeval::["{is-current-version}"=="false"]
+[role="screenshot"]
+image::apm/images/service-maps.png[Example view of service maps in the APM app in Kibana]
+endif::[]
+
We currently surface two types of service maps:
* Global: All services instrumented with APM agents and the connections between them are shown.
* Service-specific: Highlight connections for a selected service.
-[role="screenshot"]
-image::apm/images/service-maps.png[Example view of service maps in the APM app in Kibana]
-
[float]
[[service-maps-how]]
=== How do service maps work?