diff --git a/docs/organization/integrations/feature-flag/launchdarkly/img/launchdarkly-ui.png b/docs/organization/integrations/feature-flag/launchdarkly/img/launchdarkly-ui.png
new file mode 100644
index 0000000000000..f4fa83482dbf5
Binary files /dev/null and b/docs/organization/integrations/feature-flag/launchdarkly/img/launchdarkly-ui.png differ
diff --git a/docs/organization/integrations/feature-flag/launchdarkly/index.mdx b/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
index a2c7bcc3aea94..ac233b51c195b 100644
--- a/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
+++ b/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
@@ -4,6 +4,8 @@ sidebar_order: 1
description: Learn about Sentry's LaunchDarkly integration. LaunchDarkly enables organizations to use Sentry errors as a metric in their LaunchDarkly experiments.
---
+## Metrics Integration
+
This integration is maintained and supported by the company that created it. For more details or questions, feel free to contact rrosefigura@launchdarkly.com.
## Install and Configure
@@ -23,3 +25,9 @@ The LaunchDarkly integration is only available to organizations with a Business
1. Navigate to **Settings > Integrations > LaunchDarkly**
2. Follow the full [LaunchDarkly installation instructions](https://docs.launchdarkly.com/integrations/sentry).
+
+## Change Tracking Integration
+
+Sentry offers a flag change tracking integration which allows Sentry to associate flag definition changes with errors that occurred in your application. To enable this integration, create a new "Generic Trigger" integration and paste the Sentry web hook URL generated by the Feature Flag Integration Modal. For information on how to generate a Sentry Web Hook URL, visit the feature flag integration documentation here. Learn more about LaunchDarkly's "Generic Triggers" here.
+
+
diff --git a/docs/product/issues/issue-details/img/feature-flags.png b/docs/product/issues/issue-details/img/feature-flags.png
deleted file mode 100644
index 4df355e3ea33b..0000000000000
Binary files a/docs/product/issues/issue-details/img/feature-flags.png and /dev/null differ
diff --git a/docs/product/issues/issue-details/img/suspect-flags-table.png b/docs/product/issues/issue-details/img/suspect-flags-table.png
deleted file mode 100644
index 33ed6541a691d..0000000000000
Binary files a/docs/product/issues/issue-details/img/suspect-flags-table.png and /dev/null differ
diff --git a/docs/product/issues/issue-details/img/suspect-flags-timeline.png b/docs/product/issues/issue-details/img/suspect-flags-timeline.png
deleted file mode 100644
index 3cfddd34a7b23..0000000000000
Binary files a/docs/product/issues/issue-details/img/suspect-flags-timeline.png and /dev/null differ
diff --git a/docs/product/issues/issue-details/index.mdx b/docs/product/issues/issue-details/index.mdx
index 7003b62afc365..d46e7ce18e797 100644
--- a/docs/product/issues/issue-details/index.mdx
+++ b/docs/product/issues/issue-details/index.mdx
@@ -102,6 +102,18 @@ If you’ve enabled [Session Replay](/product/explore/session-replay/), you’ll

+## Feature Flags
+There are two types of integrations you can configure to integrate feature flag data into your error events.
+
+The first integration type is **flag evaluation tracking** within the Sentry SDK. To enable it, update the Sentry SDK's `init` method to include one of our supported feature flag integrations. Support varies by language and by provider. Doing so will give you access to the feature flag table, which shows any flags that were evaluated after the Sentry SDK's initialization and before the error event occurred. You will see rows of (flag, evaluation-result) pairs. Supported integrations include:
+
+* LaunchDarkly ([Python](/platforms/python/integrations/launchdarkly/) and [JavaScript](/platforms/javascript/integrations/launchdarkly/))
+* OpenFeature ([Python](/platforms/python/integrations/openfeature/) and [JavaScript](/platforms/javascript/integrations/openfeature/))
+
+The second integration type is **feature flag change tracking**. This will enable a timeline of feature flag definition changes on the event and user volume chart. These annotations can help you diagnose when a feature flag change is related to a new issue. To enable this type of integration, please visit the documentation page of one of our supported providers:
+
+When both integrations are enabled, you'll see suspect feature flags highlighted in yellow in the feature flag table. Feature flags are marked as "suspect" if they're modified suspiciously close to the detection of a new issue.
+
## Breadcrumbs
