Conditions

By default, experiments are only limited in time. You can further restrict your experiment's conditions by adding rules:

Duration
Audience share
Pages included in experiment
GET parameters
Region
Platform
Custom parameters
Without web crawlers
Using custom IDs

Note

To apply conditions to your experiment:

  1. In Yandex Metrica, go to VarioqubExperimentsCreate experiment.
  2. Select the desired condition.

Duration

The experiment's duration can range from 1 to 90 days. After reaching the end date, the experiment stops automatically. You can stop it manually at any time:

  1. Go to Experiments.

  2. Open the menu next to the experiment and click Stop.

Audience share

By default, experiments take 100% of the site's audience into account. You can specify a percentage (from 1% to 100%) of the total audience across all samples, which will be evenly divided between the samples. Choose the percentage based on your site's traffic.

Pages included in experiment

Specify the domain of the website and URL path without the protocol (http/https) and hash (the # character in the URL and the value after it). For example, to limit the experiment to the home page of your site, specify example.com. Use special operators to set flexible conditions. The period (.) isn't considered an operator.

To have multiple conditions in one string, use the “AND”/“OR” operators.

Examples of operator use What is included in the experiment
example.com* All pages of the domain.
example.* All pages of all the domains starting with example.
example.com/*search* All site pages that include search in their URLs.
example.com/search? Page URLs with either no characters or a single character at the end of the string. For example: example.com/search, example.com/search/, example.com/search2.
example.com/search+ Page URLs with one or more characters at the end of the string. For example: example.com/search/, example.com/search2, example.com/search_goods.
More information about the URL structure

https://<host>/<path>?<params>#<fragment>

  • <host>: Site domain.

  • <path>: A path that can have a hierarchical structure. The structure is indicated using slashes “/”.

  • <params>: The section of parameters that's separated from the path by “?”. These parameters are also called GET parameters.

  • <fragment>: A string with arbitrary content. Separated from GET parameters by “#” (the hash symbol). Not used in the Pages included in experiment conditions.

GET parameters

If you want to run the experiment only on some of the site's pages, specify the GET parameters that are used or not used in their URLs. Use special operators to set flexible conditions. The period (.) isn't considered an operator.

To apply multiple conditions in Varioqub, separate them with commas: aparam=avalue,bparam=bvalue (the conditions are joined by a logical AND). Condition blocks are combined by the OR operator.

Here are the characters you can use with parameters and their values:

  • = — Placed between the parameter name and its value. If absent, only the parameter's presence is taken into account. Example: param=value
  • ? — Matches any character between zero or one time. Example: pa?am=va?ue
  • * — Matches any characters between zero or unlimited times. Example: p*m=v*e
  • + — Matches any characters between one or unlimited times. Example: p+m=v+e
  • ! — Means negation of a condition or exclusion of a parameter from influencing the experiment. Example: !param=val

Warning

Only use negation ! as the first character in a key.

  • Correct example: !param=value.
  • Incorrect examples: param!=value or param=!value.

Usage examples

Usage example

What's taken into account in the experiment

param

Only the presence of the parameter, regardless of its value.

param=value

Exact match of the parameter and its exact value.

!param

Absence of the parameter with any value.

*param*=value

All parameters that contain the param fragment with the value value.

!*param*=value

The value of any parameter with the param fragment shouldn't be value.

!*param*=*value*

The value of any parameter with the param fragment shouldn't contain value.

!*param*

Absence of a parameter containing the param fragment.

Region

The region is determined by the IP address of the user visiting your site.

Possible values:

Russia
  • Moscow
  • Moscow and the Moscow region
  • Belgorod region
  • Bryansk region
  • Vladimir region
  • Voronezh region
  • Ivanovo region
  • Kaluga region
  • Kostroma region
  • Kursk region
  • Lipetsk region
  • Oryol region
  • Ryazan region
  • Smolensk region
  • Tambov region
  • Tver region
  • Tula region
  • Yaroslavl region
  • Saint Petersburg and the Leningrad region
  • Arkhangelsk region
  • Vologda region
  • Kaliningrad region
  • Murmansk region
  • Novgorod region
  • Pskov region
  • Republic of Karelia
  • Komi Republic
  • Kirov region
  • Nizhniy Novgorod region
  • Orenburg region
  • Penza region
  • Perm Territory
  • Republic of Bashkortostan
  • Republic of Mari El
  • Republic of Mordovia
  • Republic of Tatarstan
  • Samara region
  • Saratov region
  • Udmurtian Republic
  • Ulyanovsk region
  • Chuvash Republic
  • Astrakhan region
  • Volgograd region
  • Krasnodar Territory
  • Republic of Adygea
  • Republic of Kalmykia
  • Rostov region
  • Altai Territory
  • Irkutsk region
  • Kemerovo region (Kuzbass)
  • Krasnoyarsk Territory
  • Novosibirsk region
  • Omsk region
  • Republic of Altai
  • Republic of Tuva
  • Republic of Khakassia
  • Tomsk region
  • Amur region
  • Jewish Autonomous Region
  • Trans-Baikal Territory
  • Kamchatka Territory
  • Magadan region
  • Primorye Territory
  • Republic of Buryatia
  • Republic of Sakha (Yakutia)
  • Sakhalin region
  • Khabarovsk Territory
  • Alushta
  • Armyansk
  • Bakhchisarayskiy District
  • Dzhankoy
  • Yevpatoriya
  • Kerch
  • Krasnoperekopsk
  • Leninsky District
  • Saki
  • Sevastopol
  • Simferopol
  • Sudak
  • Feodosia
  • Yalta
  • Kabardino-Balkarian Republic
  • Karachayevo-Circassian Republic
  • Republic of Daghestan
  • Republic of Ingushetia
  • Republic of Crimea
  • Republic of Severnaya Ossetia–Alania
  • Stavropol Territory
  • Chechen Republic
  • Kurgan region
  • Sverdlovsk region
  • Tyumen region
  • Khanty-Mansi Autonomous Area (Yugra)
  • Chelyabinsk region
  • Yamalo-Nenets Autonomous Area
  • Nenets Autonomous Area
CIS
  • Abkhazia
  • Azerbaijan
  • Armenia
  • Belarus
  • Kazakhstan
  • Kyrgyzstan
  • Moldova
  • Tajikistan
  • Turkmenistan
  • Uzbekistan
  • South Ossetia
Europe
  • Austria
  • Belgium
  • Bulgaria
  • United Kingdom
  • Hungary
  • Germany
  • Greece
  • Denmark
  • Spain
  • Italy
  • Cyprus
  • Lithuania
  • Netherlands
  • Norway
  • Poland
  • Portugal
  • Romania
  • Serbia
  • Slovakia
  • Slovenia
  • Türkiye
  • Finland
  • France
  • Croatia
  • Montenegro
  • Czechia
  • Switzerland
  • Sweden
Asia
  • Bahrain
  • Vietnam
  • Georgia
  • Israel
  • India
  • Indonesia
  • Jordan
  • Yemen
  • Cambodia
  • Qatar
  • China
  • Kuwait
  • Malaysia
  • United Arab Emirates
  • Oman
  • Saudi Arabia
  • Singapore
  • Thailand
  • Taiwan
  • Philippines
  • South Korea
  • Japan
North America
  • Guatemala
  • Dominican Republic
  • Canada
  • United States of America
  • Mexico
South America
  • Argentina
  • Brazil
  • Colombia
  • Peru
  • Uruguay
  • Chile
Africa
  • Egypt
  • Côte d'Ivoire
Australia and Oceania
  • Australia
  • New Zealand

You can also use the "Exclude selected regions" toggle to invert your selection, removing the chosen regions from the experiment.

Platform

Smartphones, tablets, desktop devices (PCs), TVs. A site user's device type is identified by their User Agent. To find out from which devices people are most likely to visit your site, see the Devices report in Yandex Metrica.

Custom parameters

Note

This functionality is available in the extended version of Varioqub.

To apply this condition, implement parameter transmission on your site. For example, to send parameters that help profile your users: indicate that they're important, registered on your site, and so on.

Then specify these parameters and their values in the Custom values field so that Varioqub can recognize and use them during the experiment.

To apply multiple conditions in Varioqub, separate them with commas: aparam=avalue,bparam=bvalue (the conditions are joined by a logical AND). Condition blocks are combined by the OR operator.

Here are the characters you can use with parameters and their values:

  • = — Placed between the parameter name and its value. If absent, only the parameter's presence is taken into account. Example: param=value
  • ? — Matches any character between zero or one time. Example: pa?am=va?ue
  • * — Matches any characters between zero or unlimited times. Example: p*m=v*e
  • + — Matches any characters between one or unlimited times. Example: p+m=v+e
  • ! — Means negation of a condition or exclusion of a parameter from influencing the experiment. Example: !param=val

Warning

Only use negation ! as the first character in a key.

  • Correct example: !param=value.
  • Incorrect examples: param!=value or param=!value.

Usage examples

Usage example

What's taken into account in the experiment

param

Only the presence of the parameter, regardless of its value.

param=value

Exact match of the parameter and its exact value.

!param

Absence of the parameter with any value.

*param*=value

All parameters that contain the param fragment with the value value.

!*param*=value

The value of any parameter with the param fragment shouldn't be value.

!*param*=*value*

The value of any parameter with the param fragment shouldn't contain value.

!*param*

Absence of a parameter containing the param fragment.

Without web crawlers

Web crawlers are robots that access your site, for example, for indexing a site or checking its operation. Some robots introduce themselves, while others, on the contrary, try to disguise themselves as a real user so that analytical systems do not detect them.

When creating an experiment, you can exclude crawlers that have identified themselves (their User-agent is known) from the experiment's audience. To do this, select the option Without web crawlers.

Using custom IDs

Note

This functionality is available in the extended version of Varioqub.

To run experiments, Varioqub divides site visitors into groups using its own user IDs.

You can also choose to split users using your own custom user IDs if your service supports them.

To use this condition:

  1. Select Use custom uid for usersplit.

  2. Implement the passing of the GET parameter cuid on the site. The value of the parameter needs to correspond to the user ID.

    Sample request
    GET https://uaas.yandex.ru/v1/exps
      ? [client_id=<String>]
      & [url=<String>]
      & [i=<String>]
      & [client_features=<String>]
      & [cuid=<String>]
    

Warning

The custom ID must not be longer than 30 characters. Users with IDs that exceed this length won't be included in the experiment.

Alert

You might see discrepancies between Varioqub and Yandex Metrica reports because Yandex Metrica reports don't support custom IDs.

FAQ and troubleshooting

I'm trying to create an experiment, but all the fields are locked.

What if I want to use conditions that are not available in the Varioqub interface?

How do I disable a specific experiment type for an entire site or page?

Contact support

Yandex Metrica user ID. Format: metrika.{counter_id}. Where {counter_id} is the Yandex Metrica tag ID. How to find the tag ID

Full URL, including GET parameters, of the page browsed by the user.

If no URL is passed, Varioqub uses the referer from the headers. However, in some cases it may not be possible to send the referer in full or at all. For this reason, we recommend always passing the URL.

Site user's ID stored in first-party cookies. Make sure to set it in the _ymab_param cookie upon receiving the response. It may be empty during the user's first visit to the site.

We recommend passing it in each API request. The field may be empty in the first request.

A serialized JSON object containing user parameters. Example: {"param2": "value2", "param1": "value1"}.

A custom ID that allows you to use your own user IDs in experiments.