[iamie] section

This chart provides details about the hit and the method that cxImpact used to capture the hit.

Key fields include:

Table 1. [iamie] section
REQTEXT
Field Name	Use	Source
`TLTSID`	The final `TLTSID` value that provides the unique key value that is used to identify all hits within a visitor session.	Cookie Injector. Computed by cxImpact.
`TLTHID`	A unique value that differentiates this hit from all other hits that are captured by cxImpact.	Cookie Injector. Computed by cxImpact.
`TLTUID`	A unique value that differentiates this user from all other users that are captured by cxImpact.	Cookie Injector. Computed by cxImpact.
`CaptureSource`	Identifies how this hit was captured. Common Values are for Client-Side Capture, Passive Capture, or the IIS Filter Capture.	Inserted by cxImpact.
`CaptureType`	The capture type defines the type of content that is captured by the PCA. The following possible values are inserted by the PCA: `1` - Request and response were captured. `3` - Content is captured per specification in a Capture Type list in the PCA.	PCA
`CaptureVersion`	The version of the Capture Source that captured this hit.	PCA
`CaptureInst`	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
`CapturePipelineInst`	The PCA pipeline instance that processed this hit. This value is useful for determining the load distribution among multiple pipeline instances.	PCA

The 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 TLTSID from a configurable value. Typically, either the ASPSESSIONID cookie or the JSESSIONID cookie is used to derive the TLTSID.

Request view