---
metadata:
  - name: generator
    content: Diplodoc Platform v5.54.2
alternate:
  - https://yandex.com/support/varioqub/en/unload-data.md
  - https://yandex.com/support/varioqub/ru/unload-data.md
  - https://yandex.com/support/varioqub/tr/unload-data.md
  - href: en/unload-data.md
    type: text/markdown
    title: Markdown version
  - href: llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com/support/varioqub/en/llms.txt

# Exporting experiment data

With the [Yandex Metrica Logs API](https://yandex.com/dev/metrika/en/logs/), you can get non-aggregated data on experiment results.

<!-- source: en/_includes/paid-feature.md -->
{% note info %}

Only available in the [Varioqub extended version](https://yandex.com/support/varioqub/en/paid-functionality.md).

{% endnote %}
<!-- endsource: en/_includes/paid-feature.md -->

In addition to the standard fields available in the Logs API, you can get a list of IDs of experimental variants. The variants are linked to [sessions](https://yandex.com/dev/metrika/en/logs/fields/visits) of the users included in the sample. To export data, use the following field:

#|
|| **Field** | **Data type** | **Description** ||
|| ##ym:s:testids## | Array(Integer) | ID array. ||
|#

The ID can be found in the [Varioqub report](https://yandex.com/support/varioqub/en/stat.md).

![](_assets/id.png =430x)

You can also get a list of experiment variant IDs and names in Yandex Metrica:

1. Go to **Varioqub → Experiments**.
1. In the upper-right corner of the page, click on the three dots.

![Download variants ids](_assets/id-title.png =430x)

## Integration with Yandex Cloud {#cloud}

<!-- source: en/_includes/paid-feature.md -->
{% note info %}

Only available in the [Varioqub extended version](https://yandex.com/support/varioqub/en/paid-functionality.md).

{% endnote %}
<!-- endsource: en/_includes/paid-feature.md -->

Using the [Yandex Metrica connector](https://yandex.cloud/en/docs/data-transfer/tutorials/metrika-to-clickhouse), you can collect non-aggregated data in your Clickhouse cluster hosted on [Yandex Cloud](https://yandex.cloud/en/).

The integration isn't backward compatible with [LogsAPI](https://yandex.com/dev/metrika/en/logs/) in terms of data format.

The integration mechanism has several advantages compared to Logs API:

- Real-time data streaming. The delay between the time of the event and adding its record to ClickHouse is 15 minutes or less.

- Extended set of fields:

  #|
  || **Category** | **Fields** ||
  || Content analytics data |

  – Article topics and authors.
  – Traffic source.
  – Clicks to other articles on the site.
  – ID of the article from which the user landed to the current one.
  – Article viewing time.
  – Full scrolls. ||
  || Traffic source details |

  – Yandex Direct ad click ID (YCLID).
  – Ad ID.
  – Placement platform.
  – QR code scans. ||
  || Client and order data from CRM |

  – Hash OrderID and Hash UserID.
  – Order version.
  – Order creation and modification time.
  – Order status.
  – Product names and quantities in the order. ||
  |#

To export data, use the following field:

#|
|| **Field** | **Data type** | **Description** ||
|| ##Experiment.SystemID## | Array(Integer) | An array of experiment variant IDs, including negative (technical) values. ||
|#

[Learn more about the integration and Yandex Cloud operating principles](https://yandex.com/support/metrica/pro/cloud.html)

<!-- source: en/_includes/feedback/feedback.md -->
<details>
    <summary class="button">Contact support</summary>
    <div style="padding: 15px;
     margin: 10px 0;
     background: #FFFFFF;
     border-radius: 10px;
     border: 1px solid var(--yc-color-line-generic);">
     <iframe style="background: #FFFFFF;"
        height="700"
        width="100%"
        frameborder="0"
        src="https://forms.yandex.ru/surveys/1705/?iframe=1&lang=en">
    </iframe>
</details>






<!-- endsource: en/_includes/feedback/feedback.md -->

<!-- source: en/_includes/image-styles.md -->

<!-- endsource: en/_includes/image-styles.md -->