Peaka Destination

1. From your workspace's Destination catalog page search for Peaka
2. Select Peaka and click Add destination.
3. Choose which source should send data to the Peaka destination.
4. Log in to Peaka.
5. Follow the steps in the Peaka documentation to create your Segment catalog and obtain your API key.
6. Enter the API Key in the Peaka destination settings in the Segment UI.

Peaka supports the following methods, as specified in the Segment Spec.

Segment sends Page calls to Peaka. For example:

analytics.page("Retail Page", "Home");

You can see Page event data in your Peaka Catalog under the pages table.

Segment sends Screen calls to Peaka. For example:

1
[[SEGAnalytics sharedAnalytics] screen:@"Home"
2
                            properties:@{ @"Feed Type": @"private" }];

You can see Screen event data in your Peaka Catalog under the screens table.

Segment sends Identify calls to Peaka. For example:

1
analytics.identify("97980cfea0067", {
2
  name: "Peter Gibbons",
3
  email: "peter@example.com",
4
  plan: "premium",
5
  logins: 5,
6
});

You can see Identify event data in your Peaka Catalog under the identifies table.

Segment sendsTrack calls to Peaka. For example:

1
analytics.track("User Registered", {
2
  plan: "Pro Annual",
3
  accountType: "Facebook",
4
});

You can see Track event data in your Peaka Catalog under the tracks table.

Segment sends Group calls to Peaka. For example:

1
analytics.group("0e8c78ea9d97a7b8185e8632", {
2
  name: "Initech",
3
  industry: "Technology",
4
  employees: 329,
5
  plan: "enterprise",
6
  "total billed": 830,
7
});

You can see Group event data in your Peaka Catalog under the groups table.

Segment sends Group calls to Peaka. For example:

analytics.alias("507f191e81");

You can see Alias event data in your Peaka Catalog under the aliases table.

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.

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