Lantern Destination

Lantern provides autonomous anomaly detection for all your product metrics. It only takes a minute to enable with Segment, no coding involved.

Lantern is a user behavior monitoring solution for modern product teams. Lantern alerts you on Slack when something doesn’t look right. You get full-coverage over your product and the confidence that you will be notified of any significant variation.

This destination is maintained by Lantern. For any issues with the destination, contact Lantern’s support.

Getting Started

Automated Setup

1. Log into your Lantern dashboard.
2. When prompted to add a source, click the Segment logo.
3. Pick a Segment workspace and source.
4. Click “Allow”.

Manual Setup

1. From the Segment web app, click Catalog.
2. Search for “Lantern” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the “API Key” into your Segment Settings UI which you can find by contacting Lantern’s support settings page.

Next Steps

• That’s it! Lantern is already at work and will deliver your fist insights in a few hours.
• In the meantime, you can connect your Slack workspace to Lantern by clicking on the “Receive Insights In Slack” button from the Lantern newsfeed page.
• Add more sources to get more insights. Go to Settings -> Sources -> Add Source to repeat the process for additional sources.

Page

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

analytics.page();

Lantern will monitor page events and send you alerts when an anomaly occurs (sudden change in level, trend or periodicity of the metric).

Screen

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

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Lantern will monitor screen events and send you alerts when an anomaly occurs (sudden change in level, trend or periodicity of the metric).

Identify

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:

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

Lantern does not surface information that links to a user’s personal identity. Lantern only analyses the volume of identify calls to detect anomalies related to the total number of unique users and perform various computation over aggregated data.

Track

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

analytics.track('Products Searched', {
  query: 'blue hotpants'
});

Lantern will monitor track events and send you alerts when an anomaly occurs (sudden change in level, trend or periodicity of the metric).

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.