Skip to main content

Adding ID Lists

Adding ID Lists​

What is an ID List?​

An ID List enables you to define a reusable audience segment using user identifiers like userID, stableID, or organizationID.

You can manage ID Lists by manually adding/removing IDs, uploading CSVs, or replacing the entire list.

Creating an ID List Segment​

  1. Navigate to the Segments section in the Statsig Console.
  2. Click Create New Segment.
  3. Toggle the segment type from Conditional to ID List. Create New Segment
  4. Select the ID type you want to build from. Create New Segment

Managing IDs​

Once inside your ID List segment, you have a variety of options:

  • Manual Entry: Enter IDs directly into the input box. Create New Segment
  • Upload CSV: Import a list of IDs from a CSV.
  • Bulk Actions: Choose how your input affects the existing list:
    • Add: Add IDs to the list
    • Remove: Remove matching IDs from the list
    • Replace: Clear all IDs and replace with a new list

You can also sync in an ID list Segment from sources like an Amplitude Cohorts or Segment Audiences or from a custom source using the Console API

There is a hard limit of 10 million IDs across all ID Lists in your project.

Keep ID Lists Small(!)​

When an ID List is small (no more than 1000 IDs), it is synchronized in the same process with other feature gates, experiments, and conditional segments, which has high consistency and reliability. Once an ID List goes over 1000 in size, to scale efficiently and not negatively impact the other entities as the lists grow, there is a separate process to synchronize them. As a result, they are not downloaded in the main initialization process (in the initialization path of server SDKs, or the local evaluation version of our client SDKs), and change propagation takes longer.

We recommend always keeping your ID Lists to be no more than 1000 IDs in each, unless you are okay with the caveats mentioned above.

(deprecated) Large ID Lists(!)​

Statsig's support for very large ID lists has been deprecated. To target hundreds of thousands of users (or billions), the preferred pattern is to set an attribute on the User object passed to the Statsig SDK. e.g. pass in user_type:Paid or user_type:Trial in the User object, instead of having ID Lists that enumerate the Paid and Trial users. This does require your app to have this information when calling the Statsig SDK, but you're better able to control how/where to cache this information.