> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# SDK Initialization

> Attach the MoEGameObject script to your Unity scene and configure your MoEngage App ID.

# Unity Initialization

In your Unity project, add an empty game object to the first scene, attach the ***MoEGameObject.cs*** script, and set the ***App ID*** as shown below

<Frame>
  <img src="https://mintcdn.com/moengage/b13dNrqwcDhjET-m/images/SDKIntialization1.png?fit=max&auto=format&n=b13dNrqwcDhjET-m&q=85&s=430632ccbc3c70a12eb0246084368221" alt="SDK Intialization1" width="1228" height="950" data-path="images/SDKIntialization1.png" />
</Frame>

<Frame>
  <img src="https://mintcdn.com/moengage/b13dNrqwcDhjET-m/images/SDKIntialization.png?fit=max&auto=format&n=b13dNrqwcDhjET-m&q=85&s=5e501f72f7db79744e492ae0a5d957af" alt="SDK Intialization" width="3584" height="1052" data-path="images/SDKIntialization.png" />
</Frame>

\
MoEngage supports two ways to initialize the SDK: manually in code, or through a native configuration file.

<Info>
  Unity iOS SDK supports file-based initialization only. Manual initialization is available for Android only.
</Info>

## Manual Initialization

Initialize the SDK programmatically in your Android Application class.

* [Android](/docs/developer-guide/unity-sdk/sdk-integration/sdk-initialization/manual-initialization/android)

## File Based Initialization

Initialize the SDK using a native configuration file, keeping the Workspace ID and settings separate from your application logic.

* [Android](/docs/developer-guide/unity-sdk/sdk-integration/sdk-initialization/file-based-initialization/android)
* [iOS](/docs/developer-guide/unity-sdk/sdk-integration/sdk-initialization/file-based-initialization/ios)