Humanic AI Destination

1. Navigate to Connections > Catalog and select the Destinations tab in the catalog.
2. Search for Humanic AI in the catalog and select the destination.
3. Choose which source should send data to the Humanic AI destination.
4. Go to the Humanic dashboard and select the API Keys tab. Generate an API key and copy it.
5. Enter the API Key in the Humanic AI destination settings in Segment.

Humanic AI supports the following methods as specified in the Segment Spec.

Send Page calls to record which web pages users visited. For example:

1
analytics.page("Pricing", {
2
  title: "Segment Pricing",
3
  url: "https://segment.com/pricing",
4
  path: "/pricing",
5
  referrer: "https://segment.com/warehouses",
6
});

Segment sends Page calls to Humanic AI as a pageview.

Send Screen calls to record which mobile app screens users viewed. For example:

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

Segment sends Screen calls to Humanic AI as a screenview.

Send Identify calls to create new users or update existing users with new values. For example:

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

Segment sends Identify calls to Humanic AI as an identify event.

Send Track calls to record user behavior in your app. For example:

analytics.track('Login Button Clicked');

Segment sends Track calls to Humanic AI as a track event.

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.