Remove Segment extension from docs

content/concepts/broadcasts.mdx

@@ -128,7 +128,7 @@ Additionally, developer tools and extensions are available for broadcasts as the
 
 - [Outbound webhooks](/developer-tools/outbound-webhooks/overview): all messages produced by a broadcast will emit outbound webhook events.
 - [Observability extensions](/integrations/extensions/overview): all processing metrics produced by a broadcast will be sent to the observability tools you have configured (Datadog and New Relic).
-- [CDP and analytics extensions](/integrations/extensions/overview): all message events produced by a broadcast will be sent to the CDP and analytics tools you have configured (Segment and Heap).
+- [Analytics extensions](/integrations/extensions/overview): all message events produced by a broadcast will be sent to the analytics tools you have configured (such as [Heap](/integrations/extensions/heap)).
 - [Data warehouse sync](/integrations/extensions/data-sync): all messages produced by a broadcast will be visible within your Knock `messages` table.
 
 ## Broadcasts and user preferences

content/in-app-ui/guides/handling-engagement.mdx

@@ -5,7 +5,7 @@ tags: ["guides", "rendering", "lifecycle", "marketing", "tours"]
 section: Building in-app UI > Guides
 ---
 
-Guides produce [messages](/concepts/messages) that capture the content rendered to the user and the engagement of the user with the guide, just like workflows and broadcasts within Knock. This means guide messages will appear in messages tables synced to your data warehouse and in downstream events sent to Segment and Heap.
+Guides produce [messages](/concepts/messages) that capture the content rendered to the user and the engagement of the user with the guide, just like workflows and broadcasts within Knock. This means guide messages will appear in messages tables synced to your data warehouse and in downstream events sent to analytics tools like [Heap](/integrations/extensions/heap).
 
 ## When is a guide message created?
 

content/integrations/extensions/overview.md

@@ -9,7 +9,6 @@ Knock integrates with popular third-party platforms, enabling new functionality
 
 - [Slack](/integrations/extensions/slack)
 - [Data warehouse sync](/integrations/extensions/data-sync)
-- [Segment](/integrations/extensions/segment)
 - [Datadog](/integrations/extensions/datadog)
 - [New Relic](/integrations/extensions/new-relic)
 - [Heap](/integrations/extensions/heap)

content/integrations/overview.mdx

@@ -60,7 +60,7 @@ See the [sources overview](/integrations/sources/overview) for configuration det
 Knock can also integrate with other tools for debugging, monitoring, and more, including the following:
 
 - [Datadog](/integrations/extensions/datadog)/[New Relic](/integrations/extensions/new-relic). Receive Knock platform metrics for workflow & channel successes and errors.
-- [Segment](/integrations/extensions/segment)/[Heap](/integrations/extensions/heap). Send Knock notification events to downstream analytics tools.
+- [Heap](/integrations/extensions/heap). Send Knock notification events to downstream analytics tools.
 - [Vercel](/integrations/extensions/vercel). Synchronize your Knock API keys to one or more Vercel projects.
 
 ## Per environment configurations

data/sidebars/integrationsSidebar.ts

@@ -164,7 +164,6 @@ export const INTEGRATIONS_SIDEBAR: SidebarContent[] = [
       { slug: "/overview", title: "Overview" },
       { slug: "/slack", title: "Slack" },
       { slug: "/data-sync", title: "Data warehouse sync" },
-      { slug: "/segment", title: "Segment" },
       { slug: "/datadog", title: "Datadog" },
       { slug: "/new-relic", title: "New Relic" },
       { slug: "/heap", title: "Heap" },