Skip to content

Commit ad76785

Browse files
authored
Merge pull request #175 from segmentio/repo-sync
repo sync
2 parents 8c88f23 + 01036f3 commit ad76785

File tree

1 file changed

+65
-0
lines changed
  • src/connections/destinations/catalog/datarangers

1 file changed

+65
-0
lines changed
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
rewrite: true
3+
title: BytePlus
4+
beta: true
5+
---
6+
7+
BytePlus provides product analytics for mobile and web applications, including event/retention/funnel/error analysis, user segmentation, user paths, behavior lookup, A/B testing, and other functions.
8+
9+
In addition to the docs below, please reference the [BytePlus integration guide](https://docs.byteplus.com/data-intelligence/docs/sdk-integration-1){:target="_blank"}.
10+
11+
This destination is maintained by BytePlus. For any issues with the destination, please [contact the BytePlus Support team](mailto:[email protected])
12+
13+
Getting Started
14+
15+
16+
{% include content/connection-modes.md %}
17+
18+
19+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
20+
2. Search for "BytePlus" in the Destinations Catalog, and select the "BytePlus" destination.
21+
3. Choose which Source should send data to the "BytePlus" destination.
22+
4. In BytePlus, go to your "[Organization Settings](https://docs.byteplus.com/data-intelligence/docs/create-your-organizations-and-projects)" > "Project List" and find the targeted project.
23+
5. Click on **Details** for the targeted project and find the API key ("App Key") on the pop-out information page. This should be a 32-character string of numbers and letters.
24+
6. Enter the "API Key" in the "BytePlus" destination settings in Segment.
25+
26+
27+
Page
28+
29+
If you aren’t familiar with the Segment Spec, take a look at the Page method documentation (https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
30+
31+
32+
```js
33+
analytics.page()
34+
```
35+
36+
37+
Segment sends Page calls to BytePlus as a `page` event.
38+
39+
Screen
40+
41+
If you aren’t familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
42+
```obj-c
43+
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
44+
```
45+
46+
Segment sends Screen calls to BytePlus as a`screen`event.
47+
48+
Identify
49+
50+
If you aren’t familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
51+
52+
```js
53+
analytics.identify('userId123', {
54+
55+
});
56+
```
57+
Segment sends Identify calls to BytePlus as an `identify `event with `SSID`.
58+
59+
Track
60+
61+
If you aren’t familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
62+
```js
63+
analytics.track('Login Button Clicked')
64+
```
65+
Segment sends Track calls to BytePlus as a `track` event with event name and properties.

0 commit comments

Comments
 (0)