> For the complete documentation index, see [llms.txt](https://docs.candy-smith.com/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candy-smith.com/main/bubble-shooter-toolkit/tutorials/ads-setup/unit-ads-legacy-setup.md).

# Unit ads legacy setup

{% hint style="info" %}
Unity recommended to use Ads mediation, it will help to maximize the ad monetization of app publishers by increasing their display ad fill rates. But if you not going to use ads mediation you can setup Unity ads separately
{% endhint %}

{% hint style="warning" %}
Unity ads have legacy status and will no longer regularly updated. [more info](https://docs.unity.com/ads/en-us/manual/UnityAdsHome)
{% endhint %}

## Setup

* Copy the game id from the Unity ads account and put it into [Ads settings](/main/bubble-shooter-toolkit/tutorials/ads-setup/ads-settings.md) into appropreate profile


---

# 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://docs.candy-smith.com/main/bubble-shooter-toolkit/tutorials/ads-setup/unit-ads-legacy-setup.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.