> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/cafe-24/24-copy.md).

# Cafe24 A/B Experiment Metrics - (In Progress)

{% hint style="info" %}
This document describes A/B experiment metrics using events that are automatically collected during Cafe24 Integration.

This document assumes that the Hackle SDK has been installed via [Cafe24 Integration](/en/cafe-24/integration.md). It provides guidance on how to set up metrics commonly used for Cafe24 store A/B experiments using the events automatically collected after integration.

For the basic guide on setting A/B metrics, refer to the links below.

* A/B Test Create & Configure
* Set Metrics for A/B Tests
  {% endhint %}

## 1. Purchase Conversion Rate

You can measure the `purchase conversion rate` of users who completed an order among users assigned to the experiment.

* Numerator event: Order complete (`cafe24_complete_order`)
  * Calculation type (`User count`)
* Denominator event: All users
  * Calculation type (`User count`)
* Success criteria: `Increase compared to control`

![](/files/JWtjExH1upJxCiw9yWT9)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/cafe-24/24-copy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.