This chart provides details about the hit and the method that cxImpact used to capture the hit.
Key fields include:
||Cookie Injector. Computed by cxImpact.|
||A unique value that differentiates this hit from all other hits that are captured by cxImpact.||Cookie Injector. Computed by cxImpact.|
||A unique value that differentiates this user from all other users that are captured by cxImpact.||Cookie Injector. Computed by cxImpact.|
||Identifies how this hit was captured. Common Values are for Client-Side Capture, Passive Capture, or the IIS Filter Capture.||Inserted by cxImpact.|
||The capture type defines the type of content that is captured by the PCA. The
following possible values are inserted by the PCA:
||The version of the Capture Source that captured this hit.||PCA|
||The PCA instance from which this hit was captured and reassembled. This value is useful for determining the origin of duplicated hits and in load testing.||PCA|
||The PCA pipeline instance that processed this hit. This value is useful for determining the load distribution among multiple pipeline instances.||PCA|
TLTSID is used to stitch together the hits that compose a visitor session.
The cxImpact system has a number of ways to generate this value:
- Cookie Injectors: The best way to identify a session is to use the Cookie Injectors that are installed on the web servers.
- Session Agent: The default method that is used by Experience Analytics creates a Session
Agent in the pipeline to create a
TLTSIDfrom a configurable value. Typically, either the
ASPSESSIONIDcookie or the
JSESSIONIDcookie is used to derive the