You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-absmartly/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ for this purpose.
39
39
> info ""
40
40
> By default, the _Track Calls_ mapping will filter and not send any events with the name `Experiment Viewed` to ABsmartly.
41
41
42
-
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.
42
+
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.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/braze/index.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ Braze created a sample iOS application that integrates Braze using Segment. See
67
67
68
68
#### Device-mode set up for iOS 14 support
69
69
70
-
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"}
70
+
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"}
71
71
documentation.
72
72
73
73
To use the latest Braze SDK to collect IDFAs you must do the following:
@@ -76,7 +76,7 @@ To use the latest Braze SDK to collect IDFAs you must do the following:
76
76
2. Update the Braze iOS Segment SDK to version 3.3.0 or greater.
77
77
3. Import and add the AppTrackingTransparency (ATT) Framework.
78
78
- 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.
79
-
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"}
79
+
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"}
80
80
.
81
81
5. Follow [Segment's guide for collecting IDFA](/docs/connections/sources/catalog/libraries/mobile/ios/#idfa-collection-in-40-beta-and-later)
82
82
@@ -122,7 +122,7 @@ Segment sends Page calls to Braze as custom events if you have enabled either **
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"}.
125
+
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"}.
126
126
127
127
Ifyou'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:
128
128
@@ -193,7 +193,7 @@ Segment sends all other traits (except Braze's [reserved user profile fields](ht
193
193
## Track
194
194
195
195
> info "Tip"
196
-
> 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/).
196
+
> 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/).
197
197
198
198
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:
199
199
@@ -325,7 +325,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt
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:
328
+
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:
329
329
330
330
```objc
331
331
if ([Appboy sharedInstance] == nil) {
@@ -624,4 +624,4 @@ No. Audiences are sent to Braze as either custom attributes or custom events. Yo
624
624
All Braze user profile data (including custom events, custom attributes) is stored for as long as those profiles are active.
625
625
626
626
#### What happens if I delete a computed trait or audience in Segment?
627
-
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.
627
+
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.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/courier/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Segment Track events are inbound events that might trigger a notification when C
81
81
82
82
All Inbound Events coming from Segment Track calls appear with a `Segment-TrackEvent` prefix in Courier to help distinguish them from other inbound events.
83
83
84
-
Courier extracts data from the Segment Track `properties` object, and conditionally triggers a request to the [CourierSendAPI](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”}.
84
+
Courier extracts data from the Segment Track `properties` object, and conditionally triggers a request to the [CourierSendAPI](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”}.
-Courierusesthe`userId`or`anonymousId`tolookupandincludetheassociated`User Profile`withtheinboundevent. (See the note in the [Identify section](#identify) above.)
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/everflow/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,6 @@ If you aren't familiar with the Segment Spec, take a look at the [Track method d
49
49
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"}
50
50
51
51
### Property Mappings
52
-
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"}.
52
+
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"}.
[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!
7
+
[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!
8
8
9
9
This destination is maintained by Experiments by Growthhackers. For any issues with the destination, [contact the Growthhackers Support team](mailto:tech@growthhackers.com).
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/impact-partnership-cloud/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Segment sends Page calls to Impact Partnership Cloud as a `Clicks` event, if the
30
30
> success ""
31
31
> **Tip!** To accurately track and attribute actions, send a Page call with every page load.
32
32
33
-
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.
33
+
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.
34
34
35
35
## Screen
36
36
@@ -99,4 +99,4 @@ Segment sends Track calls to Impact Partnership Cloud as a `Conversion` or `Page
99
99
100
100
`Page Load` events appear as `Clicks` on Impact Partnership Cloud's Dashboard if they fit the definition of a unique click.
101
101
102
-
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.
102
+
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.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/intercom/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ hidden: false
16
16
2. Search for "Intercom" and select it in the results that appear.
17
17
3. Choose a Kotlin or Swift Mobile source to connect to Intercom.
18
18
4. Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
19
-
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`.
19
+
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`.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/mammoth/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ rewrite: true
3
3
title: Mammoth Destination
4
4
id: 5cd3f02701645a0001cf49a0
5
5
---
6
-
[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.
6
+
[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.
7
7
8
8
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.
9
9
@@ -14,7 +14,7 @@ This destination is maintained by [Mammoth](https://mammoth.io){:target="_blank"
14
14
15
15
16
16
17
-
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"}.
17
+
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"}.
18
18
19
19
1. Create a webhook dataset in Mammoth, and copy the API key.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/orb/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Orb currently supports track calls, as specified in the [Segment Spec](/docs/con
24
24
25
25
### Track
26
26
27
-
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:
27
+
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:
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/qualaroo/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ rewrite: true
3
3
title: Qualaroo Destination
4
4
id: 54521fda25e721e32a72eee8
5
5
---
6
-
[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"}.
6
+
[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"}.
0 commit comments