# Page Not Found

The URL `pages/R6E5XOJk7Zw0SKG6tk6M` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [브레인 테스트 : 까다로운 퍼즐, 히든 퀘스트 및 게시판 이벤트 진행으로 누적 ROAS 144.62% 달성](https://playio-ads.gitbook.io/ads/playio_contents/case_studies_kr/roas-144.62.md)
- [[✈️ 글로벌 컨퍼런스  / 26.05.19] MAU Vegas 2026 리뷰: 모바일 게임 UA가 설치 수 너머의 성장으로 이동하다](https://playio-ads.gitbook.io/ads/playio_contents/playio-events/26.05.19-mau-vegas-2026-ua.md)
- [리타겟팅](https://playio-ads.gitbook.io/ads/ad_info/retargeting.md)
- [[👩‍💻웨비나 / 24.11.06] 글로벌 게임 마케팅 트렌드: 일본과 대만 게임 시장 분석](https://playio-ads.gitbook.io/ads/playio_contents/playio-events/24.11.06.md)
- [스팀 (Steam)](https://playio-ads.gitbook.io/ads/ad_info/steam.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter, and the optional `goal` parameter:

```
GET https://playio-ads.gitbook.io/ads/playio_contents/case_studies_kr/roas-144.62.md?ask=<question>&goal=<end_goal>
```

`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.

### Option 2 — Browse the documentation index

Full index: https://playio-ads.gitbook.io/ads/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://playio-ads.gitbook.io/ads/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/ads/playio_contents/case_studies_kr/roas-144.62.md`).

You may also use `Accept: text/markdown` header for content negotiation.