-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Hyperengage Actions] - Added Documentation for New Destination #5539
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for docs team reviewer:
This Integration has 3 Actions, one to handle each of track(), identify() and group calls.
|
||
Hyperengage (Actions) offers several advantages: | ||
|
||
- **Seamless Data Mapping.** Hyperengage streamlines the process of syncing your user and account data. By linking your account, identify, track, and group calls with user or account data will be processed by Hyperengage, bypassing the need for manual API integrations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we reword the sentence starting with "By linking your account..." please? I feel that it could be better explained. We're only syncing Segment identify, track and group calls, not 'account' calls.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @joe-ayoub-segment ,
Thank you for your feedback, I've rephrased the sentence to sound less ambigious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a couple of changes and we'll be good to go 🚀
<!-- 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. --> | ||
[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. | ||
|
||
## Benefits of Hyperengage (Actions) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @tcgilbert - do we typically include this section if there is not a classic destination already available to folks? I'm not seeing it in the template!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not typically, but I see no problem in keeping htis in there
--- | ||
# Hyperengage Destination | ||
title: Hyperengage Destination | ||
hide-boilerplate: true | ||
hide-dossier: true | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This destination is in the catalog as Hyperengage (Actions), so I've updated the destination's name accordingly. I also added the private and beta tags to denote the current status of the destination. The destination ID is pulled from Segment's Public API - including it in the frontmatter like this allows us to programmatically build content on the site (for example, this destination will appear on the list of Actions destinations).
--- | |
# Hyperengage Destination | |
title: Hyperengage Destination | |
hide-boilerplate: true | |
hide-dossier: true | |
--- | |
--- | |
title: Hyperengage (Actions) Destination | |
hide-boilerplate: true | |
hide-dossier: true | |
private: true | |
beta: true | |
id: 651c1db19de92d8e595ff55d | |
--- |
|
||
Hyperengage (Actions) offers several advantages: | ||
|
||
- **Seamless Data Mapping.** Hyperengage streamlines the process of syncing your user and account data. When you link your data, Hyperengage will automatically process Segment's identify, track, and group calls, eliminating the necessity for manual API integrations." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **Seamless Data Mapping.** Hyperengage streamlines the process of syncing your user and account data. When you link your data, Hyperengage will automatically process Segment's identify, track, and group calls, eliminating the necessity for manual API integrations." | |
- **Seamless Data Mapping**: Hyperengage streamlines the process of syncing your user and account data. When you link your data with Segment, Hyperengage automatically processes Segment's Identify, Track, and Group calls, eliminating the need for manual API integrations. |
Hyperengage (Actions) offers several advantages: | ||
|
||
- **Seamless Data Mapping.** Hyperengage streamlines the process of syncing your user and account data. When you link your data, Hyperengage will automatically process Segment's identify, track, and group calls, eliminating the necessity for manual API integrations." | ||
- **Pre-configured Mapping.** We have prebuilt mappings tailored for Hyperengage with all the necessary parameters, reducing the need for manual customization. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **Pre-configured Mapping.** We have prebuilt mappings tailored for Hyperengage with all the necessary parameters, reducing the need for manual customization. | |
- **Pre-configured Mappings**: The Hyperengage (Actions) Destination has prebuilt mappings tailored for Hyperengage with all the necessary parameters, reducing the need for manual customization. |
|
||
- **Seamless Data Mapping.** Hyperengage streamlines the process of syncing your user and account data. When you link your data, Hyperengage will automatically process Segment's identify, track, and group calls, eliminating the necessity for manual API integrations." | ||
- **Pre-configured Mapping.** We have prebuilt mappings tailored for Hyperengage with all the necessary parameters, reducing the need for manual customization. | ||
- **Direct Data Transfer.** Data moves straight from Segment to Hyperengage, eliminating the need for third-party intermediaries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **Direct Data Transfer.** Data moves straight from Segment to Hyperengage, eliminating the need for third-party intermediaries. | |
- **Direct Data Transfer**: Data moves straight from Segment to Hyperengage, eliminating the need for third-party intermediaries. |
## Getting Started | ||
|
||
1. Navigate to the Segment web app and select **Catalog**, then pick **Destinations**. | ||
2. In the Destinations Catalog, search for "hyperengage" and choose the destination. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. In the Destinations Catalog, search for "hyperengage" and choose the destination. | |
2. In the Destinations Catalog, search for "Hyperengage" and select the Hyperengage (Actions) destination. |
|
||
1. Navigate to the Segment web app and select **Catalog**, then pick **Destinations**. | ||
2. In the Destinations Catalog, search for "hyperengage" and choose the destination. | ||
3. Opt for **Configure Hyperengage**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3. Opt for **Configure Hyperengage**. | |
3. Click **Add destination**. |
1. Navigate to the Segment web app and select **Catalog**, then pick **Destinations**. | ||
2. In the Destinations Catalog, search for "hyperengage" and choose the destination. | ||
3. Opt for **Configure Hyperengage**. | ||
4. Choose an existing Source to connect to Hyperengage (Actions). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Choose an existing Source to connect to Hyperengage (Actions). | |
4. Choose an existing Source to connect to Hyperengage (Actions) and click **Next**. | |
5. Enter a name for your destination and click **Create destination**. |
2. In the Destinations Catalog, search for "hyperengage" and choose the destination. | ||
3. Opt for **Configure Hyperengage**. | ||
4. Choose an existing Source to connect to Hyperengage (Actions). | ||
5. Access the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the **API Key** & **Workspace Identifier**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5. Access the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the **API Key** & **Workspace Identifier**. | |
6. Open the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the API Key and Workspace Identifier. |
3. Opt for **Configure Hyperengage**. | ||
4. Choose an existing Source to connect to Hyperengage (Actions). | ||
5. Access the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the **API Key** & **Workspace Identifier**. | ||
6. Paste the "API Key" & "Workspace Identifier" into the "Hyperengage (Actions)" destination settings within Segment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6. Paste the "API Key" & "Workspace Identifier" into the "Hyperengage (Actions)" destination settings within Segment. | |
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. |
@@ -0,0 +1,45 @@ | |||
--- | |||
# Hyperengage Destination | |||
title: Hyperengage Destination |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: Hyperengage Destination | |
title: Hyperengage (Actions) Destination |
# Hyperengage Destination | ||
title: Hyperengage Destination | ||
hide-boilerplate: true | ||
hide-dossier: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hide-dossier: true | |
hide-dossier: true | |
beta: true | |
private: true | |
id: 651c1db19de92d8e595ff55d |
hey @tcgilbert - can you take a look at this PR when you get a chance? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please remove template comments
hide-dossier: true | ||
--- | ||
|
||
<!-- 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. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- 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. --> |
|
||
{% include content/plan-grid.md name="actions" %} | ||
|
||
<!-- Include a brief description of the destination here, along with a link to your website. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- Include a brief description of the destination here, along with a link to your website. --> |
{% include content/plan-grid.md name="actions" %} | ||
|
||
<!-- Include a brief description of the destination here, along with a link to your website. --> | ||
<!-- 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. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- 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. --> |
- **Direct Data Transfer**: Data moves straight from Segment to Hyperengage, eliminating the need for third-party intermediaries. | ||
- **Event Tracking and User Identification**: With Segment's Actions-based destination, you can keep track of events and identify users and organizations in Hyperengage. | ||
|
||
<!-- 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. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- 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. --> |
6. Open the [Hyperengage App](https://hyperengage.io/){:target="_blank"}, proceed to **Integration Settings**, and copy the API Key and Workspace Identifier. | ||
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. | ||
|
||
<!-- The line below will render a table of connection settings (if they exist), Pre-built Mappings, and potential actions. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- The line below will render a table of connection settings (if they exist), Pre-built Mappings, and potential actions. --> |
<!-- | ||
Additional Context | ||
|
||
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. | ||
--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<!-- | |
Additional Context | |
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. | |
--> |
hi @zhadier39 - I'm not able to directly edit this branch due to protections on your branch. I've duplicated the contents of this PR in #5606 and we'll use that one to merge the docs into the site! |
Proposed changes
Added documentation for the Hyperengage Actions Destination.
Merge timing