How to Create a Session ID for the Device Data Collector

The session identifier, or sessionId, is used to join the device data with the order data sent by the Risk Inquiry System (RIS) process. When the RIS process posts data to Kount, it must use the session identifier that was created when the customer initiated the data collector HTML.

The customer determines what the sessionId is, but you must follow the limitation guidelines. Many customers use a portion of the application session that is generated when the page is created as the session identifier.

Limitation guidelines state that it must be alpha-numeric value with a minimum of one character and a maximum of 32 characters.

The session identifier must be unique over a 30-day time period. If there are duplicate session IDs, data obtained via the Device Data Collector may be erroneously linked to RIS order data.

Implementation Details

Kount Generated (RECOMMENDED)

The value (UUIDv4 without the dashes) is created by Kount and returned when the Device Data Collection SDK is downloaded. This method guarantees the sessionId is unique and meets the requirements. To have Kount generate the sessionId, exclude the sessionId parameter in the call to download the Device Data Collection SDK, as shown in the following example (web implementation only):

<script type='text/javascript' 
src='https://DATA_COLLECTOR_URL/collect/sdk?m=123456'> 
</script>

Customer Generated

If you require control over the sessionId that is passed to Kount, you can generate your own. The sessionId must meet the requirements and be sent in the call to download the Device Data Collection SDK (web implementation only). The follow example assumes the sessionId is abcdefg12345abababab123456789012:

<script type='text/javascript' 
src='https://DATA_COLLECTOR_URL/collect/sdk?
m=123456&
s=abcdefg12345abababab123456789012'> 
</script>

Accessing the sessionId

Whether you let Kount generate your session ID, or you generate your own, it is made available to the script on the page via the ka.sessionId attribute that is included in the downloaded Device Data Collection SDK. This is discussed in greater detail on the Web Client and Browser Setup documentation page.

sessionId Requirements

• sessionId must be unique per request. They must be unique for a minimum of 30 days.
• sessionId must contain only alphanumeric characters (0-9, a-z or A-Z), dashes (-) or underscores (_).
• sessionId values should be 32 characters in length. sessionId values of less than 32 characters are accepted, but it is strongly recommended to use a 32 character value.