---
title: "Analytics and data tracking"
description: "Find out what usage data Adyen collects for Drop-in and Components."
url: "https://docs.adyen.com/online-payments/analytics-and-data-tracking"
source_url: "https://docs.adyen.com/online-payments/analytics-and-data-tracking.md"
canonical: "https://docs.adyen.com/online-payments/analytics-and-data-tracking"
last_modified: "2024-10-21T10:19:00+02:00"
language: "en"
---

# Analytics and data tracking

Find out what usage data Adyen collects for Drop-in and Components.

[View source](/online-payments/analytics-and-data-tracking.md)

Drop-in and Components include analytics and tracking features which let us collect usage data about your integration. We use this data to improve the performance of our products and we store it for two years.

## Benefits of data collection

The data we collect will help us to:

* **Optimize the checkout experience.** For example, find out how different device types can affect checkout performance and make improvements where needed.
* **See region and industry specific performance.** For example, identify integration issues with popular payment methods to improve performance and conversion.
* **Compare different integration types you might have.** For example, compare performance to continuously improve the product and the checkout experience for the shopper.

## Data we are collecting

We collect different types of data:

* **Telemetry**

  * Type of integration you are using, that is Drop-in or Components.
  * Version of Drop-in or Components.
  * Platform, that is web, iOS, or Android.
  * For mobile integrations, system version of the shopper's device.
  * Locale, which is the language the shopper sees in the UI, for example en-US.
  * URL for the page where you mounted Drop-in or Components.
  * Payment methods rendered on Drop-in.
  * Components you are using.
  * [User agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent).
  * Payment amount and currency.
  * Web Drop-in/Components build type, that is Universal Module Definition (UMD), or compiled.

* **[Checkout attempt identifier](#checkout-attempt-identifier)**
  * Using the checkout attempt identifier, we link the telemetry data to the payment data. We are not using cookies to collect analytics data.

* **Drop-in/Components analytics**

  * Front end errors, like payment form input errors.
  * Shopper events, like scanning a QR code for a payment, or authenticating with 3D Secure 2.

Check with your legal counsel if in your country or region the collection of this data needs to be added to your privacy or cookie policy.

## Versions with data collection features

Data collection is turned on by default for the versions that support this feature. If you use the [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) endpoint, you must also include the [checkout attempt identifier](#checkout-attempt-identifier) in your payment requests.

The table below shows the supported types of data collection for each platform.

| Platform                        | Telemetry and checkout attempt identifier                                                                                                                                                                                                                            | Drop-in/Components analytics                                                                                                                                                                                                        |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Web Drop-in/Components          | [v5.16.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=5.16.0) or later Build type is only collected for [v6.2.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=6.2.0) or later | [v5.69.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=5.69.0) or later [v6.2.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=6.2.0) or later |
| iOS Drop-in/Component           | [v5.0.0](/online-payments/release-notes/?title%5B0%5D=iOS%20Components%2FDrop-in\&version%5B0%5D=5.0.0#releaseNote=2022-11-01-ios-componentsdrop-in-5.0.0) or later                                                                                                  | [v5.12.0](/online-payments/release-notes/?title%5B0%5D=iOS%20Components%2FDrop-in\&version%5B0%5D=5.12.0) or later                                                                                                                  |
| Android Drop-in/Components      | [v5.0.0](/online-payments/release-notes/?title%5B0%5D=Android%20Components%2FDrop-in\&version%5B0%5D=5.0.0) or later                                                                                                                                                 | [v5.7.0](/online-payments/release-notes/?title%5B0%5D=Android%20Components%2FDrop-in\&version%5B0%5D=5.7.0) or later                                                                                                                |
| React Native Drop-in/Components | [v1.0.0](/online-payments/release-notes/?=1\&title%5B0%5D=React%20Native%20Components%2FDrop-in\&version%5B0%5D=1.1.0#releaseNote=2023-08-01-react-native-componentsdrop-in-1.1.0) or later                                                                          |                                                                                                                                                                                                                                     |
| Flutter Drop-in/Components      | [v1.0.0](/online-payments/release-notes/?title%5B0%5D=Flutter%20Components%2FDrop-in\&version%5B0%5D=1.0.2) or later                                                                                                                                                 |                                                                                                                                                                                                                                     |

### Checkout attempt identifier

The checkout attempt identifier is a unique identifier which links the payment data to the telemetry data. This identifier contains the data required for the [Checkout dashboard](/uplift#uplift-dashboards) that lets you analyze your checkout performance. For Web integrations, it also lets you use the [Adyen Uplift Personalize module](/uplift#uplift-personalize).

If your integration uses the [/sessions](https://docs.adyen.com/api-explorer/Checkout/latest/post/sessions) endpoint, the checkout attempt identifier is sent automatically with the payment request.

If your integration uses the [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) endpoint:

* Newer versions of Drop-in/Components include the `sdkData` field that includes the `checkoutAttemptId`, and you no longer have to forward the identifier separately. You pass the `sdkData` when making a [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) request with your [integration](/online-payments/build-your-integration/advanced-flow). This is currently supported on:

  * Web [v6.29.0](/release-notes?title%5B0%5D=Web%2BComponents%2FDrop-in\&version%5B0%5D=6.29.0)
  * iOS [v5.22.0](/online-payments/release-notes#releaseNote=2025-12-18-ios-componentsdrop-in-5.22.0) or later
  * Android [v5.16.0](/online-payments/release-notes#releaseNote=2025-12-19-android-componentsdrop-in-5.16.0) or later
  * React Native [v2.9.0](/online-payments/release-notes?title%5B0%5D=React%2BNative%2BComponents%2FDrop-in\&version%5B0%5D=2.9.0)
  * Flutter [v1.8.0](/online-payments/release-notes?title%5B0%5D=Flutter%2BComponents%2FDrop-in\&version%5B0%5D=1.8.0)

* On earlier versions, you must get the `checkoutAttemptId` from your front end and include it in the [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) request you make from your server.

## Configure data collection

Analytics data collection is enabled by default. You can [configure](#configure) what data we are allowed to collect for each of your integrations:

### Tab: Web

| Parameter           | Description                                                                                                                                                                                                                                                                                                                                                                                                                     | Default  |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| `analytics.enabled` | Indicates if you are sending analytics data to Adyen. From [v5.69.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=5.69.0) or [v6.2.0](/online-payments/release-notes/?title%5B0%5D=Web%20Components%2FDrop-in\&version%5B0%5D=6.2.0) or later, telemetry and checkout attempt identifier are always sent to Adyen, this configuration only impacts the Drop-in/Components analytics. | **true** |

**Configuration for analytics data collection on Web**

```js
const configuration = {
   environment: 'test',
   clientKey: 'test_...',
   analytics: {
      enabled: true // Set to false to not send analytics data to Adyen.
   }
   // Other global configuration...
};
```

### Tab: iOS

| Parameter   | Description                                                                                                                                                                                                                                                                                                   | Default  |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| `isEnabled` | Indicates if you send analytics data to Adyen. From [v5.12.0](/online-payments/release-notes/?title%5B0%5D=iOS%20Components%2FDrop-in\&version%5B0%5D=5.12.0) or later, telemetry and checkout attempt identifier are always sent to Adyen, this configuration only impacts the Drop-in/Components analytics. | **true** |

**Configuration for analytics data collection on iOS**

```swift
// Create an analytics configuration object.
var analyticsConfiguration = AnalyticsConfiguration()
// Add the isEnabled configuration parameter.
analyticsConfiguration.isEnabled = true // Set to false to not send analytics data to Adyen.

// Add the analyticsConfiguration when creating your context.
let adyenContext = AdyenContext(apiContext: apiContext, analyticsConfiguration: analyticsConfiguration)
```

### Tab: Android

| Parameter                                                                                                                                                                                | Description                                                                                                                                                                                                                                                                                                           | Default                                        |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| [`analyticsConfiguration`](https://adyen.github.io/adyen-android/components-core/com.adyen.checkout.components.core.internal/-configuration/index.html#-1107459355/Properties/339477935) | Indicates what analytics data you send to Adyen. From [v5.7.0](/online-payments/release-notes/?title%5B0%5D=Android%20Components%2FDrop-in\&version%5B0%5D=5.7.0) or later, telemetry and checkout attempt identifier are always sent to Adyen, and this configuration only impacts the Drop-in/Components analytics. | **AnalyticsConfiguration(AnalyticsLevel.ALL)** |

**Configuration for analytics data collection on Android**

```java
CheckoutConfiguration(
   environment = environment,
   clientKey = clientKey,
   analyticsConfiguration = AnalyticsConfiguration(AnalyticsLevel.ALL), // Set to AnalyticsLevel.NONE to not send analytics data to Adyen.
   // Other configuration...
)
```

### Tab: React Native

| Parameter | Description                                    | Default  |
| --------- | ---------------------------------------------- | -------- |
| `enabled` | Indicates if you send analytics data to Adyen. | **true** |

**Configuration for analytics data collection on React Native**

```js
const analyticsOptions =  {
   enabled: true, // Set to false to not send analytics data to Adyen.
};

const configuration = {
   environment: 'test',
   clientKey: 'YOUR_CLIENT_KEY',
   analytics: analyticsOptions,
   // Other global configuration...
};
```

### Tab: Flutter

| Parameter | Description                                    | Default  |
| --------- | ---------------------------------------------- | -------- |
| `enabled` | Indicates if you send analytics data to Adyen. | **true** |

**Configuration for analytics data collection on Flutter**

```js
final AnalyticsOptions analyticsOptions = AnalyticsOptions(
   enabled: true, // Set to false to not send analytics data to Adyen.
);

final DropInConfiguration dropInConfiguration = DropInConfiguration(
    environment: 'test',
    clientKey: 'YOUR_CLIENT_KEY',
    countryCode: 'YOUR_COUNTRY_CODE',
    analyticsOptions: analyticsOptions
   // Other  configuration...
);
```

## Collect additional data to detect fraud

For Web Drop-in/Components integrations, you can optionally [collect data to detect fraud](/risk-management/fraud-data-collection) outside of the checkout page, in addition to the data that you send when the shopper checks out. We recommend that you collect data about the shopper's activity on every page of your site.

To do this, add the following script to any of your web pages.

**Data collection script**

```javascript
<script src="https://checkoutshopper-live.adyen.com/checkoutshopper/assets/js/datacollection/datacollection.js"></script>
```

When the shopper checks out, Drop-in or the Component sends all of the data collected by the script to Adyen. This includes the data from the checkout page as well as any data collected from other web pages that contain the script.

## See also

* [Data collection to detect fraud](/risk-management/fraud-data-collection/)
