Strikedeck no longer exists

src/connections/destinations/catalog/strikedeck/index.md

@@ -3,22 +3,21 @@ rewrite: true
 title: Strikedeck Destination
 id: 5c940e99e3498f000177880c
 ---
-[Strikedeck](https://strikedeck.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a Customer Success platform which actively manages customer relationships to reduce churn, increase existing revenue and influence new sales. Strikedeck includes  Customer Engagement Analytics, Health Scorecard, Notifications, Recommendations & Actions.
 
-Strikedeck maintains this documentation. For any issues with the destination, [contact the Strikedeck Support team](mailto:[email protected]).
-
-
-## Getting Started
+> warning ""
+> **Strikedeck has been discontinued. This documentation is retained for reference only.**
 
+Strikedeck is a customer success platform which manages customer relationships to reduce churn, increase existing revenue and influence new sales. Strikedeck includes customer engagement analytics, health scorecard, notifications, and recommendations and actions.
 
+## Getting started
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Strikedeck" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "API Key" into your Segment Settings UI which you can find from your Strikedeck settings page. Go to Settings -> Connector and click on "Segment". Copy the API Key from this page.
+3. Enter the "API Key" into your Segment Settings UI, which you can find from your Strikedeck settings page. Go to **Settings > Connector** and click on "Segment". Copy the API Key from this page.
 
 ## Page
 
-For more information about the Page method, see the [Segment Specs - Page](/docs/connections/spec/page/) documentation.
+For more information about the Page method, see the [Segment Spec - Page](/docs/connections/spec/page/) documentation.
 
 An example Page call looks like:
 
@@ -28,9 +27,9 @@ analytics.page()
 
 Segment sends Page calls to Strikedeck as a `pageview`.
 
-
 ## Screen
-For more information about the Screen method, see the [Segment Specs - Screen](/docs/connections/spec/screen/) documentation.
+
+For more information about the Screen method, see the [Segment Spec - Screen](/docs/connections/spec/screen/) documentation.
 
 An example Screen call looks like:
 
@@ -42,7 +41,7 @@ Segment sends Screen calls to Strikedeck as a `screenview`.
 
 
 ## Identify
-For more information about the Screen method, see the [Segment Specs - Screen](/docs/connections/spec/identify/) documentation.
+For more information about the Screen method, see the [Segment Spec - Screen](/docs/connections/spec/identify/) documentation.
 
 An example Identify call looks like:
 
@@ -54,10 +53,9 @@ analytics.identify('userId123', {
 
 Segment sends Identify to Strikedeck as an `identify` event.
 
-
 ## Group
 
-For more information about the Screen method, see the [Segment Specs - Screen](/docs/connections/spec/group/) documentation.
+For more information about the Screen method, see the [Segment Spec - Screen](/docs/connections/spec/group/) documentation.
 
 An example Group call looks like:
 
@@ -69,10 +67,9 @@ analytics.group( {
 
 Segment sends Group to Strikedeck as a `group` event.
 
-
 ## Track
 
-For more information about the Screen method, see the [Segment Specs - Screen](/docs/connections/spec/track/) documentation.
+For more information about the Screen method, see the [Segment Spec - Screen](/docs/connections/spec/track/) documentation.
 
 An example Track call looks like: