Skip to content

Commit 10a4c2d

Browse files
authored
edits
1 parent bc5e42e commit 10a4c2d

File tree

1 file changed

+21
-21
lines changed
  • src/connections/destinations/catalog/peaka

1 file changed

+21
-21
lines changed

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

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -4,50 +4,50 @@ id: 651ea97b7982672f1d66b93c
44
beta: true
55
---
66

7-
[Peaka](https://peaka.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a Zero-ETL platform that connects to any source. Ingest high-volume event and streaming data. Replace batch with real-time access.
7+
[Peaka](https://peaka.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a Zero-ETL platform that connects to any source. With Peak you can ingest high-volume event and streaming data, and replace batch with real-time access.
88

99
By integrating Peaka with their Segment workspace, users can designate Peaka as one of their destinations. This means that events such as pages, screens, tracks,
10-
and more will be sent directly to Peaka's Segment data catalog. With this integration, Peaka users can begin querying their product events.
10+
and more send directly to Peaka's Segment data catalog. With this integration, Peaka users can begin querying their product events.
1111

12-
This destination is maintained by Peaka. For any issues with the destination, [contact the Peaka Support team](mailto:[email protected]).
12+
Peaka maintains this destination. For any issues with the destination, [contact the Peaka Support team](mailto:[email protected]).
1313

1414
## Getting started
1515

1616
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for **Peaka**
17-
2. Select **Peaka** and click **Add Destination**
18-
3. Choose which Source should send data to the **Peaka** destination.
19-
4. Go to the [Peaka](https://peaka.studio/){:target="_blank"}, create your Segment Catalog and copy the **API key**.
20-
5. Follow the steps in **Peaka** [Documentation](https://www.peaka.com/docs/integrations/segment/) on how to create your Segment Catalog and obtain your **API key**
21-
6. Enter the **API Key** in the **Peaka** destination settings in Segment.
17+
2. Select **Peaka** and click **Add destination**.
18+
3. Choose which source should send data to the Peaka destination.
19+
4. Log in to [Peaka](https://peaka.studio/){:target="_blank"}.
20+
5. Follow the steps in the [Peaka documentation](https://www.peaka.com/docs/integrations/segment/){:target="_blank"} to create your Segment catalog and obtain your **API key**.
21+
6. Enter the **API Key** in the **Peaka** destination settings in the Segment UI.
2222

2323
## Supported methods
2424

25-
**Peaka** supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
25+
Peaka supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
2626

2727
### Page
2828

29-
Segment sends [Page](/docs/connections/spec/page) calls to **Peaka**. For example:
29+
Segment sends [Page](/docs/connections/spec/page) calls to Peaka. For example:
3030

3131
```js
3232
analytics.page("Retail Page", "Home");
3333
```
3434

35-
You can see **Page** event data in your Peaka Catalog under **pages** table.
35+
You can see Page event data in your Peaka Catalog under the pages table.
3636

3737
### Screen
3838

39-
Segment sends [Screen](/docs/connections/spec/screen) calls to **Peaka**. For example:
39+
Segment sends [Screen](/docs/connections/spec/screen) calls to Peaka. For example:
4040

4141
```obj-c
4242
[[SEGAnalytics sharedAnalytics] screen:@"Home"
4343
properties:@{ @"Feed Type": @"private" }];
4444
```
4545
46-
You can see **Screen** event data in your Peaka Catalog under **screens** table.
46+
You can see Screen event data in your Peaka Catalog under the screens table.
4747
4848
### Identify
4949
50-
Segment sends [Identify](/docs/connections/spec/identify) calls to **Peaka**. For example:
50+
Segment sends [Identify](/docs/connections/spec/identify) calls to Peaka. For example:
5151
5252
```js
5353
analytics.identify("97980cfea0067", {
@@ -58,11 +58,11 @@ analytics.identify("97980cfea0067", {
5858
});
5959
```
6060

61-
You can see **Identify** event data in your Peaka Catalog under **identifies** table.
61+
You can see Identify event data in your Peaka Catalog under the identifies table.
6262

6363
### Track
6464

65-
Segment sends[Track](/docs/connections/spec/track) calls to **Peaka**. For example:
65+
Segment sends[Track](/docs/connections/spec/track) calls to Peaka. For example:
6666

6767
```js
6868
analytics.track("User Registered", {
@@ -71,11 +71,11 @@ analytics.track("User Registered", {
7171
});
7272
```
7373

74-
You can see **Track** event data in your Peaka Catalog under **tracks** table.
74+
You can see Track event data in your Peaka Catalog under the tracks table.
7575

7676
### Group
7777

78-
Segment sends [Group](/docs/connections/spec/group) calls to **Peaka**. For example:
78+
Segment sends [Group](/docs/connections/spec/group) calls to Peaka. For example:
7979

8080
```js
8181
analytics.group("0e8c78ea9d97a7b8185e8632", {
@@ -87,14 +87,14 @@ analytics.group("0e8c78ea9d97a7b8185e8632", {
8787
});
8888
```
8989

90-
You can see **Group** event data in your Peaka Catalog under **groups** table.
90+
You can see Group event data in your Peaka Catalog under the groups table.
9191

9292
### Alias
9393

94-
Segment sends [Group](/docs/connections/spec/alias) calls to **Peaka**. For example:
94+
Segment sends [Group](/docs/connections/spec/alias) calls to Peaka. For example:
9595

9696
```js
9797
analytics.alias("507f191e81");
9898
```
9999

100-
You can see **Alias** event data in your Peaka Catalog under **aliases** table.
100+
You can see Alias event data in your Peaka Catalog under the aliases table.

0 commit comments

Comments
 (0)