update trace retention

Author: rtrieu

content/en/real_user_monitoring/correlate_with_other_telemetry/apm/_index.md

@@ -458,7 +458,7 @@ To verify you've configured the APM integration with RUM, follow the steps below
 
 To view traces from the RUM Explorer:
 
-1. Navigate to your [list of sessions][21] and click on a session that has traces available. You can also query for sessions with traces by using`@_dd.trace_id:*`.
+1. Navigate to your [list of sessions][22] and click on a session that has traces available. You can also query for sessions with traces by using`@_dd.trace_id:*`.
 
 When you select a session, the session panel appears with a request duration breakdown, a flame graph for each span, and a **View Trace in APM** link.
 
@@ -717,9 +717,9 @@ Connecting RUM and traces may significantly increase the APM-ingested volumes. U
 
 ## Trace retention
 
-These traces are available for 15 minutes in the [Live Search][19] explorer. To retain the traces for a longer period of time, create [retention filters][20]. Scope these retention filters on any span tag to retain traces for critical pages and user actions.
+These traces are available for 15 minutes in the [Live Search][19] explorer. To retain the traces for a longer period of time, create [retention filters][20]. Scope these retention filters on any span tag to retain traces for critical pages and user actions. You can also use [cross-product retention filters][21] to optimize correlation between RUM sessions and APM traces. By default, [1% of RUM sessions and their traces are automatically retained][23] for 15 days at no additional cost. 
 
-## Further Reading
+## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
@@ -743,4 +743,6 @@ These traces are available for 15 minutes in the [Live Search][19] explorer. To
 [18]: https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
 [19]: /tracing/trace_explorer/#live-search-for-15-minutes
 [20]: /tracing/trace_pipeline/trace_retention/#retention-filters
-[21]: https://app.datadoghq.com/rum/explorer
+[21]: /real_user_monitoring/rum_without_limits/retention_filters/#cross-product-retention-filters
+[22]: https://app.datadoghq.com/rum/explorer
+[23]: /tracing/trace_pipeline/trace_retention/#one-percent-flat-sampling

content/en/real_user_monitoring/rum_without_limits/retention_filters.md

@@ -111,18 +111,18 @@ For example, to exclude sessions from South Korea while retaining all other sess
 
 ## Cross-product retention filters
 
+{{< callout url=
+ btn_hidden="false" header="Join the Preview!">}}
+Cross-Product Retention Filters are in Preview. Use this form to submit your request today.
+{{< /callout >}}
+
 When configuring a RUM retention filter, you can enable two cross-product retention filters: one for session replays and one for APM traces.
 
 - **Session Replay filter**: Retains replays for the specified percentage of sessions retained by the parent RUM retention filter which have an available replay.
 - **APM traces filter**: Indexes APM traces for the specified percentage of sessions retained by the parent RUM retention filter which have available traces.
+  <div class="alert alert-warning">The APM traces filter is only compatible with the following versions of the SDKs (applies to RUM and APM, but not Session Replay): <br> - Browser 6.5.0+ <br> - Android 3.0.0+ <br> - React Native 3.0.0+ <br></div>
 
-**Notes**:
-- The availability of a session replay or APM traces depends on the initialization parameters `sessionReplaySampleRate` and `traceSampleRate` of the SDK.
-- The APM traces filter is only compatible with the following versions of the SDKs:
-
-- Browser 6.5.0+
-- Android 3.0.0+
-- React Native 3.0.0+
+**Note**: The availability of a session replay or APM traces depends on the initialization parameters `sessionReplaySampleRate` and `traceSampleRate` of the SDK. 
 
 ### Default 1% retention