Post by account_disabled on Feb 22, 2024 4:14:37 GMT
The into it now. Suffice to say its a way of telling browsers to pass some referrer data to nonsecure sites and can be implemented as a meta element or HTTP header. . Missing or broken tracking code Lets say youve launched a new landing page template and forgotten to include the GA tracking code. Or to use a scenario Im encountering more and more frequently imagine your GTM container is a horrible mess of poorly configured triggers and your tracking code is simply failing to fire. Users land on this page without tracking code. They click on a link to a deeper page which does have tracking code.
From GAs perspective the first hit of the session is the America Mobile Number List second page visited meaning that the referrer appears as your own website i.e. a selfreferral. If your domain is on the referral exclusion list as per default configuration the session is bucketed as direct. This will happen even if the first URL is tagged with UTM campaign parameters. As a shortterm fix you can try to repair the damage by simply adding the missing tracking code. To prevent it happening again carry out a thorough Analytics audit move to a GTMbased tracking implementation and promote a culture of datadriven marketing. . Improper redirection This is an easy one. Dont use meta refreshes or JavaScriptbased redirects these can wipe or replace referrer data leading to direct traffic in Analytics.
You should also be meticulous with your serverside redirects and as is often recommended by SEOs audit your redirect file frequently. Complex chains are more likely to result in a loss of referrer data and you run the risk of UTM parameters getting stripped out. Once again control what you can use carefully mapped i.e. nonchained code serverside redirects to preserve referrer data wherever possible. . Nonweb documents Links in Microsoft Word documents slide decks or PDFs do not pass referrer information. By default users who click these.
From GAs perspective the first hit of the session is the America Mobile Number List second page visited meaning that the referrer appears as your own website i.e. a selfreferral. If your domain is on the referral exclusion list as per default configuration the session is bucketed as direct. This will happen even if the first URL is tagged with UTM campaign parameters. As a shortterm fix you can try to repair the damage by simply adding the missing tracking code. To prevent it happening again carry out a thorough Analytics audit move to a GTMbased tracking implementation and promote a culture of datadriven marketing. . Improper redirection This is an easy one. Dont use meta refreshes or JavaScriptbased redirects these can wipe or replace referrer data leading to direct traffic in Analytics.
You should also be meticulous with your serverside redirects and as is often recommended by SEOs audit your redirect file frequently. Complex chains are more likely to result in a loss of referrer data and you run the risk of UTM parameters getting stripped out. Once again control what you can use carefully mapped i.e. nonchained code serverside redirects to preserve referrer data wherever possible. . Nonweb documents Links in Microsoft Word documents slide decks or PDFs do not pass referrer information. By default users who click these.