Segmented and A/B Test Features

Overview

Magify allows features to be targeted to specific user groups through segmentation and A/B testing. This provides flexibility in delivering customized experiences and testing feature impact across different audiences.

Feature Selection Logic

When the client requests a configuration, Magify evaluates applicable feature values in the following priority order:

A/B Test assignment – If the user matches any active A/B test group.
Segmented value – If no A/B test is matched but the user fits a defined segment.
Default value – Used if no match is found.

Creating a Segmented Feature

To define segment-based behavior for a feature:

Go to an existing Application Feature (Navigate to Remote Config → Configurations → Application Feature).
Scroll to or open the Segmented Application Feature section in the left navigation menu.
Click +Add Segmented Application Feature.
Select one or more segments in Segmentationsfield (looked up based on the selected application).
- You can optionally exclude specific segments using the Exclude segmentations field.
Define the Value to be delivered to users in the selected segments.
Repeat this process to assign different values to other segments, if needed.

Start at / End at

The Start at and End at fields define the time window during which a segmented feature value is active and delivered in the configuration for users matching the specified segment. Times are specified in UTC timezone.

Start at – The date and time from which the feature value becomes active. Before this time, users will receive another applicable value (e.g., from a different segment or the default).
End at – The date and time after which the feature value is no longer active. Once this time is reached, users will receive the next available value in the evaluation order (such as another segment or the default).

Notes:

If only Start at is set, the feature value will become active at the specified time and remain active indefinitely.
If only End at is set, the value will be active immediately (if the user qualifies for the segment) and expire at the defined time.
These fields are available only for segmented application features. They cannot be used in default or A/B test configurations. ::

Filters and Statuses

The feature configuration interface supports a combination of filters and statuses that allow precise control over feature value delivery. Filters such as In-App Product Filters can be used to target users based on specific purchases, while statuses like Subscription Status, In-App Status, and Paying Status help define user eligibility based on their engagement and monetization activity. These tools ensure that feature values are shown only to users who match defined behavioral or transactional criteria. The same statuses and filters are used in campaign configurations. For more detailed information, refer to the Filters And Payment Statuses article.

Example: Conditional Booster Feature Distribution Logic

Scenario: The feature startup_booster_count defines how many boosters a user receives at the start of the game.

Default value: 3
Segmented value: 1 — for users located in the United States, using any language except Spanish, and running app version 3.0.0 or higher

Result: Users from the US with a non-Spanish language and app version ≥ 3.0.0 receive 1; all others receive the default value 3.

User Description	Country Condition	Language Condition	App Version Condition	Delivered Value
US user with Spanish language	US	Spanish	≥ 3.0.0	3 (default value)
US user with English language	US	English (≠ Spanish)	≥ 3.0.0	1 (segmented value)
US user with French language	US	French (≠ Spanish)	≥ 3.0.0	1 (segmented value)
US user with any language	US	Any	< 3.0.0	3 (default value)
Non-US user (e.g., CA, UK, DE) with any language	Not US	Any	Any	3 (default value)

Creating A/B Test Features

To assign different feature values to A/B test groups:

First, create an A/B test in draft status—only tests in this status can be selected when configuring feature variations. For details, refer to the A/B Test article.
Navigate to the feature you want to A/B test (Navigate to Remote Config → Configurations → Application Feature).
Scroll to or open the A/B Test Application Feature section.
Click +Add A/B Test Application Feature.
Select the appropriate A/B test from the list — draft status tests are automatically populated in the dropdown — and assign the corresponding groups.
Define the Value that the selected group(s) should receive.
Repeat the process to define values for other groups in the same test.
Click Save to apply changes.
After completing these steps, the A/B test is ready to be launched.