---
title: Device profiling method
description: To produce a risk assessment for a sign-on event, FraudForce requires information about the user's device. You can collect this information using the TruValidate IdP Adapter or by attaching the scripts to another adapter in your sign-on flow.
component: truvalidate
page_id: truvalidate::pf_truvalidate_ik_device_profiling_method
canonical_url: https://docs.pingidentity.com/integrations/truvalidate/pf_truvalidate_ik_device_profiling_method.html
llms_txt: https://docs.pingidentity.com/integrations/truvalidate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: May 22, 2025
section_ids:
  captured-by-the-truvalidate-idp-adapter: Captured by the TruValidate IdP Adapter
  captured-by-a-previous-adapter: Captured by a previous adapter
---

# Device profiling method

To produce a risk assessment for a sign-on event, FraudForce requires information about the user's device. You can collect this information using the TruValidate IdP Adapter or by attaching the scripts to another adapter in your sign-on flow.

## Captured by the TruValidate IdP Adapter

The TruValidate IdP Adapter inserts a page into the sign-on flow that shows a spinner animation while the device profiling process runs. The page typically appears after the first-factor authentication page, as determined by your authentication policy.

|   |                                                            |
| - | ---------------------------------------------------------- |
|   | This method adds a short wait time to the sign-on process. |

## Captured by a previous adapter

Scripts are added to a page presented by another adapter in your authentication policy. This page must appear earlier in the sign-on flow than the TruValidate IdP Adapter, such as the first-factor authentication page.

This method reduces wait times by allowing the TruValidate JavaScript to prepare the device profile blackbox while the user types in their credentials.

The TruValidate IdP Adapter is still responsible for sending data back to the TruValidate API, so the script uses HTTP cookies to pass the device profile blackbox from the first-factor authentication page to the TruValidate IdP Adapter.

You can integrate the TruValidate script into any page that meets the following criteria:

* The page appears before the TruValidate IdP Adapter in the sign-on flow.

* The page is hosted in the same domain as your PingFederate server. This allows you to use HTTP cookies to pass the blackbox to the TruValidate IdP Adapter.

  |   |                                                                                                              |
  | - | ------------------------------------------------------------------------------------------------------------ |
  |   | You might be able to work around this requirement by consolidating your domains with a reverse proxy server. |

* You have access to add JavaScript to the page's HTML code.

You can find instructions in [Adding device profiling to an authentication page](setup/pf_truvalidate_ik_adding_device_profiling_authentication_page.html) after you finish [Deploying the integration files](setup/pf_truvalidate_ik_deploying_integration_files.html).