Skip to content

Commit fa124ad

Browse files
committed
Add link and more cleanup
1 parent 650ab03 commit fa124ad

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

src/connections/auto-instrumentation/configuration.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ hidden: true
66

77
## Configure Signals
88

9+
10+
911
### Swift
1012

1113

src/connections/auto-instrumentation/setup.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@ This guide outlines the steps required to set up the Signals SDK in your applica
88
You'll learn how to add Auto-Instrumentation sources, integrate dependencies, and ensure that your setup captures and processes data as intended.
99

1010
> 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.
1212
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.
1515
1616
## Step 1: Add a source and get its write key
1717

@@ -25,7 +25,7 @@ You'll first need to add a source and copy its write key:
2525

2626
## Step 2: Add dependencies and initialization code
2727

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.
2929

3030
### Swift
3131

@@ -45,7 +45,7 @@ Follow these steps to integrate the Signals SDK into your Swift application:
4545
4646
// Set up the Signals SDK configuration
4747
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
4949
maximumBufferSize: 100,
5050
useSwiftUIAutoSignal: true,
5151
useNetworkAutoSignal: true
@@ -102,8 +102,6 @@ Follow these steps to integrate the Signals SDK into your Kotlin application:
102102
analytics.add(SignalsComposeTrackingPlugin())
103103
```
104104

105-
<!-- PW: Hmmm, no write key in this code? -->
106-
107105
3. (Optional:) If you want to track network activity, configure your OkHttpClient to use the Signals OkHttp3 plugin:
108106

109107
```kotlin
@@ -116,7 +114,7 @@ Follow these steps to integrate the Signals SDK into your Kotlin application:
116114

117115
## Step 3: Verify and deploy events
118116

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:
120118
121119
1. In your Segment workspace, return to **Connections > Auto-Instrumentation** and click on the new source you created.
122120
2. Verify that signals appear as expected on the dashboard.

0 commit comments

Comments
 (0)