> For the complete documentation index, see [llms.txt](https://tvingads.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tvingads.gitbook.io/guide/solution/kbo/sponsorship/inning-highlight-v-ad.md).

# 이닝 하이라이트 가상광고

<figure><img src="https://1255383138-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPFaEnKc0G69Yys4xNPMD%2Fuploads%2FfuSJsVuhjgXAk7gwZG5r%2Fimage.png?alt=media&amp;token=f4a8feed-fd5c-4e99-841e-84d484d35601" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**이닝 하이라이트 구간에 하단 배너 영역을 활용해 광고주 로고 및 슬로건을 노출하는 가상광고 상품**
{% endhint %}

<table data-first-column-sticky><thead><tr><th width="121">구분</th><th>내용</th></tr></thead><tbody><tr><td><strong>대상프로그램</strong></td><td><ul><li><strong>슈퍼매치 only</strong></li></ul></td></tr><tr><td><strong>상품 특징</strong></td><td><ul><li>경기 핵심 장면인 이닝별 주요 플레이 및 하이라이트에 노출하여 높은 주목도와 광고 집중도 확보 가능</li></ul></td></tr><tr><td><strong>노출 횟수</strong></td><td><ul><li><strong>4주간 약 48회 노출 / 경기당 6회</strong></li></ul></td></tr><tr><td><strong>상품 단가</strong></td><td><ul><li><strong>5천만 원/월</strong></li><li><strong>월 1구좌 한정</strong></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://tvingads.gitbook.io/guide/solution/kbo/sponsorship/inning-highlight-v-ad.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.