---
schema_version: "1"
id: 2eeefc8bfbab8e4c83481d8ea19540bf7e7d5255e5d8fbbfa15a0b9ee34a2b8c
title: ClientBrowser
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_clientbrowser.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_clientbrowser.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: abfc9535a523f64448233e2899b5ae4035dbdaa4005fa6e470b339647a68a1b3
description: Represents a cookie added to the browser upon login, and also includes information about the browser application where the cookie was inserted. This object is available in version 28.0 and later.
---
# ClientBrowser

Represents a cookie added to the browser upon login, and also includes information about the browser application where the cookie was inserted. This object is available in version 28.0 and later.

## Supported Calls

describeSObjects(), delete(), query(), retrieve()

## Fields

| Field | Details |
| --- | --- |
| FullUserAgent | 
Type

string

Properties

Filter, Nillable, Sort

Description

Detailed information about the client (browser). For example, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1



 |
| LastUpdate | 

Type

dateTime

Properties

Filter, Nillable, Sort

Description

Represents the last time the cookie was changed.



 |
| ProxyInfo | 

Type

string

Properties

Filter, Nillable, Sort

Description

The browser’s current proxy information.



 |
| UsersId | 

Type

reference

Properties

Filter, Group, Sort

Description

The ID of the user associated with this item.

This is a relationship field.

Relationship Name

Users

Relationship Type

Lookup

Refers To

User



 |

## Usage

At every login, the device the login request is from is checked against the known devices using ClientBrowser. A match means a cookie was found on the browser that matches an entry in the ClientBrowser table, so the device is known. No match means that no matching cookie was found, so the device is unknown, and the user is asked to confirm their identity.