> For the complete documentation index, see [llms.txt](https://support.happydemics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.happydemics.com/methodology/media-formats-and-targeting-strategies/media-channels-and-formats/in-game.md).

# In-game

In-game advertising is a media channel that places ads directly within video games, most commonly on mobile devices. These ads come in various formats that are closely tied to the gaming experience—whether it’s earning extra lives by watching a video, spotting a branded message integrated into gameplay, or hearing an audio ad between levels. In-game placements allow your messaging to reach players in an engaging and interactive environment.

<figure><img src="/files/7wKrg4rRhL3wiKTB35fb" alt=""><figcaption><p>In-game formats</p></figcaption></figure>

**Available formats:**

* **Banner:** Ads displayed within the game interface, often appearing in the corner or at the bottom of the screen. *Example: A small banner ad shown at the bottom of a mobile game screen.*
* **Video:** Video ads that play during gameplay, such as interstitials or pre-rolls. *Example: A 15-second video ad that appears before a player continues with the game.*
* **Audio:** Audio-only ads played during the gaming experience or between levels, offering a non-intrusive way to reach players. *Example: A brief audio ad playing like a radio spot during a driving game.*
* **Rewarded ads:** Ads that users can choose to watch in exchange for in-game rewards like currency, bonuses, or extra lives. *Example: A player watches a video ad to receive a bonus or additional lives in the game.*

**Targeting strategies supported:** Contextual, behavioral, demographic, and geographic


---

# 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://support.happydemics.com/methodology/media-formats-and-targeting-strategies/media-channels-and-formats/in-game.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.