> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/userguide/playlist.md).

# 재생목록

재생목록은 여러 개의 샵 플레이어를 묶어 만든 목록을 말해요. 신상품이나 기획전 같은 특정 주제 맞춰 선택한 샵 플레이어를 위, 아래로 스와이프하여 연속적으로 재생할 수 있어요. 자사몰에서 만든 숏폼 콘텐츠를 시청자들에게 끊임없이 전달하여 쇼핑몰 체류시간과 구매 전환을 높여보세요.

<figure><img src="https://1296347489-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLKEFnVmIYlmffzSBEtw1%2Fuploads%2F8miYT8cll2yPhjzMeCRs%2F%E1%84%8C%E1%85%A2%E1%84%89%E1%85%A2%E1%86%BC%E1%84%86%E1%85%A9%E1%86%A8%E1%84%85%E1%85%A9%E1%86%A8%20%E1%84%8F%E1%85%A1%E1%84%83%E1%85%B3.png?alt=media&amp;token=2912d684-4171-49da-af38-310aac55b4a6" alt=""><figcaption></figcaption></figure>

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th>정보</th><th></th></tr></thead><tbody><tr><td><mark style="color:purple;"><strong>정보</strong></mark></td><td><ul><li>썸네일(Thumbnail)</li><li>재생목록 제목</li><li>재생목록 생성자 </li><li>재생목록 생성일</li></ul></td></tr><tr><td><mark style="color:purple;"><strong>기능</strong></mark></td><td><ul><li>재생목록 정렬 (최신순, 오래된순)</li><li>재생목록 카드 링크 복사</li><li>재생목록 카드 코드 복사</li><li>삭제</li></ul></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.charlla.io/userguide/playlist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
