paytronix > end

Author: forstisabella

src/connections/sources/catalog/cloud-apps/launchdarkly/index.md

@@ -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]).
 

src/connections/sources/catalog/cloud-apps/paytronix/index.md

@@ -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]).

src/connections/sources/catalog/cloud-apps/pendo/index.md

@@ -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]).
 

src/connections/sources/catalog/cloud-apps/provesource/index.md

@@ -17,7 +17,7 @@ This source is maintained by ProveSource. For any issues with the source, [conta
 1. From your Segment UI's Sources page click on "Add Source".
 2. Search for "ProveSource" within the Sources Catalog and confirm by clicking "Connect".
 3. Give the Source a nickname and follow the set up flow to "Add Source". The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
-4. Copy the Write key from the Segment UI and log in to your ProveSource account - navigate to [Settings](https://console.provesrc.com/#/settings) > Integrations > Click Edit next to Segment Integration and paste the key to connect.
+4. Copy the Write key from the Segment UI and log in to your ProveSource account - navigate to [Settings](https://console.provesrc.com/#/settings){:target="_blank”} > Integrations > Click Edit next to Segment Integration and paste the key to connect.
 
 
 ## Events

src/connections/sources/catalog/cloud-apps/qualtrics/index.md

@@ -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]).
 

src/connections/sources/catalog/cloud-apps/radar/index.md

@@ -4,19 +4,19 @@ id: bnpfpwKnhu
 ---
 {% include content/source-region-unsupported.md %}
 
-[Radar](https://radar.com) is the leading geofencing and location tracking platform. You can use Radar SDKs and APIs to build a wide range of location-based product and service experiences, including pickup and delivery tracking, location-triggered notifications, location verification, store locators, address autocomplete, and more.
+[Radar](https://radar.com){:target="_blank”} is the leading geofencing and location tracking platform. You can use Radar SDKs and APIs to build a wide range of location-based product and service experiences, including pickup and delivery tracking, location-triggered notifications, location verification, store locators, address autocomplete, and more.
 
 The Radar Segment Source is a Cloud-mode event source. Instead of packaging Radar's SDK using Segment as a wrapper, you include, configure, and initialize their SDK separately. Radar then sends all events that it detects and infers to Segment using its servers. As a result, only destinations that allow Cloud-mode are compatible with the Radar source.
 
 The Radar platform has three products: *Geofencing and Place Detection*, *Trip Tracking*, and *APIs for Geocoding and Search*.
 
-- **[Geofencing and Place Detection](https://radar.com/product/geofencing)**: Radar geofencing is more powerful than native iOS or Android geofencing, with cross-platform support for unlimited geofences, polygon and isochrone geofences, stop detection, and accuracy down to 10 meters. Radar's Places feature allows you to instantly configure geofencing around thousands of chains (i.e.: Starbucks, Walmart) and categories (i.e.: airports, restaurants) with the click of a button. Radar will generate a real time event on entry or exit of a custom or Places geofence to trigger messaging, drive behavioral insights, inform audience segmentation, and more.
+- **[Geofencing and Place Detection](https://radar.com/product/geofencing){:target="_blank”}**: Radar geofencing is more powerful than native iOS or Android geofencing, with cross-platform support for unlimited geofences, polygon and isochrone geofences, stop detection, and accuracy down to 10 meters. Radar's Places feature allows you to instantly configure geofencing around thousands of chains (i.e.: Starbucks, Walmart) and categories (i.e.: airports, restaurants) with the click of a button. Radar will generate a real time event on entry or exit of a custom or Places geofence to trigger messaging, drive behavioral insights, inform audience segmentation, and more.
 
-- **[Trip Tracking](https://radar.com/product/trip-tracking)**: Radar has a powerful trip tracking product that allows a brand to personalize the pickup and delivery experience for brick and mortar brands and logistics use cases.
+- **[Trip Tracking](https://radar.com/product/trip-tracking){:target="_blank”}**: Radar has a powerful trip tracking product that allows a brand to personalize the pickup and delivery experience for brick and mortar brands and logistics use cases.
   - **Curbside Pickup and BOPIS** - When a user places an order for pickup, offer them the option to share location to reduce wait times and, for restaurants, increase food freshness. Radar will track the user's location while en route, provide staff with a real time ETA, and produce an arrival event which can trigger an Iterable notification to the user and/or staff. These features optimize operation efficiencies at the store and lead to a much stronger customer experience.
   - **Delivery and Fleet Tracking** - Track your in-house delivery team using a driver app to be able to send ETA updates and real time arrival notifications to the end user who is expecting the delivery.
 
-- **[Search and Geocoding APIs](https://radar.com/product/api)**: Import and search your own location data, or tap into Radar's best-in-class address and POI datasets. Use these APIs to power store finders, address autocomplete, forward and reverse geocoding, IP geocoding, and more.
+- **[Search and Geocoding APIs](https://radar.com/product/api){:target="_blank”}**: Import and search your own location data, or tap into Radar's best-in-class address and POI datasets. Use these APIs to power store finders, address autocomplete, forward and reverse geocoding, IP geocoding, and more.
 
 When you enable Radar as a Segment Source, you can forward Geofences, Places, Regions, and Trip Tracking data to your warehouse or destinations.
 
@@ -30,23 +30,23 @@ Radar will send the following events to your Segment warehouses and destinations
 
 <!-- TODO: Update the Region Entered/Exited with new links, when availible -->
 
-- [Geofence Entered](https://radar.com/documentation/integrations/segment#geofence-entered)
-- [Geofence Exited](https://radar.com/documentation/integrations/segment#geofence-exited)
-- [Place Entered](https://radar.com/documentation/integrations/segment#place-entered)
-- [Place Exited](https://radar.com/documentation/integrations/segment#place-exited)
-- [Region Entered](https://radar.com/documentation/integrations/segment#country-entered)
-- [Region Exited](https://radar.com/documentation/integrations/segment#country-exited)
-- [Trip Started](https://radar.com/documentation/integrations/segment#trip-started)
-- [Trip Updated](https://radar.com/documentation/integrations/segment#trip-updated)
-- [Trip Approaching Destination](https://radar.com/documentation/integrations/segment#trip-approaching-destination)
-- [Trip Arrived Destination](https://radar.com/documentation/integrations/segment#trip-arrived-destination)
-- [Trip Stopped](https://radar.com/documentation/integrations/segment#trip-stopped)
+- [Geofence Entered](https://radar.com/documentation/integrations/segment#geofence-entered){:target="_blank”}
+- [Geofence Exited](https://radar.com/documentation/integrations/segment#geofence-exited){:target="_blank”}
+- [Place Entered](https://radar.com/documentation/integrations/segment#place-entered){:target="_blank”}
+- [Place Exited](https://radar.com/documentation/integrations/segment#place-exited){:target="_blank”}
+- [Region Entered](https://radar.com/documentation/integrations/segment#country-entered){:target="_blank”}
+- [Region Exited](https://radar.com/documentation/integrations/segment#country-exited){:target="_blank”}
+- [Trip Started](https://radar.com/documentation/integrations/segment#trip-started){:target="_blank”}
+- [Trip Updated](https://radar.com/documentation/integrations/segment#trip-updated){:target="_blank”}
+- [Trip Approaching Destination](https://radar.com/documentation/integrations/segment#trip-approaching-destination){:target="_blank”}
+- [Trip Arrived Destination](https://radar.com/documentation/integrations/segment#trip-arrived-destination){:target="_blank”}
+- [Trip Stopped](https://radar.com/documentation/integrations/segment#trip-stopped){:target="_blank”}
 
-For a complete view of the events that Radar passes into Segment, visit [Radar's Segment Events Mapping documentation](https://radar.com/documentation/integrations/segment#event-mapping).
+For a complete view of the events that Radar passes into Segment, visit [Radar's Segment Events Mapping documentation](https://radar.com/documentation/integrations/segment#event-mapping){:target="_blank”}.
 
 ## Radar User Traits
 
-Radar will also send the following user traits to Segment, depending on Radar user state when Radar events are sent to Segment. For a complete view of the user attributes that Radar passes into Segment, visit [Radar's Segment User Mapping documentation](https://radar.com/documentation/integrations/segment#user-mapping)
+Radar will also send the following user traits to Segment, depending on Radar user state when Radar events are sent to Segment. For a complete view of the user attributes that Radar passes into Segment, visit [Radar's Segment User Mapping documentation](https://radar.com/documentation/integrations/segment#user-mapping){:target="_blank”}.
 
 <table>
   <tr>
@@ -112,17 +112,17 @@ Radar will also send the following user traits to Segment, depending on Radar us
   <tr>
     <td>radar_place_categories</td>
     <td>array <string></td>
-    <td>List of the [categories of the place](https://www.radar.com/documentation/places/categories).</td>
+    <td>List of the [categories of the place](https://www.radar.com/documentation/places/categories){:target="_blank”}.</td>
   </tr>
   <tr>
     <td>radar_place_chain_name</td>
     <td>string</td>
-    <td>The name of the [chain of the user's last known place](https://www.radar.com/documentation/places/chains).</td>
+    <td>The name of the [chain of the user's last known place](https://www.radar.com/documentation/places/chains){:target="_blank”}.</td>
   </tr>
   <tr>
     <td>radar_place_chain_slug</td>
     <td>string</td>
-    <td>A human-readable unique ID for the [chain of the user's last known place](https://www.radar.com/documentation/places/chains).</td>
+    <td>A human-readable unique ID for the [chain of the user's last known place](https://www.radar.com/documentation/places/chains){:target="_blank”}.</td>
   </tr>
   <tr>
     <td>radar_insights_state_home</td>

src/connections/sources/catalog/cloud-apps/refiner/index.md

@@ -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]).