SDK Initialization

Good to know: Magify Advanced

Magify provides a large list of functions, but not all of them are always necessary to get started. That's why a significant part of the functionality is hidden under define MAGIFY_ADVANCED. You can add it at any stage of the project. This will open up the advanced functionality of the SDK for you. Hidden functionality is also labeled in the documentation. Therefore, if you see that you need a feature and it is marked as Advanced, you will need to enable the define symbol beforehand.

Magify settings & Magify Service arguments

Before initializing and working with the SDK, you'll need to prepare two things:

1. Magify settings This is a Scriptable Object that must be created and stored somewhere in your project.
2. Magify Service arguments This is a runtime object with parameters that may vary under different conditions (one set for development builds, another for release builds).

Please review them in the appropriate sections before moving on.

Initialize Magify in runtime

All interactions with the SDK are performed through the MagifyService class. To get started, you need to initialize it using static method MagifyService.Initialize. It takes two parameters Magify settings and Magify Service arguments, which we discussed in the previous section.

using UnityEngine;
using Magify;

public class MagifyInitializer : MonoBehaviour
{
    [SerializeField]
    private MagifySettings _settings;

    private void Start()
    {
        var args = Debug.isDebugBuild ? CreateDevArgs() : CreateProdArgs();
        MagifyService.Initialize(_settings, args);
        Application.quitting += ApplicationQuittingHandler;
    }

    private MagifyServiceArgs CreateDevArgs() => new MagifyServiceArgs
    {
        IsLoggingEnabled = true,
        Environment = Environment.Staging,
    };

    private MagifyServiceArgs CreateProdArgs() => new MagifyServiceArgs
    {
        Environment = Environment.Production,
    };

    private void ApplicationQuittingHandler()
    {
        MagifyService.Terminate();
    }
}

Please note that upon completing your interaction with Magify, typically when exiting your application, it's advisable to call the MagifyService.Terminate() method. This ensures the proper termination of internal processes within the SDK for a clean and graceful conclusion of its operations.

Use ClientId for all integrations

Connect with 3rd party services. If your app has Appsflyer, Adjust, RevenueCat or another sdks, you should initialize them with ClientId provided by Magify:

var clientId = MagifyService.Instance.ClientId;

// AppsFlyer
AppsFlyer.setCustomerUserID(clientId);

// RevenueCat
var purchases = GetComponent<Purchases>();
purchases.appUserID = clientId;

// Adjust
var clientId = MagifyService.Instance.ClientId;
var adjustConfig = new AdjustConfig("{YourAppToken}", yourEnvironment)
{
    ExternalDeviceId = clientId,
};
adjustConfig.SessionSuccessDelegate += success => MagifyManager.AdjustId = success.Adid;
adjustConfig.SessionFailureDelegate += failure => MagifyManager.AdjustId = failure.Adid;
Adjust.AddGlobalCallbackParameter("client_id", clientId);
Adjust.AddGlobalPartnerParameter("client_id", clientId);
Adjust.InitSdk(adjustConfig);
// for old adjust sdk see here: https://magify.atlassian.net/wiki/spaces/GW/pages/1283362/Adjust+sdk

// Crashlytics
Crashlytics.SetUserId(clientId);

// GameAnalytics
GameAnalytics.SetCustomId(clientId);

// Applovin MAX (you don't need to do it if you use Magify.MaxMediator)
MaxSdk.SetUserId(clientId);

// LevelPlay / IronSource (you don't need to do it if you use Magify.LevelPlayMediator)
IronSource.Agent.setUserId(clientId);

// etc.

Next steps

Now you have a fully operational SDK and you can move on to the sections of interest to customize the corresponding functionality:

• Analytics;
• Purchases;
• Advertisement.