This also resolved an issue where random strings were being appended to the Source
We are tracking the utm_campaign parameter if it is available on the url. Unlike in GA, where we can track utm_campaign on the session level, we are only able to track this parameter on the first kinja url that a user loads.
Origin/Source tracks how a user discovers content on Kinja. Values can refer to social networks (twitter, facebook) or to widgets in kinja proper (inset, youmayalsolike, secondscroll)
Fixed an issue in our data pipeline that had caused Amazon Subtag metadata to not write to our warehouse since 5/23
After a test which showed an overall CTR improvement for Commerce, we turned on the winning feature switch