> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/3rd-party-sources/ad-revenue/unity.md).

# Unity Ads

## Unity settings

You will need **Organization Core Id**, **Game Id** and **Reporting API Key** to integrate Unity Ads.

Go to [Dashboard](<https://operate.dashboard.unity3d.com/ >) and click Settings in the left menu, you will find **Organization Core Id** in organization settings:

![](https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LnGcP_ZeRJ1ipj9O8dF%2F-M7CeR2houv0Q_QiG5NU%2F-M7CiDqUeoNNUngmviYJ%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202020-05-13%20%D0%B2%2014.08.32.png?alt=media\&token=8363a641-3d9a-479c-bb3d-df4048a7bf49)

Go to Ads Data Export -> API access in the left menu next and create new **Monetization Stats API Access** key, this is your **Reporting API Key**:

![](https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LnGcP_ZeRJ1ipj9O8dF%2F-M7CeR2houv0Q_QiG5NU%2F-M7CifS7V2xiHKqo4ed2%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202020-05-13%20%D0%B2%2014.10.28.png?alt=media\&token=f5b54dab-7334-4813-8efe-d428381bfef2)

Go to Projects -> Select your projects and click Settings -> Project settings in the left menu, you will find **Game ID** for corresponding platform here:

![](https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LnGcP_ZeRJ1ipj9O8dF%2F-M7CeR2houv0Q_QiG5NU%2F-M7CjF_KwslOBA39aFDR%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202020-05-13%20%D0%B2%2014.11.33.png?alt=media\&token=a05a14cf-1d69-41bd-b045-eb59ba16af5b)

## devtodev settings

Go to Settings -> 3rd party sources -> Ad revenue, fill in Organization Core Id, Game Id and Reporting API Key.

Save settings and enable the integration.

<figure><img src="https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnGcP_ZeRJ1ipj9O8dF%2Fuploads%2FxUOQiruMTBVKdb6iWZjk%2Fimage.png?alt=media&amp;token=4170a69f-7b2f-4fc8-bbff-b4f0bf3f3c85" alt=""><figcaption></figcaption></figure>


---

# 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://docs.devtodev.com/3rd-party-sources/ad-revenue/unity.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.