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-amplitude/index.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,13 +53,14 @@ To manually add the Log Purchases Action:
53
53
54
54
The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)) with the Actions-framework version of the destination, you do not need the device-mode connection.
55
55
56
-
Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Unify Identity Resolution.
56
+
57
+
Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution.
57
58
58
59
Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)
59
60
60
61
61
62
### Device ID Mappings
62
-
The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses the a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID.
63
+
The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID.
63
64
64
65
By default, Segment maps the Segment property `context.device.id` to the Amplitude property `Device ID`. If `context.device.id` isn't available, Segment maps the property `anonymousId` to the Amplitude `Device ID`. The Actions interface indicates this with the following contents of the Device ID field: `coalesce(``context.device.id``anonymousId``)`.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-tiktok-audiences/index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ By using Segment's TikTok Audiences destination, you can increase traffic and dr
25
25
26
26
### Connect the TikTok Audiences destination
27
27
28
-
1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with the TikTok Audiences destination. Either choose an existing Engage Audience or create a new one. This is the Audience you plan to send to TikTok.
28
+
1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with the TikTok Audiences destination. Either choose an existing Engage audience or create a new one. This is the audience you plan to send to TikTok.
29
29
30
30
2. Navigate to **Engage > Engage Settings** and click **Destinations**. Please ensure you are still in the correct Engage space.
31
31
@@ -43,12 +43,12 @@ By using Segment's TikTok Audiences destination, you can increase traffic and dr
43
43
44
44
9. Repeat Steps 7 and 8 to also set up a **Remove Users** mapping.
45
45
46
-
10. Navigate back to **Engage > Audiences** and click on the Audience from Step 1.
46
+
10. Navigate back to **Engage > Audiences** and click on the audience from Step 1.
47
47
48
48
11. Click **Add Destinations** and select the TikTok Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and do **not** change the Audience Entered/Audience Exited event names. Click **Save Settings**.
49
49
50
-
The setup is complete and the audience will start syncing to TikTok. The audience will appear in your [TikTok Ads Manager](https://www.tiktok.com/business/en-US/solutions/ads-manager){:target="_blank"} account under **Assets > Audiences**. Please note that it can take 24-28 hours for users to appear in TikTok.
50
+
The setup is complete and the audience will start syncing to TikTok. The audience will appear in your [TikTok Ads Manager](https://www.tiktok.com/business/en-US/solutions/ads-manager){:target="_blank"} account under **Assets > Audiences**. Please note that it can take 24-48 hours for users to appear in TikTok.
51
51
52
52
To sync additional audiences from your Engage space, create a separate mapping in the TikTok Audiences destination. Navigate to **Connections > Destinations**, search and select the TikTok Audiences destination, and follow Steps 7-11 above.
53
53
54
-
{% include components/actions-fields.html settings="true"%}
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/clevertap/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Once the Segment library is integrated, toggle CleverTap on in your Segment dest
9
9
10
10
You can integrate CleverTap using a server-side or mobile destination (iOS or Android). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
11
11
12
-
All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap.
12
+
All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap. CleverTap maintains the server-side integration. For any issues with the server-side integration, [contact the CleverTap Support team](https://help.clevertap.com/hc/en-us/requests/new){:target="_blank"}.
13
13
14
14
CleverTap supports the `identify`, `track`, `page` (server-side only), and `screen` (iOS and server-side only) methods.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/heap/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ id: 54521fd725e721e32a72eebd
12
12
1. From the Segment web app, click **Catalog**.
13
13
2. Search for "Heap" in the Catalog, select it, and choose which of your sources to connect the destination to.
14
14
3. In the destination settings, enter your Heap "App ID" into the connection settings.
15
-
4.If you are using Heap using Segment's client-side `analytics.js` library, we asynchronously load Heap's JavaScript library onto the page. As such, all native functionality of Heap, including auto-capturing of all events.
15
+
4.Remove Heap's snippet from your page if you're using Segment's client-side Analytics.js library to load Heap. With the Analytics.js library, Segment asynchronously loads Heap's JavaScript library onto your page. All native functionality of Heap, including auto-capturing of all events are available to you.
Copy file name to clipboardExpand all lines: src/connections/destinations/destination-filters.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ rewrite: true
10
10
11
11
Use destination filters to prevent certain data from flowing into a destination. You can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
12
12
13
-
You can configure destination filters on cloud-mode, mobile, and web device-mode and actions-based destinations. With device-mode destinations, you can use the same user interface or API mechanism that you use for your cloud-mode destinations, and have those filters acted upon for device-mode destinations on web and mobile.
13
+
You can configure destination filters on cloud-mode, mobile cloud-mode destinations, and web device-mode and actions-based destinations. With device-mode destinations, you can use the same user interface or API mechanism that you use for your cloud-mode destinations, and have those filters acted upon for device-mode destinations on web.
14
14
15
15
Common use cases for destination filters include:
16
16
- Managing PII (personally identifiable information) by blocking fields from reaching certain destinations
@@ -29,7 +29,9 @@ Keep the following limitations in mind when you use destination filters:
29
29
-*(For device-mode)* Destination filters don't filter on native events that the destination SDK collects. Instead, you can use the load option to conditionally load relevant bundled JavaScript on the page. See the docs for [load options](/docs/connections/sources/catalog/libraries/website/javascript/#load-options).
30
30
-*(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
31
31
-*(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
32
-
-*(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source. Destination filters for mobile is currently not supported.
32
+
-*(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source.
33
+
-*(For mobile device-mode)* Destination filters for mobile device-mode is currenlty not supported.
34
+
33
35
34
36
[Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
The instanceId was introduced in [V 2.10.1](https://github.com/segmentio/analytics-react-native/releases/tag/%40segment%2Fanalytics-react-native-v2.10.1) and correlates events to a particular instance of the client in a scenario when you might have multiple instances on a single app.
685
+
686
+
### How do I interact with the integrations object?
687
+
The integrations object is no longer part of the Segment events method signature. To access the integrations object and control what destinations the event reaches, you can use a Plugin:
688
+
689
+
```js
690
+
import {
691
+
EventType,
692
+
Plugin,
693
+
PluginType,
694
+
SegmentEvent,
695
+
} from'@segment/analytics-react-native';
696
+
697
+
exportclassModifyextendsPlugin {
698
+
type =PluginType.before;
699
+
700
+
asyncexecute(event:SegmentEvent) {
701
+
if (event.type==EventType.TrackEvent) {
702
+
let integrations =event.integrations;
703
+
if (integrations !==undefined) {
704
+
integrations['Appboy'] =false;
705
+
}
706
+
}
707
+
//console.log(event);
708
+
returnevent;
709
+
}
710
+
}
711
+
```
685
712
## Changelog
686
713
[View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/server/net/index.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,11 @@
2
2
title: Analytics for .NET
3
3
repo: analytics.NET
4
4
id: 8HWbgPTt3k
5
+
tags:
6
+
- C#
7
+
- C-sharp
5
8
---
6
-
Our .NET library is the best way to integrate analytics into your .NET application or website. It lets you record analytics data from your ASP.NET, C#, F#, and Visual Basic code. The library issues requests that hit our servers, and then we route your data to any analytics service you enable on our destinations page. This library is open-source, so you can [check it out on GitHub](https://github.com/segmentio/Analytics.NET).
9
+
Segment's .NET library is the best way to integrate analytics into your .NET application or website. It lets you record analytics data from your ASP.NET, C#, F#, and Visual Basic code. The library issues requests that hit our servers, and then Segment routes your data to any analytics service you enable on our destinations page. This library is open-source, so you can [check it out on GitHub](https://github.com/segmentio/Analytics.NET).
7
10
8
11
All of Segment's server-side libraries are built for high-performance, so you can use them in your web server controller code. This library uses an internal queue to make `identify` and `track` calls non-blocking and fast. It also batches messages and flushes asynchronously to our servers.
Copy file name to clipboardExpand all lines: src/connections/storage/index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ title: Data Storage overview
5
5
Off-the-shelf analytics tools (like Google Analytics and Mixpanel) offer quick and easy insights about common business questions, and often meet the needs of marketing teams and product managers. However, data analysts and data scientists need access to an organization's raw data to derive deeper and more customized insights to support their organization.
6
6
7
7
> success ""
8
-
> Warehouse Destination are only available and functional for Business and Team Tier customers.
8
+
> Only users with Business or Team plans can add Warehouse destinations.
9
9
10
10
Segment offers several [Data Storage Destinations](/docs/connections/storage/catalog/) to help you store your raw Segment data, including:
11
11
12
-
-[Data Warehouses](/docs/connections/storage/warehouses/) (SQL-based databases, such as Postgres and Redshift)
0 commit comments