Anodot Destination

Anodot rapidly identifies revenue-critical issues by leveraging AI to constantly monitor and correlate business performance, providing real-time alerts and forecasts.

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

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Anodot” in the Destinations Catalog, and select the Anodot destination.
3. Choose which Source should send data to the Anodot destination.
4. Go to Anodot’s Data Management Page, create a new “Segment” Source, and copy the Integration Token.
5. Enter the Integration Token into the “API Key” field in the Anodot Destination settings in Segment.
6. Create a Stream in Anodot. Choose which Segment Methods and which Dimensions to track.

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 Anodot as a pageview.

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 Anodot as a screenview.

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 Anodot as an identify event.

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 Anodot as a track event.

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.