-
Notifications
You must be signed in to change notification settings - Fork 357
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d8b134f
commit 8bac408
Showing
20 changed files
with
157 additions
and
157 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,7 +4,7 @@ id: cODRw1GgIP | |
--- | ||
{% include content/source-region-unsupported.md %} | ||
|
||
[LaunchDarkly](https://launchdarkly.com) is a feature management platform that empowers development teams to safely deliver and control software through feature flags. | ||
[LaunchDarkly](https://launchdarkly.com){:target="_blank"} is a feature management platform that empowers development teams to safely deliver and control software through feature flags. | ||
|
||
This source is maintained by LaunchDarkly. For any issues with the source, [contact the LaunchDarkly Support team](mailto:[email protected]). | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,12 +6,12 @@ beta: true | |
|
||
[Paytronix](https://support-paytronix.force.com/help/s/article/000001348){:target="_blank”} is the leading provider of Digital Customer Engagement Solutions for restaurants, convenience stores, and retailers who seek to develop lasting relationships with their guests. For over 20 years, Paytronix has grown its Guest Engagement Platform to seamlessly incorporate individual components of digital customer engagement into a single, robust platform. | ||
|
||
This is an [Event Cloud Source](https://segment.com/docs/sources/#event-cloud-sources){:target="_blank”} which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations. | ||
This is an [Event Cloud Source](docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations. | ||
|
||
This source is maintained by Paytronix. For any issues with the source, [contact the Paytronix Support team](mailto:[email protected]){:target="_blank”}. | ||
This source is maintained by Paytronix. For any issues with the source, [contact the Paytronix Support team](mailto:[email protected]). | ||
|
||
> info "" | ||
> The Paytronix Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on January 27, 2023. If you are interested in joining their beta program or have any feedback to help improve the Paytronix Source and its documentation, [let the Paytronix team know](mailto:[email protected]){:target="blank"}. | ||
> The Paytronix Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on January 27, 2023. If you are interested in joining their beta program or have any feedback to help improve the Paytronix Source and its documentation, [let the Paytronix team know](mailto:[email protected]). | ||
## Getting started | ||
|
||
|
@@ -67,6 +67,6 @@ The table below list the properties included in the events listed above. | |
|
||
Now that your Source is set up, you can connect it with Destinations. | ||
|
||
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](https://segment.com/docs/connections/event-delivery/){:target="_blank”} tool, and refer to the Destination docs for each tool for troubleshooting. | ||
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](/docs/connections/event-delivery/){:target="_blank”} tool, and refer to the Destination docs for each tool for troubleshooting. | ||
|
||
If there are any issues with how the events are arriving to Segment, [contact the Paytronix support team](mailto:[email protected]){:target="_blank”}. | ||
If there are any issues with how the events are arriving to Segment, [contact the Paytronix support team](mailto:[email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,7 +4,7 @@ id: lWnQVj7Zo4 | |
--- | ||
{% include content/source-region-unsupported.md %} | ||
|
||
[Pendo](https://pendo.io) is a product cloud that helps product teams deliver software users love. With Pendo, product teams can understand product usage, collect feedback, measure NPS, onboard users, and announce new features in app—all without requiring engineering resources. | ||
[Pendo](https://pendo.io){:target="_blank”} is a product cloud that helps product teams deliver software users love. With Pendo, product teams can understand product usage, collect feedback, measure NPS, onboard users, and announce new features in app—all without requiring engineering resources. | ||
|
||
This source is maintained by Pendo. For any issues with the source, [contact the Pendo Support team](mailto:[email protected]). | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ beta: true | |
|
||
[Qualtrics](https://qualtrics.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is an Experience Management platform that allows companies to design and improve customer and employee experiences through listening, analysis, and action. | ||
|
||
This is an [Event Cloud Source](https://segment.com/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations. | ||
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations. | ||
|
||
Qualtrics maintains this source. For any issues with the source, [contact the Qualtrics Support team](mailto:[email protected]). | ||
|
||
|
@@ -14,7 +14,7 @@ Qualtrics maintains this source. For any issues with the source, [contact the Qu | |
## Getting started | ||
|
||
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog) click **Add Source**. | ||
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”} click **Add Source**. | ||
2. Search for "Qualtrics" in the Sources Catalog, select Qualtrics, and click **Add Source**. | ||
3. On the next screen, give the Source a nickname configure any other settings. | ||
- The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, SourceName_Prod, SourceName_Staging, or SourceName_Dev). | ||
|
@@ -44,7 +44,7 @@ The Qualtrics integration allows you to define event properties within the follo | |
|
||
Now that your Source is set up, you can connect it with Destinations. | ||
|
||
Log into your downstream tools and verify that events and properties appear the way you expect. If events and properties don’t appear as you expect them to, check the [Event Delivery](https://segment.com/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting. | ||
Log into your downstream tools and verify that events and properties appear the way you expect. If events and properties don’t appear as you expect them to, check the [Event Delivery](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting. | ||
|
||
If there are any issues with how the events are arriving to Segment, [contact the Qualtrics support team](mailto:[email protected]). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,7 +12,7 @@ This source allows you to enrich user profiles with survey responses and use the | |
This source is maintained by Refiner. For any issues with the source, [contact Refiner Support](mailto:[email protected]). | ||
|
||
> success "" | ||
> **Good to know**: This page is about the Refiner Segment source, which sends data _into_ Segment. There's also a page about the [Refiner Segment destination](https://segment.com/docs/connections/destinations/catalog/refiner/), which receives data from Segment! | ||
> **Good to know**: This page is about the Refiner Segment source, which sends data _into_ Segment. There's also a page about the [Refiner Segment destination](/docs/connections/destinations/catalog/refiner/), which receives data from Segment! | ||
## Getting Started | ||
|
||
|
@@ -72,6 +72,6 @@ A `group` call issued by Refiner could look like this: | |
|
||
Now that your Source is set up, you can connect it with Destinations. | ||
|
||
Log into your downstream tools and check to see that your events are appearing as expected, and that they contain all of the properties you expect. If your events and properties don't appear, check the [Event Delivery](https://segment.com/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting. | ||
Log into your downstream tools and check to see that your events are appearing as expected, and that they contain all of the properties you expect. If your events and properties don't appear, check the [Event Delivery](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting. | ||
|
||
If you see any issues with how the events are arriving to Segment, [contact the Refiner support team](mailto:[email protected]). |
Oops, something went wrong.