Unity

SDK Initialization

If you have previously used the Unity SDK version 2+, you need to delete the following files and folders in the "Assets" folder of your project:
Attention! When importing to Unity 2020, you may face the following error:
Assembly 'Assets/Plugins/DevToDev/Analytics/Windows/AnalyticsWindowsEditor.dll' will not be loaded due to errors: AnalyticsWindowsEditor references strong named Newtonsoft.Json Assembly references: 13.0.0.0 Found in project: 12.0.0.0. Assembly Version Validation can be disabled in Player Settings "Assembly Version Validation"
The error might occur due to the conflict between our package’s NewtonsoftJson dependency version and the one used in the VersionControl package. There are two ways to resolve this issue:
A. If you don’t use the VersionControl package, remove it from the package list. Choose Window->Package Manager in the Unity window:
In the window that appears, choose Packages: In Project from a drop-down list at the top. After that, select Version Control from the package list and click Remove.
B. If you use Unity’s Version Control, you need to replace the newtonsoft.Json package. Open the directory of your main project (the one you want to integrate analytics with) MainProject\Library\PackageCache\ and move the com.unity.nuget.newtonsoft-json folder to the MainProject\Packages\ folder. It should look something like this:
2. Create a script with the following code and attach it to the GameObject that will survive the entire life cycle of the app.
1
using DevToDev.Analytics;
2
using UnityEngine;
3
4
public class DTDObject : MonoBehaviour
5
{
6
void Start()
7
{
8
#if UNITY_ANDROID
9
DTDAnalytics.Initialize("androidAppID", config);
10
#elif UNITY_IOS
11
DTDAnalytics.Initialize("IosAppID", config);
12
#elif UNITY_WEBGL
13
DTDAnalytics.Initialize("WebAppID", config);
14
#elif UNITY_STANDALONE_WIN
15
DTDAnalytics.Initialize("winAppID", config);
16
#elif UNITY_STANDALONE_OSX
17
DTDAnalytics.Initialize("OsxAppID", config);
18
#elif UNITY_WSA
19
DTDAnalytics.Initialize("UwpAppID", config);
20
#endif
21
}
22
}
Copied!
  • You can find the AppID in the settings of the respective app in devtodev (Settings → SDK → Integration → Credentials).
  • config - an object instance of DTDAnalyticsConfiguration, which is used for specifying additional properties during the initialization.
DTDAnalyticsConfiguration
Parameter
Type
Description
CurrentLevel
Integer
The player level at the moment of devtodev SDK initialization. It’s optional but we recommend using it for improving data accuracy.
UserId
String
A custom user ID assigned by the developer. In the case of default calculation by device IDs, the identifier can be used for searching users in devtodev. In case the project uses calculation by user IDs, the parameter is mandatory because it becomes the principal calculation ID in devtodev.
TrackingAvailability
DTDTrackingStatus (enum)
The property allows or disallows devtodev tracking of the user. By default, it is set to DTDTrackingStatus.Enable. SDK stores the previously assigned value. Pass DTDTrackingStatus.Disable if the user opted out of tracking in line with GDPR.
LogLevel
DTDLogLevel (enum)
The level of logging the SDK activity. The DTDLogLevel.No value is used by default. For troubleshooting during integration, it is recommended to set it to DTDLogLevel.Debug, and either switch it off DTDLogLevel.No or use it only for error handling DTDLogLevel.Error in the release version.
ApplicationVersion
String
The app version during the devtodev SDK initialization. Use the property on the WinStandalone platform only. For all other platforms, data is collected automatically.
Example:
1
var config = new DTDAnalyticsConfiguration
2
{
3
ApplicationVersion = "1.2.3",
4
LogLevel = DTDLogLevel.Debug,
5
TrackingAvailability = DTDTrackingStatus.Enable,
6
CurrentLevel = 1,
7
UserId = "unique_userId"
8
};
9
DTDAnalytics.Initialize("androidAppId",config);
Copied!

Specific integration features of certain platforms

Windows Standalone

SDK Activity
The SDK can’t control app activity in case you use Windows Standalone therefore this responsibility is shifted to the developer. While initializing the SDK, the activity starts automatically and after that, the activity status will not auto-change. To track app activity, the developer can use the following methods: DTDAnalytics.StartActivity and DTDAnalytics.StopActivity. It is recommended to use the DTDAnalytics.StopActivity method to stop activity when the app goes into the background or gets closed. You can use the DTDAnalytics.StartActivity method to resume activity when the app gets reopened from the taskbar.
For other platforms, there is no need to manually call the DTDAnalytics.StartActivity and DTDAnalytics.StopActivity methods.

Android

Add the following strings to proguard.txt (read more about Unity proguard here):
1
-keep class com.devtodev.** { *; }
2
-dontwarn com.devtodev.**
Copied!

iOS

To integrate with Xcode, the SDK uses PostProcessBuild in the DTDPostProcessAnalytics and DTDPostProcessMessaging scripts. If you use custom PostProcessBuild scripts, add them callbackOrder of less than 98 to avoid conflicts.
Last modified 30d ago