Skip to content

Commit 2616592

Browse files
author
Thomas Gilbert
committed
[index.md] update Bucket destination copy
1 parent 43adcfe commit 2616592

File tree

1 file changed

+11
-11
lines changed
  • src/connections/destinations/catalog/bucket

1 file changed

+11
-11
lines changed

src/connections/destinations/catalog/bucket/index.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,10 @@ title: Bucket Destination
33
rewrite: true
44
id: 5fabc0b00f88248bbce4db48
55
---
6-
[Bucket](https://bucket.so/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) features analytics for SaaS companies.
76

8-
This destination is maintained by Bucket. For any issues with the destination, [contact the Bucket Support team](mailto:[email protected]).
7+
[Bucket](https://bucket.co/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is feature-focused analytics. Bucket empowers software teams with a repeatable approach to shipping features that customers crave.
8+
9+
This destination is maintained by Bucket. For any issues with the destination, [contact the Bucket Support team](mailto:[email protected]).
910

1011
## Getting Started
1112

@@ -14,17 +15,17 @@ This destination is maintained by Bucket. For any issues with the destination, [
1415
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
1516
2. Search for "Bucket" in the Destinations Catalog, and select the Bucket destination.
1617
3. Choose which Source should send data to the Bucket destination.
17-
4. Go to [Bucket's Settings](https://bucket.so) and find and copy the "App ID".
18-
5. Enter the App ID as "API Key" in the "Bucket" destination settings in Segment.
18+
4. Go to [Bucket's Settings](https://bucket.co) and find and copy the "Tracking Key" under Settings.
19+
5. Enter the "Tracking Key" as "API Key" in the "Bucket" destination settings in Segment.
1920

2021
## Identify
2122

2223
If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
2324

2425
```js
25-
analytics.identify('userId123', {
26-
name: 'John Doe',
27-
26+
analytics.identify("userId123", {
27+
name: "John Doe",
28+
2829
});
2930
```
3031

@@ -35,8 +36,8 @@ Segment sends Identify calls to Bucket as an `identify` event which updates User
3536
If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like:
3637

3738
```js
38-
analytics.identify('groupId123', {
39-
name: 'Acme, Inc',
39+
analytics.identify("groupId123", {
40+
name: "Acme, Inc",
4041
});
4142
```
4243

@@ -47,8 +48,7 @@ Segment sends Group calls to Bucket as a `group` event which updates Company pro
4748
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like:
4849

4950
```js
50-
analytics.track('Login Button Clicked', {
51-
})
51+
analytics.track("Login Button Clicked", {});
5252
```
5353

5454
Segment sends Track calls to Bucket as a `track` event which updates the Features page.

0 commit comments

Comments
 (0)