{"title":"Analytics and data tracking","category":"default","creationDate":1677854460,"content":"<p>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.<\/p>\n<h2>Benefits of data collection<\/h2>\n<p>The data we collect will help us to:<\/p>\n<ul>\n<li><strong>Optimize the checkout experience.<\/strong> For example, find out how different device types can affect checkout performance and make improvements where needed.<\/li>\n<li><strong>See region and industry specific performance.<\/strong> For example, identify integration issues with popular payment methods to improve performance and conversion.<\/li>\n<li><strong>Compare different integration types you might have.<\/strong> For example, compare performance to continuously improve the product and the checkout experience for the shopper.<\/li>\n<\/ul>\n<h2>Data we are collecting<\/h2>\n<p>We collect different types of data:<\/p>\n<ul>\n<li><strong>Telemetry<\/strong>\n<ul>\n<li>Type of integration you are using, that is Drop-in or Components.<\/li>\n<li>Version of Drop-in or Components.<\/li>\n<li>Platform, that is web, iOS, or Android.<\/li>\n<li>For mobile integrations, system version of the shopper's device.<\/li>\n<li>Locale, which is the language the shopper sees in the UI, for example en-US.<\/li>\n<li>URL for the page where you mounted Drop-in or Components.<\/li>\n<li>Payment methods rendered on Drop-in.<\/li>\n<li>Components you are using.<\/li>\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Headers\/User-Agent\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">User agent<\/a>.<\/li>\n<li>Payment amount and currency.<\/li>\n<li>Web Drop-in\/Components build type, that is  Universal Module Definition (UMD), or compiled.<\/li>\n<\/ul><\/li>\n<li><strong><a href=\"#checkout-attempt-identifier\">Checkout attempt identifier<\/a><\/strong>\n<ul>\n<li>Using the checkout attempt identifier, we link the telemetry data to the payment data. We are not using cookies to collect analytics data.<\/li>\n<\/ul><\/li>\n<li><strong>Drop-in\/Components analytics<\/strong>\n<ul>\n<li>Front end errors, like payment form input errors.<\/li>\n<li>Shopper events, like scanning a QR code for a payment, or authenticating with 3D Secure 2.<\/li>\n<\/ul><\/li>\n<\/ul>\n<div class=\"notices yellow\">\n<p>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.<\/p>\n<\/div>\n<h2 id=\"versions\">Versions with data collection features<\/h2>\n<p>Data collection is turned on by default for the versions that support this feature. If you use the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> endpoint, you must also include the <a href=\"#checkout-attempt-identifier\">checkout attempt identifier<\/a> in your payment requests.<\/p>\n<p>The table below shows the supported types of data collection for each platform.<\/p>\n<table>\n<thead>\n<tr>\n<th>Platform<\/th>\n<th>Telemetry and checkout attempt identifier<\/th>\n<th>Drop-in\/Components analytics<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Web Drop-in\/Components<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;version%5B0%5D=5.16.0\">v5.16.0<\/a> or later <br>  Build type is only collected for <a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;version%5B0%5D=6.2.0\">v6.2.0<\/a> or later<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;version%5B0%5D=5.69.0\">v5.69.0<\/a> or later <br> <a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;version%5B0%5D=6.2.0\">v6.2.0<\/a> or later<\/td>\n<\/tr>\n<tr>\n<td>iOS Drop-in\/Component<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=iOS%20Components%2FDrop-in&amp;version%5B0%5D=5.0.0#releaseNote=2022-11-01-ios-componentsdrop-in-5.0.0\"> v5.0.0<\/a> or later<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=iOS%20Components%2FDrop-in&amp;version%5B0%5D=5.12.0\">v5.12.0<\/a> or later<\/td>\n<\/tr>\n<tr>\n<td>Android Drop-in\/Components<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Android%20Components%2FDrop-in&amp;version%5B0%5D=5.0.0\">v5.0.0<\/a> or later<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Android%20Components%2FDrop-in&amp;version%5B0%5D=5.7.0\">v5.7.0<\/a> or later<\/td>\n<\/tr>\n<tr>\n<td>React Native Drop-in\/Components<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?=1&amp;title%5B0%5D=React%20Native%20Components%2FDrop-in&amp;version%5B0%5D=1.1.0#releaseNote=2023-08-01-react-native-componentsdrop-in-1.1.0\">v1.0.0<\/a> or later<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Flutter Drop-in\/Components<\/td>\n<td><a href=\"\/pt\/online-payments\/release-notes\/?title%5B0%5D=Flutter%20Components%2FDrop-in&amp;version%5B0%5D=1.0.2\">v1.0.0<\/a> or later<\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"checkout-attempt-identifier\">Checkout attempt identifier<\/h3>\n<p>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 <a href=\"\/pt\/uplift#uplift-dashboards\">Checkout dashboard<\/a> that lets you analyze your checkout performance. For Web integrations, it also lets you use the <a href=\"\/pt\/uplift#uplift-personalize\">Adyen Uplift Personalize module<\/a>.<\/p>\n<p>If your integration uses the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/sessions<\/a> endpoint, the checkout attempt identifier is sent automatically with the payment request.<\/p>\n<p>If your integration uses the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> endpoint:<\/p>\n<ul>\n<li>Newer versions of Drop-in\/Components include the <code>sdkData<\/code> field that includes the <code>checkoutAttemptId<\/code>, and you no longer have to forward the identifier separately. You pass the <code>sdkData<\/code> when making a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request with your <a href=\"\/pt\/online-payments\/build-your-integration\/advanced-flow\">integration<\/a>. This is currently supported on:\n<ul>\n<li>Web <a href=\"\/pt\/release-notes?title%5B0%5D=Web%2BComponents%2FDrop-in&amp;version%5B0%5D=6.29.0\">v6.29.0<\/a><\/li>\n<li>iOS <a href=\"\/pt\/online-payments\/release-notes#releaseNote=2025-12-18-ios-componentsdrop-in-5.22.0\">v5.22.0<\/a> or later<\/li>\n<li>Android <a href=\"\/pt\/online-payments\/release-notes#releaseNote=2025-12-19-android-componentsdrop-in-5.16.0\">v5.16.0<\/a> or later<\/li>\n<li>React Native <a href=\"\/pt\/online-payments\/release-notes?title%5B0%5D=React%2BNative%2BComponents%2FDrop-in&amp;version%5B0%5D=2.9.0\">v2.9.0<\/a><\/li>\n<li>Flutter <a href=\"\/pt\/online-payments\/release-notes?title%5B0%5D=Flutter%2BComponents%2FDrop-in&amp;version%5B0%5D=1.8.0\">v1.8.0<\/a><\/li>\n<\/ul><\/li>\n<li>On earlier versions, you must get the <code>checkoutAttemptId<\/code> from your front end and include it in the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request you make from your server.<\/li>\n<\/ul>\n<h2 id=\"configure\">Configure data collection<\/h2>\n<p>Analytics data collection is enabled by default. You can <a href=\"#configure\">configure<\/a> what data we are allowed to collect for each of your integrations:<\/p>\n\n<div id=\"tabqK5Xo\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;Web&quot;,&quot;content&quot;:&quot;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th&gt;Parameter&lt;\\\/th&gt;\\n&lt;th&gt;Description&lt;\\\/th&gt;\\n&lt;th&gt;Default&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td&gt;&lt;code&gt;analytics.enabled&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Indicates if you are sending analytics data to Adyen. &lt;br&gt; From &lt;a href=\\&quot;\\\/pt\\\/online-payments\\\/release-notes\\\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;amp;version%5B0%5D=5.69.0\\&quot;&gt;v5.69.0&lt;\\\/a&gt; or &lt;a href=\\&quot;\\\/pt\\\/online-payments\\\/release-notes\\\/?title%5B0%5D=Web%20Components%2FDrop-in&amp;amp;version%5B0%5D=6.2.0\\&quot;&gt;v6.2.0&lt;\\\/a&gt; or later, telemetry and checkout attempt identifier are always sent to Adyen, this configuration only impacts the Drop-in\\\/Components analytics.&lt;\\\/td&gt;\\n&lt;td&gt;&lt;strong&gt;true&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n    &lt;code-sample :title=\\&quot;&#039;Configuration for analytics data collection on Web&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=\\&quot;[{&amp;quot;language&amp;quot;:&amp;quot;js&amp;quot;,&amp;quot;tabTitle&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;content&amp;quot;:&amp;quot;const configuration = {\\\\n   environment: &#039;test&#039;,\\\\n   clientKey: &#039;test_...&#039;,\\\\n   analytics: {\\\\n      enabled: true \\\\\\\/\\\\\\\/ Set to false to not send analytics data to Adyen.\\\\n   }\\\\n   \\\\\\\/\\\\\\\/ Other global configuration...\\\\n};&amp;quot;}]\\&quot; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;web_0_1&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;iOS&quot;,&quot;content&quot;:&quot;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th&gt;Parameter&lt;\\\/th&gt;\\n&lt;th&gt;Description&lt;\\\/th&gt;\\n&lt;th&gt;Default&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td&gt;&lt;code&gt;isEnabled&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Indicates if you send analytics data to Adyen. &lt;br&gt; From &lt;a href=\\&quot;\\\/pt\\\/online-payments\\\/release-notes\\\/?title%5B0%5D=iOS%20Components%2FDrop-in&amp;amp;version%5B0%5D=5.12.0\\&quot;&gt;v5.12.0&lt;\\\/a&gt; or later, telemetry and checkout attempt identifier are always sent to Adyen, this configuration only impacts the Drop-in\\\/Components analytics.&lt;\\\/td&gt;\\n&lt;td&gt;&lt;strong&gt;true&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n    &lt;code-sample :title=\\&quot;&#039;Configuration for analytics data collection on iOS&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;swift\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;\\\\\\\/\\\\\\\/ Create an analytics configuration object.\\\\nvar analyticsConfiguration = AnalyticsConfiguration()\\\\n\\\\\\\/\\\\\\\/ Add the isEnabled configuration parameter.\\\\nanalyticsConfiguration.isEnabled = true \\\\\\\/\\\\\\\/ Set to false to not send analytics data to Adyen.\\\\n\\\\n\\\\\\\/\\\\\\\/ Add the analyticsConfiguration when creating your context.\\\\nlet adyenContext = AdyenContext(apiContext: apiContext, analyticsConfiguration: analyticsConfiguration)\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;ios_1_2&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Android&quot;,&quot;content&quot;:&quot;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th&gt;Parameter&lt;\\\/th&gt;\\n&lt;th&gt;Description&lt;\\\/th&gt;\\n&lt;th&gt;Default&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td&gt;&lt;a href=\\&quot;https:\\\/\\\/adyen.github.io\\\/adyen-android\\\/components-core\\\/com.adyen.checkout.components.core.internal\\\/-configuration\\\/index.html#-1107459355\\\/Properties\\\/339477935\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot; class=\\&quot;external-link no-image\\&quot;&gt;\\n  &lt;code&gt;analyticsConfiguration&lt;\\\/code&gt;\\n&lt;\\\/a&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Indicates what analytics data you send to Adyen. &lt;br&gt; From &lt;a href=\\&quot;\\\/pt\\\/online-payments\\\/release-notes\\\/?title%5B0%5D=Android%20Components%2FDrop-in&amp;amp;version%5B0%5D=5.7.0\\&quot;&gt;v5.7.0&lt;\\\/a&gt; or later, telemetry and checkout attempt identifier are always sent to Adyen, and this configuration only impacts the Drop-in\\\/Components analytics.&lt;\\\/td&gt;\\n&lt;td&gt;&lt;strong&gt;AnalyticsConfiguration(AnalyticsLevel.ALL)&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n    &lt;code-sample :title=\\&quot;&#039;Configuration for analytics data collection on Android&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;java\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;CheckoutConfiguration(\\\\n   environment = environment,\\\\n   clientKey = clientKey,\\\\n   analyticsConfiguration = AnalyticsConfiguration(AnalyticsLevel.ALL), \\\\\\\/\\\\\\\/ Set to AnalyticsLevel.NONE to not send analytics data to Adyen.\\\\n   \\\\\\\/\\\\\\\/ Other configuration...\\\\n)\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;android_2_3&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;React Native&quot;,&quot;content&quot;:&quot;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th&gt;Parameter&lt;\\\/th&gt;\\n&lt;th&gt;Description&lt;\\\/th&gt;\\n&lt;th&gt;Default&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td&gt;&lt;code&gt;enabled&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Indicates if you send analytics data to Adyen.&lt;\\\/td&gt;\\n&lt;td&gt;&lt;strong&gt;true&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n    &lt;code-sample :title=\\&quot;&#039;Configuration for analytics data collection on React Native&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=\\&quot;[{&amp;quot;language&amp;quot;:&amp;quot;js&amp;quot;,&amp;quot;tabTitle&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;content&amp;quot;:&amp;quot;const analyticsOptions =  {\\\\n   enabled: true, \\\\\\\/\\\\\\\/ Set to false to not send analytics data to Adyen.\\\\n};\\\\n\\\\nconst configuration = {\\\\n   environment: &#039;test&#039;,\\\\n   clientKey: &#039;YOUR_CLIENT_KEY&#039;,\\\\n   analytics: analyticsOptions,\\\\n   \\\\\\\/\\\\\\\/ Other global configuration...\\\\n};&amp;quot;}]\\&quot; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;react_native_3_4&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Flutter&quot;,&quot;content&quot;:&quot;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th&gt;Parameter&lt;\\\/th&gt;\\n&lt;th&gt;Description&lt;\\\/th&gt;\\n&lt;th&gt;Default&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td&gt;&lt;code&gt;enabled&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Indicates if you send analytics data to Adyen.&lt;\\\/td&gt;\\n&lt;td&gt;&lt;strong&gt;true&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n    &lt;code-sample :title=\\&quot;&#039;Configuration for analytics data collection on Flutter&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=\\&quot;[{&amp;quot;language&amp;quot;:&amp;quot;js&amp;quot;,&amp;quot;tabTitle&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;content&amp;quot;:&amp;quot;final AnalyticsOptions analyticsOptions = AnalyticsOptions(\\\\n   enabled: true, \\\\\\\/\\\\\\\/ Set to false to not send analytics data to Adyen.\\\\n);\\\\n\\\\nfinal DropInConfiguration dropInConfiguration = DropInConfiguration(\\\\n    environment: &#039;test&#039;,\\\\n    clientKey: &#039;YOUR_CLIENT_KEY&#039;,\\\\n    countryCode: &#039;YOUR_COUNTRY_CODE&#039;,\\\\n    analyticsOptions: analyticsOptions\\\\n   \\\\\\\/\\\\\\\/ Other  configuration...\\\\n);&amp;quot;}]\\&quot; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;flutter_4_5&quot;,&quot;relation&quot;:&quot;&quot;}]\"\n            :should-update-when-url-changes='false'>\n        <\/tabs>\n    <\/div>\n<\/div>\n\n<h2>Collect additional data to detect fraud<\/h2>\n \n<p>For Web Drop-in\/Components integrations, you can optionally <a href=\"\/pt\/risk-management\/fraud-data-collection\">collect data to detect fraud<\/a> 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.<\/p>\n \n<p>To do this, add the following script to any of your web pages.<\/p>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Data collection script'\" :id=\"''\" :code-data='[{\"language\":\"javascript\",\"tabTitle\":\"\",\"content\":\"&lt;script src=\\\"https:\\\/\\\/checkoutshopper-live.adyen.com\\\/checkoutshopper\\\/assets\\\/js\\\/datacollection\\\/datacollection.js\\\"&gt;&lt;\\\/script&gt;\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p>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.<\/p>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/risk-management\/fraud-data-collection\/\"\n                        target=\"_self\"\n                        >\n                    Data collection to detect fraud\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/online-payments\/analytics-and-data-tracking","articleFields":{"description":"Find out what usage data Adyen collects for Drop-in and Components.","feedback_component":true,"filters_component":false,"decision_tree":"[]","page_id":"9ddb0b09-05e7-407d-a7bf-1dd77d83ee29","last_edit_on":"21-10-2024 10:19"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/analytics-and-data-tracking","title":"Analytics and data tracking","content":"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.\nBenefits of data collection\nThe data we collect will help us to:\n\nOptimize the checkout experience. For example, find out how different device types can affect checkout performance and make improvements where needed.\nSee region and industry specific performance. For example, identify integration issues with popular payment methods to improve performance and conversion.\nCompare different integration types you might have. For example, compare performance to continuously improve the product and the checkout experience for the shopper.\n\nData we are collecting\nWe collect different types of data:\n\nTelemetry\n\nType of integration you are using, that is Drop-in or Components.\nVersion of Drop-in or Components.\nPlatform, that is web, iOS, or Android.\nFor mobile integrations, system version of the shopper's device.\nLocale, which is the language the shopper sees in the UI, for example en-US.\nURL for the page where you mounted Drop-in or Components.\nPayment methods rendered on Drop-in.\nComponents you are using.\nUser agent.\nPayment amount and currency.\nWeb Drop-in\/Components build type, that is  Universal Module Definition (UMD), or compiled.\n\nCheckout attempt identifier\n\nUsing the checkout attempt identifier, we link the telemetry data to the payment data. We are not using cookies to collect analytics data.\n\nDrop-in\/Components analytics\n\nFront end errors, like payment form input errors.\nShopper events, like scanning a QR code for a payment, or authenticating with 3D Secure 2.\n\n\n\nCheck 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.\n\nVersions with data collection features\nData collection is turned on by default for the versions that support this feature. If you use the  \/payments endpoint, you must also include the checkout attempt identifier in your payment requests.\nThe table below shows the supported types of data collection for each platform.\n\n\n\nPlatform\nTelemetry and checkout attempt identifier\nDrop-in\/Components analytics\n\n\n\n\nWeb Drop-in\/Components\nv5.16.0 or later   Build type is only collected for v6.2.0 or later\nv5.69.0 or later  v6.2.0 or later\n\n\niOS Drop-in\/Component\n v5.0.0 or later\nv5.12.0 or later\n\n\nAndroid Drop-in\/Components\nv5.0.0 or later\nv5.7.0 or later\n\n\nReact Native Drop-in\/Components\nv1.0.0 or later\n\n\n\nFlutter Drop-in\/Components\nv1.0.0 or later\n\n\n\n\nCheckout attempt identifier\nThe 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 that lets you analyze your checkout performance. For Web integrations, it also lets you use the Adyen Uplift Personalize module.\nIf your integration uses the  \/sessions endpoint, the checkout attempt identifier is sent automatically with the payment request.\nIf your integration uses the  \/payments endpoint:\n\nNewer 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 request with your integration. This is currently supported on:\n\nWeb v6.29.0\niOS v5.22.0 or later\nAndroid v5.16.0 or later\nReact Native v2.9.0\nFlutter v1.8.0\n\nOn earlier versions, you must get the checkoutAttemptId from your front end and include it in the  \/payments request you make from your server.\n\nConfigure data collection\nAnalytics data collection is enabled by default. You can configure what data we are allowed to collect for each of your integrations:\n\n\n    \n        \n        \n    \n\n\nCollect additional data to detect fraud\n \nFor Web Drop-in\/Components integrations, you can optionally collect data to detect fraud 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.\n \nTo do this, add the following script to any of your web pages.\n\n    \n\nWhen 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.\nSee also\n\n\n                    Data collection to detect fraud\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Analytics and data tracking"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"\/pt\/online-payments\/analytics-and-data-tracking"},"levels":3,"category":"Online Payments","category_color":"green","tags":["Analytics","tracking"]}}