# A/B 테스트

- [A/B 테스트란](https://docs.hackle.io/ab-test/about.md)
- [체험하기(Tutorial)](https://docs.hackle.io/ab-test/about/ab-step-by-step.md)
- [A/B 테스트 주제가 고민된다면?](https://docs.hackle.io/ab-test/about/ab-test-topic.md)
- [A/B 테스트 기획 문서 작성하기](https://docs.hackle.io/ab-test/about/ab-test-one-pager.md)
- [A/B 테스트 생성 및 설정](https://docs.hackle.io/ab-test/create-and-configure.md)
- [새 A/B 테스트 생성하기](https://docs.hackle.io/ab-test/create-and-configure/create-ab-test.md)
- [파라미터 설정](https://docs.hackle.io/ab-test/create-and-configure/abtest-parameter.md)
- [지표 설정하기](https://docs.hackle.io/ab-test/create-and-configure/set-metrics.md)
- [리텐션 생성하기](https://docs.hackle.io/ab-test/create-and-configure/set-abretention-metric.md)
- [퍼널 생성하기](https://docs.hackle.io/ab-test/create-and-configure/set-funnel-metric.md)
- [타겟팅 설정하기](https://docs.hackle.io/ab-test/create-and-configure/ab-targeting.md)
- [A/B 테스트 시작하기](https://docs.hackle.io/ab-test/create-and-configure/start-ab-test.md)
- [트래픽 할당하기](https://docs.hackle.io/ab-test/create-and-configure/traffic-allocation.md)
- [테스트 예약하기](https://docs.hackle.io/ab-test/create-and-configure/abtest-scheduling.md)
- [목표 설정하기\_(유형 추가)](https://docs.hackle.io/ab-test/create-and-configure/set-metrics-ver05.md)
- [목표 설정하기 - version 2](https://docs.hackle.io/ab-test/create-and-configure/set-metric-ver02.md)
- [A/B 테스트의 상태](https://docs.hackle.io/ab-test/status.md)
- [진행 상태 진단](https://docs.hackle.io/ab-test/status/health-check.md)
- [테스트 그룹 분배](https://docs.hackle.io/ab-test/group-distribution.md)
- [테스트 그룹 분배 과정](https://docs.hackle.io/ab-test/group-distribution/ab-variation.md)
- [테스트 그룹 분배 원리](https://docs.hackle.io/ab-test/group-distribution/ab-bucketing.md)
- [테스트 그룹 분배 결과](https://docs.hackle.io/ab-test/group-distribution/ab-variation-result.md)
- [데이터 분석 및 결과 해석](https://docs.hackle.io/ab-test/data-analysis.md)
- [데이터 분석](https://docs.hackle.io/ab-test/data-analysis/interpret-results.md)
- [데이터 세부 분석 설정하기](https://docs.hackle.io/ab-test/data-analysis/ab-segment-setting.md)
- [데이터가 없을 때 해결 방법](https://docs.hackle.io/ab-test/data-analysis/sa-trouble-shooting.md)
- [데이터 세부 분석 소개](https://docs.hackle.io/ab-test/data-analysis/intro-segment.md)
- [리텐션](https://docs.hackle.io/ab-test/data-analysis/ab_test_retention.md)
- [퍼널](https://docs.hackle.io/ab-test/data-analysis/analyze-ab-funnel-data.md)
- [극단치](https://docs.hackle.io/ab-test/data-analysis/outlier.md)
- [A/A 테스트](https://docs.hackle.io/ab-test/data-analysis/aa-test.md)
- [전사 영향도 (Global Impact)](https://docs.hackle.io/ab-test/data-analysis/global-impact.md)
- [A/B 테스트 관리하기](https://docs.hackle.io/ab-test/management.md)
- [공통 영역](https://docs.hackle.io/ab-test/management/ab-detail-top.md)
- [A/B 테스트 설정](https://docs.hackle.io/ab-test/management/ab-settings.md)
- [데이터 분석](https://docs.hackle.io/ab-test/management/analyze-ab-data.md)
- [실시간 노출 현황](https://docs.hackle.io/ab-test/management/realtime-status.md)
- [모니터링 알람](https://docs.hackle.io/ab-test/management/ab-test-monitoring-alarm.md)
- [수동할당](https://docs.hackle.io/ab-test/ab-override.md)
- [목표](https://docs.hackle.io/ab-test/metrics.md)
- [MAB (Multi-Armed Bandit) 테스트](https://docs.hackle.io/ab-test/mab-test.md)
- [MAB 테스트 vs A/B 테스트](https://docs.hackle.io/ab-test/mab-test/mab-vs-ab-test.md)
- [MAB 테스트 생성하기](https://docs.hackle.io/ab-test/mab-test/create-mab-test.md)
- [MAB 성공지표 설정하기](https://docs.hackle.io/ab-test/mab-test/mab-metrics.md)
- [URL 테스트](https://docs.hackle.io/ab-test/url-test.md)
- [URL 테스트 진행 방법](https://docs.hackle.io/ab-test/url-test/steps-of-an-url-test.md)
- [URL 테스트 연동 코드](https://docs.hackle.io/ab-test/url-test/url-test-integration.md)
- [상호 배타적 설정](https://docs.hackle.io/ab-test/mutually-exclusive-group.md)


---

# Agent Instructions: 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:

```
GET https://docs.hackle.io/ab-test.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.