Akita User Tracking Destination

Destination Info

Akita provides Customer Success Management tools for Software-as-a-Service applications–helping you nurture, retain and grow your customer base.

This destination is maintained by Akita. For any issues with the destination, contact Akita support.

The Akita Destination is in beta, which means that they are still actively developing the destination. To join their beta program, or if you have any feedback to help improve the Akita Destination and its documentation, contact the Akita support team!

Getting Started

  1. From the Destinations catalog page in the Segment App, click Add Destination.
  2. Search for “Akita” in the Destinations Catalog, and select the “Akita User Tracking” destination.
  3. Choose which Source should send data to the “Akita User Tracking” destination.
  4. Go to the “Connect Segment” Page, find and copy the “Segment.com API Key”.
  5. Enter the “API Key” in the “Akita User Tracking” destination settings in Segment.

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("contact_123", {
  email: "john.doe@example.com",
  groupId: "account_123" /** Optional **/,
});

Segment sends Identify calls to Akita as a contact event.

You may find a list of useful information to send as traits in your Identify call in the Segment > Configure tab in Akita.

Akita adds contacts described using Identify events as Contacts associated with the correct account.

Akita is primarily an Account management tool. All Contacts in Akita must be associated with one-and only one-Account. You must also use the Segment Group event (see below).

For best results, Akita recommends you also send the groupId (the identifier you send with Group) as a trait in all Identify events. This allows Akita to identify the Contact if you have not yet made the required Group call.

Group

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

analytics.group("account_123", {
  name: "Initech",
  plan: "Enterprise",
});

Segment sends Group calls to Akita as an account event.

You may find a list of useful information to send as traits in your Group call in the Segment > Configure tab in Akita.

Accounts described using the Group event are added to Akita as Accounts.

Groups identified through Segment Group events become Accounts in Akita.

Track

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

analytics.track("search:submit");

Segment sends Track calls to Akita as a event event.

Page

If you aren’t familiar with the Page 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 Akita as a page event.

You must send either event or page events (or both) for Akita to recognize and store your users Sessions.

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.

Real-time to batch destination sync frequency

Real-time audience syncs to Akita User Tracking may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

Settings

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

Setting Description
API Key
(required)
string. You can find your Segment.com API Key in Akita under Settings > Segment.com.

This page was last modified: 16 Nov 2022



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account