Moesif API Analytics Destination

1. From the Segment web app, click Catalog.
2. Search for "Moesif" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the Moesif "API Key" into the destinations settings in the Segment App. You can find these by going to your Moesif account and navigating to the extensions settings.
4. Once integrated, Segment data shows up in Moesif in a few seconds.

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

1
analytics.identify('userId123', {
2
      first_name: 'John',
3
      last_name: 'Doe',
4
      email: 'john@example.com',
5
      company: {
6
          id: '67890',
7
          plan: 'Free'
8
      }
9
});

Segment sends identify() calls to Moesif as user updates which you can see in the Users section in Moesif. If you set traits.company.id on the user, Moesif associates them with a company. The integration maps user fields as follows:

The integration handles Segment reserved traits like email and firstName. It maps automatically-collected fields like campaign information and IP address.

If you haven't had a chance to review our spec, take a look tounderstand what the Track method does. An example call would look like:

analytics.track('Login Button Clicked')

Segment sends track() calls to Moesif as user actions which you can see in the Events section in Moesif. The integration maps event fields as follows:

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.