---
title: Adding device profiling to an authentication page
description: Instead of using the ID DataWeb IdP Adapter to collect the device profile, you can capture the device profile using an existing sign-on page. This can reduce perceived wait times for the user.
component: iddataweb
page_id: iddataweb:setup:pf_iddataweb_ik_adding_device_profiling_to_an_authentication_page
canonical_url: https://docs.pingidentity.com/integrations/iddataweb/setup/pf_iddataweb_ik_adding_device_profiling_to_an_authentication_page.html
revdate: July 8, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Adding device profiling to an authentication page

Instead of using the ID DataWeb IdP Adapter to collect the device profile, you can capture the device profile using an existing sign-on page. This can reduce perceived wait times for the user.

## About this task

You can adapt these instructions to add device profiling to any page, such as the HTML Form Adapter or your web application. The page must meet the criteria listed in [Device profiling methods](../pf_iddataweb_ik_device_profiling_methods.html).

## Steps

1. Embed the JavaScript files in the page.

   1. If you're modifying an external web application, copy the `id_dataweb_device_profiling.js` file from the integration `.zip` archive to a location that your page can access.

   2. Add the following to the sign-on page and adjust the path to the script file:

      ```
      <script type="text/javascript" src="id_dataweb_device_profiling.js"></script>
      ```

      |   |                                                                                                                  |
      | - | ---------------------------------------------------------------------------------------------------------------- |
      |   | If you're modifying a PingFederate template, the script path is `assets/scripts/id_dataweb_device_profiling.js`. |

   3. Save the file.

2. (Optional) In the script file, customize the name prefix for the device profile cookie to suit your environment.

   ```
   var cookieName = "idwUUID";
   ```

3. When you complete the steps in [Configuring an adapter instance](pf_iddataweb_ik_configuring_an_adapter_instance.html):

   1. Set the **Device profiling method** to **Captured by a previous adapter**.

   2. Update the **Cookie name** field if you customized it in step 2.