• Home
  • Integrations
  • SDKs
  • Guides
  • API docs
No results for ""
EXPAND ALL

EDIT ON GITHUB

Big Segments

Read time: 1 minute
Last edited: Aug 11, 2021
Big Segments is an Enterprise feature

Big Segments is available to customers on an Enterprise plan. To learn more, read about our pricing. To upgrade your plan, contact Sales.

Overview

This topic explains what Big Segments are and how to use them.

A Big Segment is a kind of segment that is backed by an external data store. Big Segments can support massive numbers of targets. The maximum number of targets is dictated only by the limits of the data store you configure it with. A standard user segment is capped at 50,000 users. To use Big Segments, you must meet additional prerequisites. To learn more, read Using Big Segments.

To learn more about user segments, read Building user segments.

Syncing Big Segments

You can sync Big Segments from an Amplitude cohort. When you sync your Amplitude cohort to the LaunchDarkly destination in the Amplitude dashboard, it creates a synced segment. This allows the segment to contain a large number of users from Amplitude.

The same prerequisites for Big Segments apply to Big Segments that are synced from an Amplitude cohort. To learn more, read Syncing segments from Amplitude cohorts.

Using Big Segments

To use Big Segments, you must meet the following prerequisites:

  • You must properly configure the Relay Proxy:
    • If you use server-side SDKs, you must use the Relay Proxy and it must be configured to use Big Segments.
    • If you use client-side SDKs, the Relay Proxy is not required. However, if you do use the Relay Proxy, you must configure it to use Big Segments. To learn more, read Using the Relay Proxy.
  • You must configure your SDKs to use Big Segments:
    • If you use server-side SDKs, you must use an SDK version that supports Big Segments. To learn more, read the Big Segments SDK documentation.
    • All client-side SDKs support Big Segments by default, so there's no additional setup required for client-side SDKs.