Stored Application Feature

Overview

A Stored Application Feature allows you to deliver application resources as separate files.

Unlike an Application Feature, which stores values directly in the generated application configuration, a Stored Application Feature stores uploaded files separately. The generated configuration contains references to these files. The Magify SDK downloads, caches, and provides the corresponding files to the client application.

Stored Application Features are recommended for large or complex resources that are easier to maintain as separate files, such as JSON configurations, game levels, images, audio files, localization resources, and other application assets.

Like Application Features, Stored Application Features support segmentation and A/B testing, allowing different files to be delivered to different groups of users.

Supported File Types

Stored Application Features can be used to deliver any file type that the client application supports.

Common examples include:

JSON configuration files
Images
Audio files
CSV files
Localization resources
Other application assets

Magify does not impose restrictions on uploaded file types. However, the client application must be able to download, process, and use the uploaded file correctly.

Creating a Stored Application Feature

To create a Stored Application Feature:

Navigate to Remote Config → Configurations → Stored Application Feature → Create New.
Select the appropriate application.
Fill in the required fields.
Upload the file to be delivered to the client application.
Click Save.

A Stored Application Feature consists of three configuration levels:

Stored Application Feature — defines the default file.
Stored Segmented Application Feature — overrides the default file for users who match specific segmentation rules.
Stored A/B Test Application Feature — overrides the default or segmented file for users participating in an A/B test.

The following sections describe each configuration level and its available fields.

Stored Application Feature

The Stored Application Feature defines the default file that is delivered when no matching segmented or A/B test configuration overrides it.

General Information

Field	Description
Application	The application to which the Stored Application Feature belongs. This field is available only during creation and cannot be changed later.
Key	A unique identifier used by the client application to request the file. The key cannot be changed after the feature is created.
Description	An optional internal description visible only in the Magify admin interface. Use it to document the purpose of the feature or provide implementation notes for your team.
File	The default file delivered when no segmented or A/B test configuration overrides it.

Version Availability

The App Version From and App Version To fields define the application version range for which the default file is available.

magify-stored-application-feature-default-app-version

Field	Description
App Version From	The minimum application version (inclusive) that can receive the file.
App Version To	The maximum application version (inclusive) that can receive the file.

The version range configured here applies only to the default Stored Application Feature.

Segmented and A/B test configurations define their own version availability independently.

The following section explains how Magify determines which file is delivered when multiple Stored Application Feature configurations exist.

Configuration Resolution

When generating the application configuration, Magify evaluates the available Stored Application Feature configurations to determine which file should be delivered.

                 Application configuration is generated
                                │
                                ▼
                  Is there a matching A/B test?
                                │
                 ┌──────────────┴──────────────┐
                 │                             │
               Yes                            No
                 │                             │
                 ▼                             ▼
      Deliver A/B test file        Is there a matching segment?
                                               │
                              ┌────────────────┴───────────────┐
                              │                                │
                            Yes                               No
                              │                                │
                              ▼                                ▼
                  Deliver segmented file         Deliver default file

Configuration priority:

Stored A/B Test Application Feature
Stored Segmented Application Feature
Stored Application Feature (default)

The first matching configuration is included in the generated application configuration.

The Magify SDK then downloads, caches, and provides the corresponding file to the client application.

Stored Segmented Application Feature

To create a segmented configuration, click + Add Stored Segmented Application Feature.

A Stored Segmented Application Feature allows you to deliver a different file to users who match specific segmentation rules.

When a user matches the configured segmentation rules, a different file is delivered instead of the default file. If no segmentation rule matches and the user is not included in a matching A/B test configuration, the default Stored Application Feature is delivered.

magify-stored-application-feature-ab-test

General Information

Field	Description
Segmentations	Defines the user segments that should receive this file.
Exclude Segmentations	Excludes selected segments from receiving this file, even if they match the included segmentation rules.
Content	The file delivered to users who match the configured segmentation rules.
Start At	Specifies the date and time from which this segmented configuration becomes active.
End At	Specifies the date and time until which this segmented configuration remains active.

Filters

In addition to segmentation rules, a segmented configuration can be filtered using user statuses, purchase history, product groups, referrer IDs, and other targeting criteria.

Unlike segmentation, which is evaluated on the server when the application configuration is generated, filters are evaluated by the client application. This allows file delivery to respond immediately to changes in user state without requiring a new configuration.

For a detailed description of all available filters and their behavior, see Filters and Payment Statuses.

Availability Period

The Start At and End At fields define the period during which this segmented configuration can be applied.

If the current date and time falls outside this period, the configuration is ignored during evaluation.

If no start or end time is specified, the configuration remains active without time restrictions.

Stored A/B Test Application Feature

To create an A/B test configuration, click + Add Stored A/B Test Application Feature.

A Stored A/B Test Application Feature allows you to deliver a different file to users assigned to a specific A/B test group.

When a user belongs to the selected A/B test group, a different file is delivered instead of the default file or any matching segmented configuration.

General Information

Field	Description
A/B Test	Specifies the A/B test that controls file delivery.
Group	Specifies the A/B test group that receives this file.
Content	The file delivered to users assigned to the selected A/B test group.
Is forced	Prevents the application from marking this A/B Test Application Feature as applied. As a result, the user remains assigned to the selected A/B test group and continues receiving this feature while the A/B test is active.

Filters

In addition to the selected A/B test group, an A/B test configuration can be filtered using user statuses, purchase history, product groups, referrer IDs, and other targeting criteria.

Unlike A/B test assignment, which is evaluated on the server when the application configuration is generated, filters are evaluated by the client application. This allows file delivery to respond immediately to changes in user state without requiring a new configuration.

For a detailed description of all available filters and their behavior, see Filters and Payment Statuses.

Note

To remove a segmented or A/B test configuration, click the Delete (trash) icon in the upper-right corner of the corresponding configuration card.
Before deleting a configuration, make sure it is not used by an active (Running) A/B test.
The default configuration and the Stored Application Feature itself cannot be deleted. If the Stored Application Feature should no longer be delivered for newer application versions, limit its version range using the App version to field. For example, to stop delivering the Stored Application Feature starting with application version 3.0.0, set App version to to 3.0.0.

magify-stored-application-feature-delete

Stored File Delivery

Stored Application Features are resolved as part of the application configuration.

Unlike regular Application Features, stored feature values are delivered as separate files rather than being included directly in the configuration.

When the application receives the generated configuration, it also receives the metadata required to access the stored files.

The application requests a stored file by its feature key. The SDK then downloads the corresponding file, caches it locally, and makes it available for use by the application.

This approach allows large resources such as JSON configurations, images, localization files, audio assets, or other application content to be delivered independently of the main configuration while still being managed through the same configuration system.

Implementation examples for Unity are available in the App Features section of the Unity SDK documentation.

Implementation examples for additional SDKs will be added in future documentation updates.

Recommendations

Follow these recommendations when working with Stored Application Features:

Use the Appropriate Feature Type

Choose the feature type based on the data you want to deliver.

Use Application Features	Use Stored Application Features
Feature flags	Images
Numeric, boolean, and string values	Audio files
Small JSON configurations	Video files
UI parameters	Localization files
Small configuration values	Large JSON files (for example, level configurations, tutorial configurations, game world configurations, dialogue databases, or balance tables)

Use Descriptive Feature Keys

Use descriptive Feature Keys that clearly reflect the purpose of the resource.

Examples:

level_configuration
tutorial_configuration
game_balance

Supported Content

Stored Application Features can contain any files supported by your application. Magify does not restrict the type of content or business scenarios they can be used for.

File Size Recommendations

Although there is no strict file size limit, we recommend keeping individual files below 160 MB.

Stored Application Features are optimized for files around 40–50 MB, providing the best balance between download performance, caching, and application startup time.

The following articles provide additional information related to Stored Application Features:

Application Features
Segmentation
A/B Tests (coming soon)
Filters and Payment Statuses
Unity SDK – App Features
Android SDK (coming soon)
iOS SDK (coming soon)