> 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/integration/integration-of-sdk-v2/push-notifications/unity.md).

# Unity

## General Information

In order to work with push notifications, you need to integrate the *messaging* module. You can do it by using one of the two methods: with the help of the *Unity Package Manager* (recommended) or by manually importing the *unitypackage*.

### **Integration by using the Unity Package Manager**

{% hint style="warning" %}
If you integrated the devtodev package manually, then you need to delete the Assets/DevToDev and Plugins/DevToDev folders.
{% endhint %}

1. In the Package Manager (Window → Package Manager), click + in the top left corner and select *Add package from git UR*L.
2. Copy the repository URL <https://github.com/devtodev-analytics/package_Messaging.git> to the input box and click *Add*.

   <figure><img src="/files/yhdO04ho426S060Sxib4" alt=""><figcaption></figcaption></figure>
3. Wait for the Unity Package Manager to download the package and all the necessary dependencies.
4. If you use Android, allow dependencies in Assets → External Dependency Manager → Android Resolver → Resolve.

{% hint style="info" %}
You can pick a specific SDK version by adding # and a version number at the end of the URL, for example: <https://github.com/devtodev-analytics/package_Messaging.git#v3.3.2>
{% endhint %}

### **Integration by importing&#x20;*****unitypackage***

1. Download the latest version of devtodev package from the repository: <https://github.com/devtodev-analytics/Unity-sdk-3.0/releases/latest>
2. Import DTDAnalytics.unitypackage to your project
3. Import DTDMessaging.unitypackage to your project
4. If you use Android, allow dependencies in Assets → External Dependency Manager → Android Resolver → Resolve.

![](https://lh3.googleusercontent.com/_SdzNiRPJM_bi6HwZdR4zp_GqjKJELgPARR3aXNmsfATEVswaIgwtKsaTxTm-nVzRX16lINih8VZ_aKoVk5ThzsdBBbTXeGUQum94L35DDexbRrVd2HFNSpeDL0NXeKc4C8Di9UQ=s0)

## Platform specific integration

{% content-ref url="/pages/6s5F6vkBrtmBCeGbvaNx" %}
[Android](/integration/integration-of-sdk-v2/push-notifications/unity/android.md)
{% endcontent-ref %}

{% content-ref url="/pages/7S0Kv77M1UHQPsWScp03" %}
[iOS](/integration/integration-of-sdk-v2/push-notifications/unity/ios.md)
{% endcontent-ref %}

{% content-ref url="/pages/odw2uYQyQmuUpk4cXj73" %}
[Windows (UWP/WSA)](/integration/integration-of-sdk-v2/push-notifications/unity/windows-uwp-wsa.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://docs.devtodev.com/integration/integration-of-sdk-v2/push-notifications/unity.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.