All Google Analytics traffic marked as ‘Direct’

@agf2 Still using LS Cache. It’s still great I think, but would of course be better if GA tracked worked as intended.
If your site is still slow even with LS cache its probably because your site is bloated with unnecessary .js or that you didn’t setup the plugin the right way I suppose.

Hey, also experiencing the traffic issue, everything has passed to direct sice we activated the caching

Hi, I’m having the same issue using GTM connected to 2 properties, one for standard UA and the other for the new GA4, both having issue assigning traffic source.
I also tried the solution proposed in their guide but nothing changed.

Hi @qtwrk,

Any updates on this issue? The guest mode is fantastic, but the only thing is the organic and direct traffic disorientation issue caused by this makes it not usable.

Any ETA on when the dev team would fix it?

Thanks.

• This reply was modified 3 years, 3 months ago by jeff0504.

Hi, after some testing I found out that the $_SERVER[‘HTTP_REFERER’] is initially correct (www.google.com) but as soon as the page loads it is reloaded with the HTTP_REFERER setted as the current page URL.
This seems to happening only after a full cache purge, on the first user visit; if he comes back from Organic Search the HTTP_REFERER is correct and no reload happens.

Hope this is helpful for someone!

Hi @hailite – been a white since we last spoke, but have to chime in as this is a very troubling issue without an update for over 3-4 months. We can share our experience running this across many sites and they all have GA issues. As a result, we rolled back to 4.1. Other work arounds do not work like turning off guest mode too @qtwrk.

FYI – We have reports showing organic drops up to 50% on each site we’ve added it over the past 2-3 months. Our GA Reports are a MESS. Can’t tell a proper story with bad data. Everyone of our clients ask “can we change it back” (like the same day, like now – while we’re on a call with them) because it’s so important for them to see consistency in their reporting.

PLEASE, we beg as a team of SEO’s, that you resolve this issue.

Please update us asap. Even if your response is that you’re not addressing it, we need to know so we can explore other options. Many thanks!

Apologize for late response. @hmsre If you exclude GA code from GM JS, when you view source code of 1st visit (which means this visit is under GM), make sure GA JS is indeed excluded from GM optm. After this, is the organic traffic still wrong ?

Hi everyone, in the last week we are testing a possible workaround that seems solve the problem.
We have inserted a little script in the very top of the head section that checks if the document.referrer contains the website domain or not (in case of organic traffic it is google.com) and save it in localSession.
On the Guest Mode page refresh we check again the document.referrer that now is equal to the website domain, so we now check if exists the old referral in localSession e replace the current referrer with the old, before any Google Analytics code is executed.

So, when it executes it sees that the document.referrer is google.com and assign that user to the organic traffic segment.

Hope this is usefull!

@michelefns This is a good idea. Thanks for the direction. Will give it a try.

Hi @michelefns ,

I just gave a commit https://github.com/litespeedtech/lscache_wp/commit/758788f88a5f50b7fb1efcc61c1caa6188115d7d as v4.4.6-a4. I didn’t confirm if it works or not yet. Did you mean something like the above code I made? Any feedback is welcomed.

Hi @hailite, this is exactly the code we wrote.

Amazing for same code! ??

Will be in next release this 27th.

@hailite I want to add along with GA, is it possible to add traffic from Instagram and Facebook?

I’m using GTM for FB pixel, and all of these are marked as DIRECT.

try v4.4.6

Hi,

Is this 100% fixed on 4.4.6?