Segmentation

Overview

Segmentation is a mechanism for dividing application users into groups (segments) based on specific characteristics.

Segments are used to control user behavior and deliver relevant configurations within Remote Config entities, including:

• campaigns (parent and nested);
• features;
• impression limits;
• A/B tests.

Segmentation allows you to:

• deliver different configurations to different audiences;
• control campaign and feature reach;
• run A/B tests;
• configure and validate setups for specific user groups (for example, QA).

Where to Find Segmentation

The Segmentation section is available at:

Magify > Configurations > Remote Config > Segmentation

This section displays the list of all segments created for the selected application.

Default Segment (ALL)

When a new application is added to the system, a system segment named ALL is created automatically.

The ALL segment is created for:

• the application in production;
• the application in sandbox.

The ALL segment includes all users of the application.

ALL Segment Details

• created automatically when an application is added;
• includes 100% of application users;
• does not contain any segmentation criteria;
• available in all Remote Config entities;
• can be archived;
• can be edited, however it is recommended to keep the ALL segment unchanged and create separate segments for custom scenarios.

Creating a Segment

To create a new segment, navigate to:

Magify > Configurations > Remote Config > Segmentation > Create New

When creating a segment, you need to:

1. Select the application for which the segment is created;
2. Specify a segment name;
3. Configure segmentation criteria.

After saving, the segment becomes available for further use.

How Segmentation Works

Segmentation in Magify is dynamic.

This means:

• user–segment matching is recalculated on every configuration request;
• a user can automatically:
  • enter a segment;
  • stop matching a segment;
  • match the segment again.

Segments do not store users and do not form permanent audiences.

Segment Lifecycle

• a segment becomes active immediately after saving;
• no additional activation or publishing is required;
• segment changes are applied automatically;
• a segment can be edited or archived at any time;
• archived segments cannot be restored;
• if needed, an archived segment can be cloned by assigning it a unique name and using it as a new segment.

If a segment is used in active entities, changes are applied on the next user configuration requests.

Next, the documentation covers available segmentation criteria, their logic, and usage examples.