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/setup.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,10 +8,10 @@ This guide outlines the steps required to set up the Signals SDK in your applica
8
8
You'll learn how to add Auto-Instrumentation sources, integrate dependencies, and ensure that your setup captures and processes data as intended.
9
9
10
10
> info "Auto-Instrumentation Pilot"
11
-
> 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.
11
+
> 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.
12
12
13
-
> success "Enable Auto-Instrumentation in your workspace"
14
-
> To enable Auto-Instrumentation in your Segment worksapce, reach out to your dedicated account manager.
13
+
> success "Enable Auto-Instrumentation"
14
+
> To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager.
15
15
16
16
## Step 1: Add a source and get its write key
17
17
@@ -25,7 +25,7 @@ You'll first need to add a source and copy its write key:
25
25
26
26
## Step 2: Add dependencies and initialization code
27
27
28
-
Next, you'll need to add the Signals SDKs to your development environment.
28
+
Next, you'll need to add the Signals SDKs to your Swift and Kotlin development environments.
29
29
30
30
### Swift
31
31
@@ -45,7 +45,7 @@ Follow these steps to integrate the Signals SDK into your Swift application:
45
45
46
46
// Set up the Signals SDK configuration
47
47
let config = Signals.Configuration(
48
-
writeKey: "<WRITE_KEY>", // Replace <WRITE_KEY> with your actual write key
48
+
writeKey: "<WRITE_KEY>", // Replace <WRITE_KEY> with the write key you previously copied
49
49
maximumBufferSize: 100,
50
50
useSwiftUIAutoSignal: true,
51
51
useNetworkAutoSignal: true
@@ -102,8 +102,6 @@ Follow these steps to integrate the Signals SDK into your Kotlin application:
102
102
analytics.add(SignalsComposeTrackingPlugin())
103
103
```
104
104
105
-
<!-- PW: Hmmm, no write key in this code? -->
106
-
107
105
3. (Optional:) If you want to track network activity, configure your OkHttpClient to use the Signals OkHttp3 plugin:
108
106
109
107
```kotlin
@@ -116,7 +114,7 @@ Follow these steps to integrate the Signals SDK into your Kotlin application:
116
114
117
115
## Step 3: Verify and deploy events
118
116
119
-
Next, you'll need to verify signal emission and create rules to convert those signals into events:
117
+
Next, you'll need to verify signal emission and [create rules](/docs/connections/auto-instrumentation/configuration/#example-rule-implementations) to convert those signals into events:
120
118
121
119
1. In your Segment workspace, return to **Connections > Auto-Instrumentation** and click on the new source you created.
122
120
2. Verify that signals appear as expected on the dashboard.
0 commit comments