Client ID Management
The CX Tag provides an easy way to implement your Client ID persistence strategy. You can use this capability to reuse user identifiers from your internal systems to be passed as Client IDs to the tag and append them to the behavior events captured from user interactions with your web applications. The Client ID can be persisted in the cookies for the time allowed by the browsers. This way, you can easily track returning behavior of visitor(s) to your web apps and analyze their behavior.
The Client ID persistence capability can be leveraged by any of the modules in the CX Tag and can be used in analyzing the cross-product user journey for a user.
Important: To request access to this feature, please contact My Oracle Support.
In this topic:
How it works?
A visitor interacts with web page(s), through multiple devices and often through multiple browsers on the same device. Each browser on the device is called a client. The CX Tag can be used to assign each client on a device a unique Client ID. This Client ID that is mapped to wt.co_f parameter and available for the reports.
The capabilities available with the CX tag are:
Managing the Client ID
The Client ID can be managed in 2 ways:
Customer managed Client ID
The Oracle customer can leverage the CX Tag methods to pass their internal system ID of the visitor as the Client ID for the visitor's session. The customer can use the same method to modify a Client ID that has already been set.
When the website implementation engineer opts for leveraging the Customer managed Client ID capability, the CX Tag waits for the response of the methods that set the Client ID. Until the Client ID is set successfully, the events are collected and queued. Only after the Client ID is set successfully, the collected events be enriched with the Client ID and then transmitted to the servers.
CX tag managed Client ID
An Oracle customer can leverage the out-of-the-box (OOB) Client ID capabilities of the CX Tag to automatically assign the Client ID for a visitor's session.
By leveraging this option, the CX Tag calls the method that retrieves an existing Client ID available in the cookies/local storage of the browser. In case the Client ID is not available in the cookies/local storage a new client ID is set by the CX Tag and the same is appended to all events that are collected and sent to the server.
Accessing the Client ID
An Oracle customer can retrieve the Client ID that is already available in a session.
Clearing the Client ID
A Client ID that is already set can be cleared. In this case, the wt.co_f value will not be sent. However, a CX tag generated Client ID will be available as a page variable for reference.
Modifying the Client ID
The Client ID can be modified in 2 ways:
Customer managed Client ID
In this case, the website implementation must call the method used to set the Client ID with a new value. This method overwrites the existing value for the Client ID.
CX tag managed Client ID
In this case, the website implementation engineer can modify the Client ID by using the setClientID again with the new Client ID. This overwrites the existing Client ID with the new Client ID.
Technical Reference
Learn how to implement and manage Client IDs by referring to the Oracle Infinity Developer Help Center - Client ID Management.
Oracle Infinity Developer Help Center - Client ID Management - Learn how to implement and manage Client IDs on your website.
Oracle Infinity Developer Help Center - Oracle CX Tag - Learn about to enable various CX products on your websites using the Oracle CX Tag.