Many sites use different url formats. You can use URL Normalization to reduce the logging of different urls that might be equivalent or redundant. A custom function with no implementation is added as a placeholder in the configuration that eventually defines how a url is normalized.
Some normalization techniques include:
- removing parameters
- masking parameter values
- replacing targeted text
The same normalization function is used to normalize urls in the Overstat, Replay, and Ajax Listener Acoustic Experience Analytics (Tealeaf) modules. Both the normalized and original urls are recorded in these modules. Acoustic Experience Analytics (Tealeaf) records the urls in type 2 messages (load/unload) for Overstat and Replay, and in type 5 message for Ajax Listener.
After you provide the implementation, ensure that adequate testing is performed. Testing ensures that the resulting url is normalized in the desired format.
The input normalization configuration is specified in the core object of the JSON configuration.
urlFunction properties are mandatory and must be declared as below.
Replace parameter value
Note: Overstat and Replay tend to strip out the querystring from url. Use slash, underscore, or other delimiters.