When you go to http://www.standaard.be/plus/avond, and youâ re not logged in, you will be directed to http://www.standaard.be/plus/login-avond?goto=http%3A%2F%2Fwww.standaard.be%3A80%2Fplus%2Favond
This is not an issue as such but it become an issue when related to campaign tracking.
So if we take the same URL but which includes GA campaign parameters, the same redirect happens, but the campaign info is not being send to the GA campaign cookie (_utmz), because of this redirect.
http://www.standaard.be/plus/avond?utm_source=standaard&utm_medium=bannerfoot&utm_campaign=behavioraldsavondpromo
becomes
http://www.standaard.be/plus/login-avond?goto=http%3A%2F%2Fwww.standaard.be%3A80%2Fplus%2Favond%3Futm_source%3Dstandaard%26utm_medium%3Dbannerfoot%26utm_campaign%3Dbehavioraldsavondpromo
So what we would like to solve via Tealium, and send the campaign info, one way or another, to the cookie.
As you see from teh example above, the campaign parameters and values are still included in the URL. So my idea was to get the GA campaign parameters based on the info from the URL (utm_source=standaard&utm_medium=bannerfoot&utm_campaign=behavioraldsavondpromo) attached to the redirected URL (applying a load rule in order to define when this should happen) , so this will become
http://www.standaard.be/plus/login-avond?goto=http%3A%2F%2Fwww.standaard.be%3A80%2Fplus%2Favond%3Futm_source%3Dstandaard%26utm_medium%3Dbannerfoot%26utm_campaign%3Dbehavioraldsavondpromo&utm_source=standaard&utm_medium=bannerfoot&utm_campaign=behavioraldsavondpromo
But there might be another more simple solution?
... View more