BytePlus

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.

In addition to the docs below, please reference the BytePlus integration guide.

This destination is maintained by BytePlus. For any issues with the destination, please contact the BytePlus Support team

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “BytePlus” in the Destinations Catalog, and select the “BytePlus” destination.
3. Choose which Source should send data to the “BytePlus” destination.
4. In BytePlus, go to Organization Settings > Project List and find the targeted project.
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.
6. Enter the “API Key” in the “BytePlus” destination settings in Segment.

Page

If you aren’t familiar with the Segment Spec, take a look at the Page method documentation to learn about what it does. An example call would look like:

analytics.page() 

Segment sends Page calls to BytePlus as a page event.

Screen

If you aren’t familiar with the Segment Spec, take a look at the Screen method documentation to learn about what it does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to BytePlus as ascreenevent.

Identify

If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

Segment sends Identify calls to BytePlus as an identify event with SSID.

Track

If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

analytics.track('Login Button Clicked')

Segment sends Track calls to BytePlus as a track event with event name and properties.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.