|
1 | 1 | ---
|
2 |
| -title: 'BytePlus Destination' |
3 |
| -hidden: true |
4 |
| -published: false |
| 2 | +rewrite: true |
| 3 | +title: BytePlus |
| 4 | +redirect_from: |
| 5 | + - '/connections/destinations/catalog/datarangers/' |
5 | 6 | beta: true
|
6 | 7 | ---
|
| 8 | + |
| 9 | +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. |
| 10 | + |
| 11 | +In addition to the docs below, please reference the [BytePlus integration guide](https://docs.byteplus.com/data-intelligence/docs/sdk-integration-1){:target="_blank"}. |
| 12 | + |
| 13 | +This destination is maintained by BytePlus. For any issues with the destination, please [contact the BytePlus Support team ](mailto:[email protected]) |
| 14 | + |
| 15 | +## Getting Started |
| 16 | + |
| 17 | +{% include content/connection-modes.md %} |
| 18 | + |
| 19 | + |
| 20 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 21 | +2. Search for "BytePlus" in the Destinations Catalog, and select the "BytePlus" destination. |
| 22 | +3. Choose which Source should send data to the "BytePlus" destination. |
| 23 | +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. |
| 24 | +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. |
| 25 | +6. Enter the "API Key" in the "BytePlus" destination settings in Segment. |
| 26 | + |
| 27 | + |
| 28 | +## Page |
| 29 | + |
| 30 | +If you aren’t familiar with the Segment Spec, take a look at the Page method documentation (/docs/connections/spec/page/) to learn about what it does. An example call would look like: |
| 31 | + |
| 32 | + |
| 33 | +```js |
| 34 | +analytics.page() |
| 35 | +``` |
| 36 | + |
| 37 | + |
| 38 | +Segment sends Page calls to BytePlus as a `page` event. |
| 39 | + |
| 40 | +## Screen |
| 41 | + |
| 42 | +If you aren’t familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: |
| 43 | +```obj-c |
| 44 | +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; |
| 45 | +``` |
| 46 | +
|
| 47 | +Segment sends Screen calls to BytePlus as a`screen`event. |
| 48 | +
|
| 49 | +## Identify |
| 50 | +
|
| 51 | +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: |
| 52 | +
|
| 53 | +```js |
| 54 | +analytics.identify('userId123', { |
| 55 | + |
| 56 | +}); |
| 57 | +``` |
| 58 | +Segment sends Identify calls to BytePlus as an `identify `event with `SSID`. |
| 59 | + |
| 60 | +## Track |
| 61 | + |
| 62 | +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: |
| 63 | +```js |
| 64 | +analytics.track('Login Button Clicked') |
| 65 | +``` |
| 66 | +Segment sends Track calls to BytePlus as a `track` event with event name and properties. |
| 67 | + |
0 commit comments