> For the complete documentation index, see [llms.txt](https://docs.reneverse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reneverse.io/publisher-flow/sdk-integration/unreal-engine/ue-sdk-setup.md).

# UE SDK Setup

### 📦 Step 1: Install the Plugin

{% hint style="warning" %}
If you are planning to develop you game for Android and submit it to store, please take into account minimal Android SDK requirements and Unreal Engine version that support it. For more information you can consult [Unreal Engine official documentation](https://dev.epicgames.com/documentation/en-us/unreal-engine/android-development-requirements-for-unreal-engine). Download ReneVerse SDK version accordingly.  
{% endhint %}

1. Download the Unreal SDK [here](/download/unreal-engine-sdk.md).
2. Move the unzipped **ReneVerseSDK** folder into your project’s `/Plugins` directory.

<figure><img src="/files/xF8Uof4ByhPb083oCEzM" alt=""><figcaption><p>If the <strong>Plugins</strong> folder is not already created, create one yourself.</p></figcaption></figure>

3. Rebuild or relaunch your project.

***

### ✅ Step 2: Enable the Plugin

1. In Unreal, go to **Edit → Plugins**.
2. Search for **ReneVerseSDK** and ensure it's enabled.

<figure><img src="/files/3XRAgT9yRlJMd9tnKlIE" alt=""><figcaption><p>Search and enable <strong>ReneVerseSDK</strong></p></figcaption></figure>

***

### 🔐 Step 3: Enter API Credentials

1. Open **Window → ReneVerse API Editor**.

<figure><img src="/files/SSdkdzh8bcte3F7kxSn9" alt=""><figcaption><p>ReneVerse API Editor</p></figcaption></figure>

2. Paste your **API Key** and **Private Key** from the ReneVerse Portal to sync the data you created for your [game in the ReneVerse Portal](/publisher-flow/registering-your-game-and-generating-api-keys.md).

<figure><img src="/files/s0R9nC3Afek60DNVokd1" alt=""><figcaption><p>Enter keys from the Portal and click <strong>Sync Data</strong>.</p></figcaption></figure>

{% hint style="warning" %}
In case you missed the previous step of [generating your API Credentials](/publisher-flow/registering-your-game-and-generating-api-keys.md), you must register your game and create API Credentials.
{% endhint %}

3. Click **Sync Data** to pull in your ad surfaces and branded object placements.

This will generate a `ReneAPIData` asset and two data tables inside a new **ReneVerse** folder in your project’s `/Content` directory. These assets hold data for the Ad Surface and Branded Object placements for your game, as well as your credentials.

<figure><img src="/files/5fSwD3iDXVpaKtZbT00w" alt=""><figcaption><p><strong>ReneVerse</strong> folder and contents should be kept in the root of your <strong>Content</strong> folder.</p></figcaption></figure>

{% hint style="danger" %}
🗂️ These hold your synced ad data and credentials—don’t move them!
{% endhint %}

Once synced, you're ready to start integrating ads into your scene.


---

# 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.reneverse.io/publisher-flow/sdk-integration/unreal-engine/ue-sdk-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.