diff --git a/content/concepts/broadcasts.mdx b/content/concepts/broadcasts.mdx index 9390168b4..a859abaab 100644 --- a/content/concepts/broadcasts.mdx +++ b/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 diff --git a/content/in-app-ui/guides/handling-engagement.mdx b/content/in-app-ui/guides/handling-engagement.mdx index e29147e73..029523a42 100644 --- a/content/in-app-ui/guides/handling-engagement.mdx +++ b/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? diff --git a/content/integrations/extensions/overview.md b/content/integrations/extensions/overview.md index 8e897111c..b693c2fbe 100644 --- a/content/integrations/extensions/overview.md +++ b/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) diff --git a/content/integrations/extensions/segment.mdx b/content/integrations/extensions/segment.mdx deleted file mode 100644 index d0745373a..000000000 --- a/content/integrations/extensions/segment.mdx +++ /dev/null @@ -1,137 +0,0 @@ ---- -title: How to send Knock data to Segment -description: Learn more about how to connect Knock with your Segment account. -layout: integrations -tags: ["segment", "extensions", "analytics"] -section: Integrations > Extensions ---- - -This documentation covers how to use our Segment extension to send Knock's normalized notification data into [Segment](https://segment.io) to forward on to your data warehouse or other tools where you run data analysis, such as Amplitude or Mixpanel. - -Once the extension is enabled, Knock automatically passes a stream of `track` events to Segment (e.g. `Notification delivered`, `Notification seen`, `Notification read`) which you can then use in your downstream tools. - -Knock also provides a separate integration for using Segment as a [Knock source](/integrations/sources/overview) to bring `track` and `identify` event data from Segment into Knock to power your notifications. You can learn more in our [Segment source docs](/integrations/sources/segment). - - - The Knock Segment extension is only available on our{" "} - - Enterprise plan - - . - - } -/> - -## Getting started - -Knock uses the Segment HTTP Source to send events to your Segment account. Each HTTP Source has a Write Key associated with it that Knock can use to push events into Segment. A best practice is to create a separate Segment HTTP Source for each Knock environment from which you plan to collect events. - -1. Create a new Segment HTTP Source in your Segment Account for each Knock environment from which you plan to collect events - 1. Log into Segment, click **Connections** > **Sources**, and then choose "Add Source" - 2. Find the "HTTP API" source and click "Add Source" - 3. Give it a useful name, e.g. "Knock Production" - 4. Make note of the write key - 5. Repeat these steps for each Knock environment you need to configure -2. Visit the **Extensions** page under the **Integrations** section of your Knock dashboard account settings -3. Find the Segment extension and click "Connect" -4. In the modal that appears, enter the write key for each environment you want to configure. Leave the field blank to disable writing events from that environment -5. Once you click save, events will begin flowing from that environment to Segment - -Segment extension configuration example - -## Events sent to Segment - -When connected, Knock will forward the following `track` events to Segment. - - - -## Event schema - -Knock uses the Segment Track spec for the event data we pass to Segment. You can find an example payload of what you can expect from Knock events coming into Segment below. - -```json title="example Segment Track event payload" -{ - "context": { - "library": { - "name": "unknown", - "version": "unknown" - } - }, - "event": "Notification Seen", - "integrations": {}, - "messageID": "2XoNHQx7lPp0zsCtZh3BGgCJxxx", - "messageId": "api-2ZjG9Ho7EeqVV9uqkdlSRYbDxxx", - "originalTimestamp": "2023-12-18T19:31:58.653982Z", - "properties": { - "channelId": "26d3f6ad-eebc-4ce4-9125-bb856dad8xxx", - "channelType": "in_app_feed", - "environment": "Production", - "messageId": "2XoNHQx7lPp0zsCtZh3BGgCJxxx", - "provider": "in_app_feed_knock", - "stepRef": "YJAxjVC-ya69fBhoSFxxx", - "workflowKey": "account-invite-accepted" - }, - "receivedAt": "2023-12-18T19:32:01.326Z", - "sentAt": null, - "timestamp": "2023-12-18T19:31:58.653Z", - "type": "track", - "userId": "70171a84-7e52-46d7-8866-5b4ab88cxxx", - "writeKey": "REDACTED" -} -``` diff --git a/content/integrations/overview.mdx b/content/integrations/overview.mdx index 3bae9fe5d..6662202d1 100644 --- a/content/integrations/overview.mdx +++ b/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 diff --git a/data/sidebars/integrationsSidebar.ts b/data/sidebars/integrationsSidebar.ts index a0ca3580e..fbb0adadd 100644 --- a/data/sidebars/integrationsSidebar.ts +++ b/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" }, diff --git a/public/images/integrations/extensions/connect-segment-modal.png b/public/images/integrations/extensions/connect-segment-modal.png deleted file mode 100644 index 441646f3e..000000000 Binary files a/public/images/integrations/extensions/connect-segment-modal.png and /dev/null differ