Skip to content
AI Agent

Install with AI Agent

Copy & paste this prompt

Install the Hyperstone Unity SDK in this project. Follow these steps: 1. Read the integration recipe: https://hyperstone.ai/docs/llms.txt 2. Use the documentation that best fits your context window: - Minimal (fast): https://hyperstone.ai/docs/llms.txt - Full (comprehensive): https://hyperstone.ai/docs/llms-full.txt - Small (optimized): https://hyperstone.ai/docs/llms-small.txt 3. Execute the installation following the recipe instructions. 4. Verify that the SDK is correctly installed and integrated into the project.

Creating an Optimization

Optimization is the main tool of Hyperstone. You specify the parameters to be optimized, indicate the target metric, and the ML algorithm begins automatically selecting the best values for different segments of your users.

To create an optimization, open the required project and click the New Experiment button.

The optimization creation interface is divided into three columns, which must be filled out strictly in order — from left to right:

ColumnNameWhat you do
1MetricsSelect the target metric, secondary metrics, and configuration “stickiness” duration.
2ParametersSelect project parameters that will be tested in the optimization.
3ConfigurationsSpecify concrete values (variants) for each selected parameter and indicate the baseline production value.

Fill in all three columns, and then either save the optimization as a draft or launch it immediately.

The bottom line of the screen displays summary information about the current state of the optimization:

FieldValue
Sec. MetricsNumber of connected secondary metrics
ConfigsNumber of configuration variants
Est. DurationEstimated minimum and recommended duration of the optimization
Testing ScopeNumber of selected parameters
Target MetricSelected target metric
StickinessSelected type of configuration “stickiness”

In this step, you define the indicators the system will use to evaluate the effectiveness of the optimization.

This is the main indicator that the ML algorithm will optimize. The system relies on it when deciding which configuration variant is better.

Choose one of two modes:

  • Recommended — ready-made metrics pre-configured by the system based on typical monetization tasks.
  • Custom (Events) — a custom metric built based on your own events.

Select the required metric from the Metric Name dropdown list. Over 30 ready-made metrics are available in the system, divided into categories: revenue, advertising, retention, sessions, engagement, and in-app purchases.

See the full list of all metrics with descriptions, types, and calculation formulas in the Optimization Metrics section.

Secondary metrics do not affect the optimization algorithm, but they are displayed in reports — they help see the full picture and avoid negative side effects.

By default, the system suggests four recommended secondary metrics:

MetricIdentifierType
IAP Revenue per Useriap_revenue_per_userper user
Ad Revenue per Userad_revenue_per_userper user
Revenue per Dayrevenue_per_dayper day
Revenuerevenue_totaltotal

You can remove unnecessary metrics or add your own by clicking + Add Secondary Metric.

Configuration: “Stickiness” (Configuration Stickiness)

Section titled “Configuration: “Stickiness” (Configuration Stickiness)”

Stickiness determines how long a user will receive the same configuration after the first request to the system. If the user opens the game again during this period, the timer resets. If the user has not visited for longer than the set time, they may receive a different configuration upon their next visit.

Available options:

VariantStickiness TimeWhen to use
Session10 minutesFor optimizations within a single game session.
Same day16 hoursFor optimizations within a single day.
User lifetime (default)30 daysFor most optimizations — the user consistently receives one configuration for a month.

In this step, you choose which specific parameters of the project the optimization will test.

On the left, a list of all parameters you added to the project during the parameter creation stage is displayed. For each parameter, its type (string, number, boolean) and default value are specified.

Click on a parameter to include it in the optimization. Selected parameters are highlighted, and the Testing Scope counter in the bottom line is updated.


In this step, you specify concrete values that the system will test for each selected parameter.

For each parameter, two blocks are configured:

Enter all the variants you want to check. Each variant is a separate “card.” Click + Add Value to add a new variant.

Example: for the parameter ad_interstitial_interval (type number), you can specify variants 30, 60, 90, 120.

Select from the dropdown list the value that is currently used in your game. This is the reference point — the system will compare the results of all variants exactly with it.


After configuring all three steps, you have two options:

ButtonWhat happens
Create as DraftOptimization is saved as a draft. The system does not start the optimization — you can return and refine the settings later.
Start NowOptimization starts immediately. The system begins distributing users among configuration variants and collecting data.

After starting the optimization, you can track its results in the Optimization Analytics section.