Skip to content

Commit cb65bbc

Browse files
committed
rename folder to match slug in the app, remove template comments
1 parent 29c8485 commit cb65bbc

File tree

1 file changed

+5
-16
lines changed
  • src/connections/destinations/catalog/actions-hyperengage

1 file changed

+5
-16
lines changed
Lines changed: 5 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,14 @@
11
---
2-
# Hyperengage Destination
3-
title: Hyperengage Destination
2+
title: Hyperengage (Actions) Destination
43
hide-boilerplate: true
54
hide-dossier: true
5+
beta: true
6+
private: true
7+
id: 651c1db19de92d8e595ff55d
68
---
79

8-
<!-- This template is meant for Actions-based destinations that do not have an existing Classic or non-Actions-based version. For Actions Destinations that are a new version of a classic destination, see the doc-template-update.md template. -->
9-
1010
{% include content/plan-grid.md name="actions" %}
1111

12-
<!-- Include a brief description of the destination here, along with a link to your website. -->
13-
<!-- In the section below, explain the value of this actions-based destination. If you don't have a classic version of the destination, remove this section. -->
1412
[Hyperengage](https://hyperengage.io/){:target="_blank"} tracks thousands of data points to trigger smart alerts on hidden opportunities when the accounts are ready for upsell, or likely to churn. By integrating product data into your GTM strategy, our platform empowers CSM’s and AE’s to achieve up to 5x higher lead conversion and better retention and adoption.
1513

1614
## Benefits of Hyperengage (Actions)
@@ -22,8 +20,6 @@ Hyperengage (Actions) offers several advantages:
2220
- **Direct Data Transfer**: Data moves straight from Segment to Hyperengage, eliminating the need for third-party intermediaries.
2321
- **Event Tracking and User Identification**: With Segment's Actions-based destination, you can keep track of events and identify users and organizations in Hyperengage.
2422

25-
<!-- The section below describes how to activate and set up the destination. Include any additional configuration steps not mentioned. For example, acquiring an API key from your system and any setup steps needed to establish a connection to the destination. -->
26-
2723
## Getting Started
2824

2925
1. Navigate to the Segment web app and select **Catalog**, then pick **Destinations**.
@@ -34,12 +30,5 @@ Hyperengage (Actions) offers several advantages:
3430
6. Open the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the API Key and Workspace Identifier.
3531
7. Open the Segment app, navigate to your Hyperengage (Actions) destination, and paste the API Key and Workspace Identifier into the destination's settings page.
3632

37-
<!-- The line below will render a table of connection settings (if they exist), Pre-built Mappings, and potential actions. -->
38-
39-
{% include components/actions-fields.html %}
40-
41-
<!--
42-
Additional Context
4333

44-
Include additional information that you think will be useful to the user here. For information that is specific to an individual mapping, please add that as a comment so that the Segment docs team can include it in the auto-generated content for that mapping.
45-
-->
34+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)