# Zuko

URL: https://docs.ablyft.com/developers/integrations/zuko/

> Send the variation a visitor saw to Zuko as a custom attribute and compare form behavior per variation.



ABlyft has a built-in Zuko integration. Once you switch it on, ABlyft adds one custom attribute per experiment to the
visitor's Zuko session. You can then filter form abandonment, field drop-off and sessions by variation.

## What you need

* Zuko is installed on your website, and the form is already added in Zuko.

## Activate the integration

1. Open **Project → Integrations**.
2. On the **Zuko** card, switch the toggle from **Not active** to **Activated** and confirm.

ABlyft then republishes the project. There are no further settings.

## Where you see the data in Zuko

Trigger: **Experiment viewed**. ABlyft sends the data every time the experiment runs for the visitor. ABlyft does not wait for Zuko.

* Attribute name: `ABlyft Experiment: <experiment name>`, one attribute per experiment
* Attribute value: `Variation: <variation name>`

Name and value are each limited to 85 characters, and Zuko does not accept longer ones. If the same attribute is set several times in a session, only the last value counts.

Need a different format? [Build a custom integration](https://docs.ablyft.com/developers/integrations/custom-integrations/).

The attribute `ABlyft Experiment: <experiment name>` appears in the filter list of these views:

* **Form Aggregate**
* **Field Aggregate**
* **Session Explorer**
* **Segment Comparison**

Choose the attribute and the value `Variation: <variation name>` to filter, or use **Segment Comparison** to put two
variations side by side. Zuko only attributes data to sessions that interact with a form added to Zuko.

## Check the setup

1. Open a page with a running experiment, in a variation you are bucketed into.
2. In Zuko, open the **Session Explorer** and look for the attribute in the filter.

## Notes

> **Consent and tracking:** The integration does not run when tracking is disabled for the visitor (opt-out or Do Not Track). Zuko may need its
> own consent category in your consent tool. Zuko expects values that describe a group of visitors, which a variation
> name does.

[Zuko documentation](https://www.zuko.io/guides/using-custom-attributes)