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/auto-instrumentation/configuration.md
+3-33Lines changed: 3 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -3,48 +3,18 @@ title: Generate Events from Signals
3
3
hidden: true
4
4
---
5
5
6
-
This guide is a reference to configuring, generating, and using signals in the Signals SDK with Auto-Instrumentation. On this page, you'll find details on:
6
+
This guide details how to use signals, and their associated data, generated in one of the Signals SDKs with the Auto-Instrumentation dashboard in your Segment workspace. On this page, you'll find details on:
7
7
8
-
- Setting up and managing signal types in the Signals SDK
9
8
- Creating custom rules to capture and translate signals into actionable analytics events
10
9
- Example rules that you can use as a basis for further customization
11
10
12
-
This guide assumes that you've already added the Signals SDK to your application. If you haven't yet, see the [Auto-Instrumentation Setup](/docs/connections/auto-instrumentation/setup/) guide for initial setup.
11
+
This guide assumes that you've already added the Signals SDK to your application. If you haven't yet, see the [Auto-Instrumentation Setup](/docs/connections/auto-instrumentation/) guide for initial setup.
13
12
14
13
> info "Auto-Instrumentation Pilot"
15
14
> Auto-Instrumentation is currently in pilot and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment doesn't recommend Auto-Instrumentation for use in a production environment, as Segment is actively iterating on and improving the user experience.
16
15
17
16
> success "Enable Auto-Instrumentation"
18
-
> To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager.
19
-
20
-
## Signals configuration
21
-
22
-
Using the Signals Configuration object, you can control the destination, frequency, and types of signals that Segment automatically tracks within your application. The following tables detail the configuration options for both Signals-Swift and Signals-Kotlin.
|`maximumBufferSize`| No | Integer | The number of signals to be kept for JavaScript inspection. This buffer is first-in, first-out. Default is `1000`. |
30
-
|`relayCount`| No | Integer | Relays signals to Segment every Xth event. Default is `20`. |
31
-
|`relayInterval`| No | TimeInterval | Relays signals to segment every X seconds. Default is `60`. |
32
-
|`broadcasters`| No |`SignalBroadcaster`| An array of broadcasters. These objects forward signal data to their destinations, like `WebhookBroadcaster` or `DebugBroadcaster` writing to the developer console. Default is `SegmentBroadcaster`. |
33
-
|`useUIKitAutoSignal`| No | Bool | Tracks UIKit component interactions automatically. Default is `false`. |
34
-
|`useSwiftUIAutoSignal`| No | Bool | Tracks SwiftUI component interactions automatically. Default is `false`. |
35
-
|`useNetworkAutoSignal`| No | Bool | Tracks network events automatically. Default is `false`. |
36
-
|`allowedNetworkHosts`| No | Array | An array of allowed network hosts. |
37
-
|`blockedNetworkHosts`| No | Array | An array of blocked network hosts. |
|`maximumBufferSize`| No | Integer | The number of signals to be kept for JavaScript inspection. This buffer is first-in, first-out. Default is `1000`. |
46
-
|`broadcastInterval`| No | Integer | Broadcasts signals to Segment every X event. Default is `60`. |
47
-
|`broadcasters`| No |`List<SignalBroadcaster>`| An array of broadcasters. These objects forward signal data to their destinations, like `WebhookBroadcaster` or `DebugBroadcaster` writing to the developer console. Default is `SegmentBroadcaster`. |
17
+
> To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager.
Auto-Instrumentation simplifies tracking in your websites and apps by eliminating the need for a traditional Segment instrumentation.
@@ -29,10 +50,35 @@ Some Auto-Instrumentation advantages include:
29
50
30
51
## How it works
31
52
32
-
After you [integrate the Analytics SDK and Signals SDK into your application](/docs/connections/auto-instrumentation/setup/), Segment begins to passively monitor user activity like button clicks, page navigation, and network data. Segment captures these events as "signals" and sends them to your Auto-Instrumentation source in real time.
53
+
Once you integrate the Analytics SDK and Signals SDK into your website or application, Segment begins to passively monitor user activity like button clicks, page navigation, and network data. Segment captures these events as "signals" and sends them to your Auto-Instrumentation source in real time.
33
54
34
55
In Segment, the Auto-Instrumentation source lets you view raw signals. You can then [use this data to create detailed analytics events](/docs/connections/auto-instrumentation/configuration/) based on those signals, enriching your insights into user behavior and applicatino performance.
Auto-Instrumentation removes personally identifiable information (PII) from breadcrumbs before they get sent to Segment. No user data is visible to Segment.
Verify that you replaced `<WRITE_KEY>` with the actual write key you copied in Step 1.
64
-
65
-
#### SwiftUI projects
66
-
67
-
If your app is written in SwiftUI, you'll need to add a `TypeAlias.swift` file to your project that captures interaction and navigation Signals, like in this example:
68
-
69
-
```swift
70
-
import Foundation
71
-
import Signals
72
-
73
-
typealias Button = SignalButton
74
-
typealias NavigationStack = SignalNavigationStack
75
-
typealias NavigationLink = SignalNavigationLink
76
-
typealias TextField = SignalTextField
77
-
typealias SecureField = SignalSecureField
78
-
```
79
-
80
-
### Kotlin
81
-
82
-
Follow these steps to integrate the Signals SDK into your Kotlin application:
28
+
Next, you'll need to add the Signals SDKs to your Kotlin application.
83
29
84
30
1. Update your module’s Gradle build file to add the right dependencies:
85
31
@@ -98,7 +44,10 @@ Follow these steps to integrate the Signals SDK into your Kotlin application:
98
44
}
99
45
```
100
46
101
-
2. Add the following code to your application to initialize the Signals SDK:
47
+
2. Add the initialization code and configuration options:
48
+
49
+
> success ""
50
+
> see [configuration options](#configuration-options) for a complete list.
102
51
103
52
```kotlin
104
53
// Configure Analytics with your settings
@@ -143,6 +92,18 @@ Next, you'll need to verify signal emission and [create rules](/docs/connections
143
92
144
93
Segment displays `Rule updated successfully` to verify that it saved your rule.
145
94
95
+
## Configuration Options
96
+
97
+
Using the Signals Configuration object, you can control the destination, frequency, and types of signals that Segment automatically tracks within your application. The following table details the configuration options for Signals-Kotlin.
| `maximumBufferSize` | No | Integer | The number of signals to be kept for JavaScript inspection. This buffer is first-in, first-out. Default is `1000`. |
103
+
| `broadcastInterval` | No | Integer | Broadcasts signals to Segment every X event. Default is `60`. |
104
+
| `broadcasters` | No | `List<SignalBroadcaster>` | An array of broadcasters. These objects forward signal data to their destinations, like `WebhookBroadcaster` or `DebugBroadcaster` writing to the developer console. Default is `SegmentBroadcaster`. |
105
+
106
+
146
107
## Next steps
147
108
148
-
This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers examples rules.
109
+
This guide walked you through initial Signals SDK/Auto-Instrumentation setup. Next, read the [Auto-Instrumentation Signals Implementation Guide](/docs/connections/auto-instrumentation/configuration/), which dives deeper into Signals and offers example rules.
0 commit comments