Add a device to test your integration:
Test DevicesWhen developing and publishing apps targeted at children under 13 years old, you need to ensure special conditions for data processing.
Check out how to enable compliance mode for Android, iOS, MacOS and Unity.
You can check the incoming events in the User card (Users & Segments section) or in the Event Log (Settings -> SDK -> Integration -> Event Log).
To check events faster, mark the User card as a Tester. This way the log in the User card will not be cached and the events will appear much quicker.
You can change the default revenue rates for your project in Settings -> SDK -> Payments.
If necessary, you can also disable some of the transation checks and set up transaction value limits.
Change LogLevel value to DTDLogLevel.Debug in the Initialization configuration.
Check out examples for different platforms in the Integration section.
Some of the events and properties are sent to devtodev automatically by the SDK.
Event timestamp
Timezone
Tracking status (iOS, Android) – the state of the flag for permission of ad tracking.
App version (must be specified by developer for WEB projects).
devtodev SDK version
Push token – in the case of an additional initialization by the developer and with a user’s permission.
Device manufacturer (iOS, Android)
Device model (iOS, Android)
Language – device’s locale data.
OS type
OS version
Rooted/Jailbreaked OS flag
User agent string
Different device IDs depending on the platform. Disabled when COPPA Control is enabled.
Session start – beginning of application activity with the date.
Activity period – duration of application activity.
The source of app install (only from Google Play), sent once.
Install date – date of the first launch of an application with integrated devtodev SDK.
Last seen date – date of the last incoming query.
IP-address – anonymized IP-address.
Country – defined by IP.
Last updated
Was this helpful?
Was this helpful?
