Unity
Last updated
Last updated
This SDK version does not support WebGL. WebGL support will be added in the next releases.
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:
1. Import the DTDAnalytics.unitypackage
from GitHub repository.
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.
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 |
| Integer | The player level at the moment of devtodev SDK initialization. It’s optional but we recommend using it for improving data accuracy. |
| 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. |
| DTDTrackingStatus (enum) | The property allows or disallows devtodev tracking of the user. By default, it is set to |
| DTDLogLevel (enum) | The level of logging the SDK activity. The |
| 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:
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.
Add the following strings to proguard.txt (read more about Unity proguard here):
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.
Your app must request tracking authorization before it can get the advertising identifier. See the detailed instruction on how to request it.
If you want to disable tracking of advertising identifiers, you need to open the DTDPostProcesssAnalytics.cs
file and comment out the line 39
.