Magify Manager

Overview

MagifyManager is the main entry point to the SDK and provides the entire API to Magify's core functions. Much of the API provides access to raw data without initiating any lengthy processes within the application.

Generally, you may have a need to interact with MagifyManager in case you need to very flexibly customize your application's interaction with Magify.

Initialize Magify

using UnityEngine;
using Magify;

public class MagifyInitializer : MonoBehaviour
{
    private void Start()
    {
        var config = Debug.isDebugBuild
            ? CreateDevConfig()
            : CreateProdConfig();
        MagifyManager.Initialize(config);
    }

    private MagifyConfig CreateDevConfig() => new MagifyConfig
    {
        AppNameIOS = "application_ios",
        ConfigPathIOS = "ConfigIOS.json",
        AppNameGP = "application_gp",
        ConfigPathGP = "ConfigGP.json",
        UseAdvancedVersion = true,
        SyncStateEnabled = true,
        Environment = Environment.Staging,
        IsLoggingEnabled = true,
        SubscriptionStatus = SubscriptionStatus.Paid,
    };

    private MagifyConfig CreateProdConfig() => new MagifyConfig
    {
        AppNameIOS = "application_ios",
        ConfigPathIOS = "ConfigIOS.json",
        AppNameGP = "application_gp",
        ConfigPathGP = "ConfigGP.json",
        UseAdvancedVersion = true,
        SyncStateEnabled = true,
        Environment = Environment.Production,
        SubscriptionStatus = SubscriptionStatus.Inactive,
    };

    private void ApplicationQuittingHandler()
    {
        MagifyManager.ShutDown();
    }
}

Please note that upon completing your interaction with Magify, typically when exiting your application, it's advisable to call the MagifyManager.ShutDown() 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 = MagifyManager.ClientId;

// AppsFlyer
AppsFlyer.setCustomerUserID(clientId);

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

// Adjust
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.