Skip to content

Commit

Permalink
first pass of external link fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
forstisabella committed Mar 20, 2024
1 parent 340091b commit c46e07f
Show file tree
Hide file tree
Showing 27 changed files with 48 additions and 41 deletions.
7 changes: 7 additions & 0 deletions ignore-links.txt
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,10 @@ https://segment.com/docs/connections/sources/catalog/cloud-apps/snowflake/
https://segment.com/docs/connections/destinations/catalog/adobe-target-cloud-mode/
https://segment.com/docs/connections/destinations/catalog/adobe-target-web/
https://segment.com/docs/connections/destinations/catalog/google-ads-remarketing-lists/
https://compose.aampe.com/configure/integrations
https://everboarding.trybento.co/data
https://app.getcorrelated.com/integrations
https://app.launchdarkly.com/default/production/debugger/goals
https://www.app.metricstory.ai/account/apikeys
https://app.unstack.com/login
https://github.com/fubotv/segment-analytics-android/pull/1
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ for this purpose.
> info ""
> By default, the _Track Calls_ mapping will filter and not send any events with the name `Experiment Viewed` to ABsmartly.
You can [install a custom event logger](https://docs.absmartly.com/docs/sdk%20documentation/getting-started/#using-a-custom-event-logger){:target="_blank"} in ABsmartly and send exposures directly to Segment.
You can [install a custom event logger](https://docs.absmartly.com/docs/SDK-Documentation/getting-started#using-a-custom-event-logger){:target="_blank"} in ABsmartly and send exposures directly to Segment.

```javascript
analytics.ready(function() {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This page contains best practices and tips for setting up and testing Adobe Anal

The following list contains tools you can use to validate data coming from Segment and going to each different Adobe Analytics component

- **Analytics.js** - [Adobe Experience Cloud Debugger](https://chrome.google.com/webstore/detail/adobe-experience-cloud-de/ocdmogmohccmeicdhlhhgepeaijenapj){:target="_blank”} and Chrome Developer Tools
- **Analytics.js** - [Adobe Experience Cloud Debugger](https://chromewebstore.google.com/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob){:target="_blank”} and Chrome Developer Tools
- **Other Segment server libraries** - Segment's in-app [Event Tester Tool](/docs/connections/test-connections/)
- **iOS Device mode** - Charles Proxy, DEBUG mode
- **Android Device Mode** - Charles Proxy, VERBOSE logging
Expand Down
12 changes: 6 additions & 6 deletions src/connections/destinations/catalog/braze/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Braze created a sample iOS application that integrates Braze using Segment. See
#### Device-mode set up for iOS 14 support
Braze updated the Braze iOS Segment SDK to 3.26.1 to prepare for iOS 14. As of version 3.27.0, Braze removed the `ABK_ENABLE_IDFA_COLLECTION` macro. To configure sending ISFA to Braze, see Braze's [Implementing IDFA Collection](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#ios-14-apptrackingtransparency){:target="_blank"}
Braze updated the Braze iOS Segment SDK to 3.26.1 to prepare for iOS 14. As of version 3.27.0, Braze removed the `ABK_ENABLE_IDFA_COLLECTION` macro. To configure sending ISFA to Braze, see Braze's [Implementing IDFA Collection](https://www.braze.com/docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations/){:target="_blank"}
documentation.

To use the latest Braze SDK to collect IDFAs you must do the following:
Expand All @@ -76,7 +76,7 @@ To use the latest Braze SDK to collect IDFAs you must do the following:
2. Update the Braze iOS Segment SDK to version 3.3.0 or greater.
3. Import and add the AppTrackingTransparency (ATT) Framework.
- Navigate to your project `Info.plist` and add a “Privacy - Tracking Usage Description”. This description appears in a popup when the application initializes in iOS 14. Applications prompt users to select if they want to allow tracking.
4. Add Braze's `ABKIDFADelegate`. For more information on how to add this see [Braze's IDFA Collection documentation](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#implementing-idfa-collection){:target="_blank"}
4. Add Braze's `ABKIDFADelegate`. For more information on how to add this see [Braze's IDFA Collection documentation](https://www.braze.com/docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations#implementing-idfa-collectionn){:target="_blank"}
.
5. Follow [Segment's guide for collecting IDFA](/docs/connections/sources/catalog/libraries/mobile/ios/#idfa-collection-in-40-beta-and-later)

Expand Down Expand Up @@ -122,7 +122,7 @@ Segment sends Page calls to Braze as custom events if you have enabled either **

> info "Tip"
> Add Segment's open-source [Middleware](https://github.com/segmentio/segment-braze-mobile-middleware){:target="_blank"}
tool to optimize your integration. This tool limits [Data Point](https://www.braze.com/docs/user_guide/onboarding_with_braze/data_points/){:target="_blank"} use by debouncing duplicate identify() calls from Segment. For more information, see the project's [README](https://github.com/segmentio/segment-braze-mobile-middleware/blob/master/README.md#how-does-this-work){:target="_blank"}.
tool to optimize your integration. This tool limits [Data Point](https://www.braze.com/docs/user_guide/data_and_analytics/data_points/){:target="_blank"} use by debouncing duplicate identify() calls from Segment. For more information, see the project's [README](https://github.com/segmentio/segment-braze-mobile-middleware/blob/master/README.md#how-does-this-work){:target="_blank"}.

If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
Expand Down Expand Up @@ -193,7 +193,7 @@ Segment sends all other traits (except Braze's [reserved user profile fields](ht
## Track
> info "Tip"
> To lower [Data Point](https://www.braze.com/docs/user_guide/onboarding_with_braze/data_points/){:target="_blank"} use, limit the events you send to Braze to those that are relevant for campaigns and segmentation to the Braze destination. For more information, see [Schema Controls](/docs/protocols/schema/).
> To lower [Data Point](https://www.braze.com/docs/user_guide/data_and_analytics/data_points/){:target="_blank"} use, limit the events you send to Braze to those that are relevant for campaigns and segmentation to the Braze destination. For more information, see [Schema Controls](/docs/protocols/schema/).
If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call looks like:

Expand Down Expand Up @@ -325,7 +325,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt
[[SEGAppboyIntegrationFactory instance] saveRemoteNotification:userInfo];
}
```
6. If you are using the `UserNotification` framework, follow [Braze's documentation](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/push_notifications/integration/#using-usernotification-framework-ios-10){:target="_blank"} to register push notifications using the `UserNotification` framework. Then in your application's `userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler` method, add the following:
6. If you are using the `UserNotification` framework, follow [Braze's documentation](https://www.braze.com/docs/developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/integration#using-usernotification-framework-ios-10){:target="_blank"} to register push notifications using the `UserNotification` framework. Then in your application's `userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler` method, add the following:
```objc
if ([Appboy sharedInstance] == nil) {
Expand Down Expand Up @@ -624,4 +624,4 @@ No. Audiences are sent to Braze as either custom attributes or custom events. Yo
All Braze user profile data (including custom events, custom attributes) is stored for as long as those profiles are active.
#### What happens if I delete a computed trait or audience in Segment?
When you delete an audience or trait in Segment they are not deleted from Braze. Data sent to Braze is immutable and cannot be deleted or modified once they receive it. However, you can [blocklist](https://www.braze.com/docs/user_guide/administrative/app_settings/manage_app_group/custom_event_and_attribute_management/#blacklisting-custom-attributes-custom-events-and-products){:target="_blank"} custom attributes and events in Braze.
When you delete an audience or trait in Segment they are not deleted from Braze. Data sent to Braze is immutable and cannot be deleted or modified once they receive it. However, you can [blocklist](https://www.braze.com/docs/user_guide/data_and_analytics/custom_data/managing_custom_data#blocklisting-custom-data){:target="_blank"} custom attributes and events in Braze.
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/courier/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Segment Track events are inbound events that might trigger a notification when C

All Inbound Events coming from Segment Track calls appear with a `Segment-TrackEvent` prefix in Courier to help distinguish them from other inbound events.

Courier extracts data from the Segment Track `properties` object, and conditionally triggers a request to the [Courier Send API](https://www.courier.com/docs/reference/send/message/){:target="_blank”} - only if that event is already [mapped](https://help.courier.com/en/articles/4202416-how-to-create-and-map-event-triggers-for-your-notifications){:target="_blank”}.
Courier extracts data from the Segment Track `properties` object, and conditionally triggers a request to the [Courier Send API](https://www.courier.com/docs/reference/send/message/){:target="_blank”} - only if that event is already [mapped](https://www.courier.com/docs/platform/sending/create-map-events/){:target="_blank”}.

- Segment passes all `properties` from the Track call to the `Send API` as elements in the `data` json objects. You can use these data points as variables in the Notification Template or as input on conditional routing logic.
- Courier uses the `userId` or `anonymousId` to look up and include the associated `User Profile` with the inbound event. (See the note in the [Identify section](#identify) above.)
Expand Down
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/everflow/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,6 @@ If you aren't familiar with the Segment Spec, take a look at the [Track method d
The TransactionId (`context.referrer.id`) and `context.referrer.type` are **required** fields. Read more about how to pass the TransactionId in [Everflow's TransactionId Documentation](https://developers.everflow.io/docs/everflow-sdk/click_tracking/){:target="_blank"}

### Property Mappings
The data type for Segment properties must match the data type set in Everflow for the corresponding property. Read more about how Everflow maps Segment properties in [Everflow's Properties Mapping documentation](https://helpdesk.everflow.io/en/articles/4785627-integrations-segment){:target="_blank"}.
The data type for Segment properties must match the data type set in Everflow for the corresponding property. Read more about how Everflow maps Segment properties in [Everflow's Properties Mapping documentation](https://helpdesk.everflow.io/en/articles/6288916-segment-integration){:target="_blank"}.

Custom properties are not supported at this time.
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Experiments by Growthhackers Destination
redirect_from: '/connections/destinations/catalog/northstar-by-growthhackers/'
id: 5cc205876b9a830001432515
---
[Experiments by Growthhackers](http://growthhackers.com/software){:target="_blank"} provides a project management tool for growth teams, allowing companies to create and prioritize ideas, run experiments and gather data to learn upon!
[Experiments by Growthhackers](https://growth.software/){:target="_blank"} provides a project management tool for growth teams, allowing companies to create and prioritize ideas, run experiments and gather data to learn upon!

This destination is maintained by Experiments by Growthhackers. For any issues with the destination, [contact the Growthhackers Support team](mailto:[email protected]).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Segment sends Page calls to Impact Partnership Cloud as a `Clicks` event, if the
> success ""
> **Tip!** To accurately track and attribute actions, send a Page call with every page load.
Read [Impact Partnership Cloud's documentation](https://impact-helpdesk.freshdesk.com/en/support/solutions/articles/48001173251){:target="_blank"} to learn more about how Page properties are mapped.
Read [Impact Partnership Cloud's documentation](https://integrations.impact.com/impact-brand/docs/integrate-with-segment#segment-spec-page-calls){:target="_blank"} to learn more about how Page properties are mapped.

## Screen

Expand Down Expand Up @@ -99,4 +99,4 @@ Segment sends Track calls to Impact Partnership Cloud as a `Conversion` or `Page

`Page Load` events appear as `Clicks` on Impact Partnership Cloud's Dashboard if they fit the definition of a unique click.

Read [Impact Partnership Cloud's documentation](https://impact-helpdesk.freshdesk.com/en/support/solutions/articles/48001173251){:target="_blank"} to learn more about how Track properties are mapped.
Read [Impact Partnership Cloud's documentation](https://integrations.impact.com/impact-brand/docs/integrate-with-segment#track-events-parameter-mapping-reference){:target="_blank"} to learn more about how Track properties are mapped.
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/intercom/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ hidden: false
2. Search for "Intercom" and select it in the results that appear.
3. Choose a Kotlin or Swift Mobile source to connect to Intercom.
4. Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
5. [Find your "App ID" in the Intercom UI](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
5. [Find your "App ID" in the Intercom UI](https://developers.intercom.com/installing-intercom/web/installation/#step-3-generate-a-config-file-with-this-command){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.


### Mobile
Expand Down
4 changes: 2 additions & 2 deletions src/connections/destinations/catalog/mammoth/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ rewrite: true
title: Mammoth Destination
id: 5cd3f02701645a0001cf49a0
---
[Mammoth](https://mammoth.io/integrations/segment/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} provides self-serve analytics for analysts, businesses, and developers who can use Mammoth's data warehousing, data discovery & data preparation abilities to arrive at insights.
[Mammoth](https://mammoth.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} provides self-serve analytics for analysts, businesses, and developers who can use Mammoth's data warehousing, data discovery & data preparation abilities to arrive at insights.

Mammoth allows you to blend your data from Segment with other sources of data such as databases and files. Using Mammoth, you can build multiple data pipelines, which are constructed by applying transforms through a no coding interface. Mammoth also allows for the visual discovery of the data and easy exports to databases such as MySQL, Elasticsearch, and PostgreSQL.

Expand All @@ -14,7 +14,7 @@ This destination is maintained by [Mammoth](https://mammoth.io){:target="_blank"



There are three steps to get started using Mammoth with Segment. First, [register for an account with Mammoth](https://mammoth.io/register/choose/starter){:target="_blank"}.
There are three steps to get started using Mammoth with Segment. First, [register for an demo with Mammoth](https://mammoth.io/book-a-demo/){:target="_blank"}.

1. Create a webhook dataset in Mammoth, and copy the API key.
2. Connect Segment to Mammoth.
Expand Down
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/olark/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ When you call [`identify`](/docs/connections/spec/identify/) on `analytics.js`,
* We call `api.visitor.updatePhoneNumber` with `traits.phone` if you send it.
* We call `api.visitor.updateCustomFields` with `traits`.

More documentation on the Olark API can be found [in Olark's docs](https://www.olark.com/documentation?r=qhl4tltg){:target="_blank"}.
More documentation on the Olark API can be found [in Olark's docs](https://www.olark.com/api){:target="_blank"}.

## Track

Expand Down
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/orb/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Orb currently supports track calls, as specified in the [Segment Spec](/docs/con

### Track

Use [Track](/docs/connections/spec/track) calls to automatically send usage events based on your customer's interactions with your application. Any Segment track call will be ingested through [Orb's ingestion pipeline](https://docs.withorb.com/docs/orb-docs/event-ingestion){:target="_blank"} <!---TODO: link machine broke ---> and usage information will be used to calculate billable totals. For example:
Use [Track](/docs/connections/spec/track) calls to automatically send usage events based on your customer's interactions with your application. Any Segment track call will be ingested through [Orb's ingestion pipeline](https://docs.withorb.com/guides/events-and-metrics/event-ingestion){:target="_blank"} and usage information will be used to calculate billable totals. For example:
```js
analytics.track({
event: "payment_confirmed",
Expand Down
2 changes: 1 addition & 1 deletion src/connections/destinations/catalog/qualaroo/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ rewrite: true
title: Qualaroo Destination
id: 54521fda25e721e32a72eee8
---
[Qualaroo](https://qualaroo.com/home){:target="_blank"} is a user testing tool that lets you add a survey to any page on your site, so you can get targeted user feedback as the user is performing a task. The `analytics.js` Qualaroo Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-qualaroo){:target="_blank"}.
[Qualaroo](https://qualaroo.com/){:target="_blank"} is a user testing tool that lets you add a survey to any page on your site, so you can get targeted user feedback as the user is performing a task. The `analytics.js` Qualaroo Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-qualaroo){:target="_blank"}.

## Getting Started

Expand Down
Loading

0 comments on commit c46e07f

Please sign in to comment.