# Check your integration

## Test devices 

Add a device to test your integration:

{% content-ref url="../test-devices" %}
[test-devices](https://docs.devtodev.com/integration/test-devices)
{% endcontent-ref %}

## Apps targeted at children 

When 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](https://docs.devtodev.com/integration-of-sdk-v2/sdk-integration/android#apps-targeted-at-children), [iOS](https://docs.devtodev.com/integration-of-sdk-v2/sdk-integration/ios#apps-targeted-at-children), [MacOS](https://docs.devtodev.com/integration-of-sdk-v2/sdk-integration/macos#apps-targeted-at-children) and [Unity](https://docs.devtodev.com/integration-of-sdk-v2/sdk-integration/unity#apps-targeted-at-children).

## How to check event logs in devtodev interface 

You can check the incoming events in the User card ([Users & Segments section](https://docs.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/users#users)) or in the [Event Log](https://docs.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/settings#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. 

## Configure Revenue rates and transaction checks

You can change the default revenue rates for your project in Settings -> SDK -> [Payments](https://docs.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/settings#payments-settings). 

If necessary, you can also disable some of the [transation checks](https://docs.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/settings#transaction-checking-terms) and set up transaction value limits.

## How to enable SDK debug logs

Change `LogLevel` value to `DTDLogLevel.Debug` in the Initialization configuration. 

Check out examples for different platforms in the [Integration](https://docs.devtodev.com/integration/integration-of-sdk-v2/sdk-integration) section.

## Data collected by devtodev automatically 

Some of the events and properties are sent to devtodev automatically by the SDK. 

### Information about a device/user: 

* 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](#apps-targeted-at-children) is enabled.

### Automatically sent events:

* **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.

### Data received by the server from queries’ metadata 

* **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.