In order for us to have taggers that tag web requests based on the referer, that field needs to be added to WebrequestData and accounted for by the UDFs & the tagging system.
The use case is a secondary tag for internally-referred pageviews that came from someone clicking on a result on a search results page.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T171985 SERP tagging | |||
| Declined | • Nuria | T172009 Add referer to WebrequestData |
This is waiting on work from Analytics to do the UDF update, we're not sure of the timeframe.
To clarify, I assume that this is separate from the general HTTP referrer header that is already recorded in the referer field in the webrequest data.
Correct, this is to add that to the webrequest class in refinery core that tagging relies on.