# Data Collection Guidance
source: https://developer.mastercard.com/identity-insights-for-transactions/documentation/tutorials-and-guides/data-collection-tutorial/index.md

## Overview {#overview}

IIT is capable of providing insights across the following classifications:

1. **Individual Insights** -- those details that the end user inputs directly into various forms hosted on the merchant's website or application.
2. **Payment Insights** -- those details that are related to the transaction being conducted. The values associated to these elements should align to the 3DS specification.
3. **Device Insights** -- those details that can be collected by the Merchant from the application/browser the user is using to interact with their service. The values associated to these elements should align to the 3DS specification.

## Individual Insights {#individual-insights}

These values should be passed to IIT as received from the user in the request field(s) that is most appropriate to the nature of the data being passed. For values such as address, that are made up of multiple individual fields, the application calling IIT should parse the values in a way that best adheres to the API validation.

## Payment Insights {#payment-insights}

Payment Insights are those details that are related to the transaction being conducted.
The values associated to these elements should align to the **3DS specification**.

## Device Insights {#device-insights}

Device Insights are those details that can be collected by the Merchant from the application or browser the user is using to interact with their service.
The values associated to these elements should align to the **3DS specification**.

The **[Device - Input Data Collection Guide](https://static.developer.mastercard.com/content/identity-insights-for-transactions/InputDataCollectionGuide.pdf)** provides guidance and sample code detailing how device-specific fields can be best collected from:

1. **Web Applications**
2. **Android Native Applications**
3. **iOS Native Applications**