Hit attributes are based on pattern matches. The same pattern may appear in different sections of the request, ex. [env], [urlfield], and [referrer]. This can cause the hit attribute to grab the wrong value, causing events to fire incorrectly.
How will this idea be used?
This is really for any event, to safeguard the data quality and reliability of our events and reporting. We have already had issues with urlfield checks, due to the same value showing up in [urlfield] on hit 1, as well as [Referrer] on hit 2, and the event should only fire on 1 of the 2 hits. |
|
What is your industry? | Banking |
What is the idea priority? | Medium |