> For the complete documentation index, see [llms.txt](https://sdk-doc.tyrads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk-doc.tyrads.com/unity/sdk-integration.md).

# SDK Integration

{% hint style="warning" %}

#### Initialize After Media Source or MMP Initialization

Please initialize our SDK only after the media source or MMP data is initialized. This ensures that the media source data is sent correctly and prevents passing empty values.
{% endhint %}

Integrating the TyrAds offerwall functionality into your application is a straightforward process that involves a few key steps. By following these integration steps, you can seamlessly incorporate the offerwall feature, enhancing user engagement and potentially generating additional revenue for your application.

{% hint style="success" %}

### SDK Initialization best practices:

* **Initiate early:** It's advisable to initialize the SDK promptly after your app launches to ensure that all Tyr SDK functionalities are accessible when needed.
* **Initiate authentication:** Login to the SDK with current user details immediately after your user signs up or signs in to the app to set the `userId`.
  {% endhint %}

For guidance on integrating TyrSDK - including proper initialization and offer display - see the example at `Sample -> Demo` .

{% content-ref url="/pages/C5oroS3PgljSCzwOiFHY" %}
[1. Scene setup](/unity/sdk-integration/1.-scene-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/ee4vv0lA2xdWlfF5Ez0F" %}
[2. Credentials setup](/unity/sdk-integration/2.-credentials-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/vkqc6mSx3kLE6MvR4FNW" %}
[3. User Login](/unity/sdk-integration/3.-user-login.md)
{% endcontent-ref %}

{% content-ref url="/pages/JoqyAJ76vQgUxOh0cWWC" %}
[4. Open Offerswall](/unity/sdk-integration/4.-open-offerswall.md)
{% endcontent-ref %}

{% content-ref url="/pages/DE8K1fJ6bfrZk1c9I6Aa" %}
[5. Configure SDK Initialization Wizard](/unity/sdk-integration/5.-configure-sdk-initialization-wizard.md)
{% endcontent-ref %}

{% content-ref url="/pages/LXFW8RaZTpFMjxSBxZGH" %}
[6. Change Language](/unity/sdk-integration/6.-change-language.md)
{% endcontent-ref %}

{% content-ref url="/pages/vVH7Qd9vmu0SSKixNsLm" %}
[7. Setup Required Android Permissions](/unity/sdk-integration/7.-setup-required-android-permissions.md)
{% endcontent-ref %}

{% content-ref url="/pages/XH10SeB3H0Z4abwHhgOZ" %}
[8. Obtaining Advertising ID's](/unity/sdk-integration/8.-obtaining-advertising-ids.md)
{% endcontent-ref %}


---

# 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://sdk-doc.tyrads.com/unity/sdk-integration.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.