Hi Nicolas,
Thanks for your response.
We tried the new version and it now logs the transactions as (Other) in Google Analytics. This is still incorrect. It needs to log whichever channel the user arrived by i.e Paid Social, Paid Search, Organic etc.
We need a work around for the redirect, it is not normal to have 2 redirects before the confirmation page. If it cannot be removed then is there an alternative? This issue is causing us to capture incorrect data in Google Analytics.
To answer your question, what is the link between redirects and direct transactions? Redirects can often keep GTM code from launching and properly identifying the traffic as having come from a paid search campaign. For example, if your ad leads to
www.mydomain.com/index.html
, but you've created a 301, 302, or JavaScript redirect from that URL to
www.mydomain.com/page2.html
, the campaign information that was originally appended to the landing page is lost upon redirection.
The browser is redirecting before the java script call from the code can be made.
For more information please refer to the following:
support.google.com/analytics/answer/1034383?hl=en
support.google.com/analytics/answer/1009614