Skip to content

DOCSPLAT 2878 Small changes #7985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 30, 2025
Merged

DOCSPLAT 2878 Small changes #7985

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/connections/auto-instrumentation/kotlin-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ navController.turnOnScreenTracking()

When you run this code, keep the following in mind:

- You'll need to replace <WRITE_KEY> with the key from your Android Source in Segment.
- You'll need to replace `<WRITE_KEY>` with the key from your Android Source in Segment.
- `debugMode` sends signals to Segment for use in the Event Builder. Only enable it in development environments.
- If your app doesn't use Jetpack Compose or Navigation, you can skip those plugin lines.

Expand Down Expand Up @@ -250,4 +250,4 @@ The following table lists the available options:

## Next steps

After you've confirmed that signals show up in the Event Builder, use the [Generate Events from Signals](/docs/connections/auto-instrumentation/configuration/) guide to configure how signals get translated into analytics events.
After you've confirmed that signals show up in the Event Builder, use the [Generate Events from Signals](/docs/connections/auto-instrumentation/configuration/) guide to configure how signals get translated into analytics events.
2 changes: 1 addition & 1 deletion src/connections/sources/catalog/cloud-apps/twilio/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ Below are tables outlining the properties included in the collections listed abo
| caller_name | The caller's name if this Call was an incoming call to a phone number with Caller ID Lookup enabled |
| date_created | The date that this resource was created, given as GMT in RFC 2822 format |
| date_updated | The date that this resource was last updated, given as GMT in RFC 2822 format |
| direction | A string describing the direction of the Call. Values are inbound for inbound calls, outbound-api for calls initiated using the REST API or outbound-dial for calls initiated by a <Dial> verb |
| direction | A string describing the direction of the Call. Values are inbound for inbound calls, outbound-api for calls initiated using the REST API or outbound-dial for calls initiated by a `<Dial>` verb |
| duration | The length of the Call in seconds. This value is empty for busy, failed, unanswered or ongoing calls |
| end_time | The time the Call ended, given as GMT in RFC 2822 format. Empty if the call did not complete successfully |
| forwarded_from | The forwarding phone number if this Call was an incoming call forwarded from another number (depends on carrier supporting forwarding) |
Expand Down
2 changes: 1 addition & 1 deletion src/partners/checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ The ultimate goal is for Partners like yourself to create and publish high quali

- Add your Component to a Workspace
- In Developer Center "Test in your workspace" section, select your personal workspace and click "view"
- Click "Configure <App>"
- Click "Configure \<App>"
- Select a Source and click "Confirm Source"
- Fill in settings like "API Key" then click the button to enable the component
- Click the "Event Tester" tab and click "Send Event"
Expand Down
Loading