The DOM Capture Virtual Hit Session Agent moves the captured DOM data or DOM Diff data from the UI hit into a newly created virtual hit, with the captured DOM or DOM Diff as its response.
After the virtual hit is created, the original DOM capture data or DOM Diff data is removed from the JSON and replaced with an empty string.
Restrictions for adding the Session Agent
If you are planning to use DOM capture or DOM Diff capture, it must be configured after the
Inflate session agent and before the Privacy session agent in
TealeafCaptureSocket.cfg. For example:
[Inflate] TypeName=Inflate DLL=SessionAgentInflate.dll UnReqCancelled=True MaxInflateSize=1536KB DownStreamConfigSection=DomCaptureVHit [DomCaptureVHit] TypeName=DomCaptureVHit DLL=SessionAgentDomCaptureVHit.dll DownStreamConfigSection=PrivacyEx
DOM Capture Virtual Hit Session Agent configuration options
These arguments allow filtering by minimum type 12 message payload size, URL Black list / White list, add an option to retain the type 12 data.
The following is a sample config snippet:
# Do not create the VHit, and discard it's type-12 JSON payload, if data (JSON) length # is below the threshold (bytes). # Default=0, meaning type 12 messages of any size are processed as usual (produce VHits # and remove). #MinSize=200 # Parametrize URL. This allows to specify another field to filter on, e.g. TLT_CUI_ORIG_URL # instead of the default TLT_CUI_URL. #UrlField=TLT_CUI_URL # For black listed pages, do not generate VHits, and type 12 data remains. #UrlBlackList=\/en-us\/shop\/category\/laptops;^\/$ # If white list is empty, type 12 messages are processed as usual (produce VHits and remove). # URL is white listed - process as usual. # URL is not white listed - do not generate VHits, and strip the type 12 data. #UrlWhiteList=\/en-us\/shop\/productdetails # If enabled, keep all type 12 JSON messages for the hits that were caught by UrlWhiteList / # MinSize. # Default=False #RetainSkippedData=True[Inflate]