Hi all,
Solved! Go to Solution.
The critical thing about distinguishing an Organic vs. Direct pageview of the exact same, untagged URL: you have only the Referrer header to draw on.
And the previous page — if there is one — is under no obligation to send that header. When there's no apparent Referrer, the pageview will look exactly like a direct pageview, regardless of whether a link was followed to get there. More details here: Here’s why your “Autofill from Referrer Parameter” setup stopped working.
Most sites do still send the Referrer, but they send the simple URL origin (https://www.example.com) only, not the full URL of the source page (https://www.example.com/this/is/stuff?you=wish&were=visible&in=Marketo) for security & privacy.
All analytics libraries have access to the same stuff in the browser for on the destination page; GA doesn't have special access to anything. Now, in the Google Console you can see which of your links were clicked in search results, for example — but that's b/c Google is the source site in this case, not the destination.
The critical thing about distinguishing an Organic vs. Direct pageview of the exact same, untagged URL: you have only the Referrer header to draw on.
And the previous page — if there is one — is under no obligation to send that header. When there's no apparent Referrer, the pageview will look exactly like a direct pageview, regardless of whether a link was followed to get there. More details here: Here’s why your “Autofill from Referrer Parameter” setup stopped working.
Most sites do still send the Referrer, but they send the simple URL origin (https://www.example.com) only, not the full URL of the source page (https://www.example.com/this/is/stuff?you=wish&were=visible&in=Marketo) for security & privacy.
All analytics libraries have access to the same stuff in the browser for on the destination page; GA doesn't have special access to anything. Now, in the Google Console you can see which of your links were clicked in search results, for example — but that's b/c Google is the source site in this case, not the destination.
Thank you, SanfordWhiteman.
So my only option to distinguish between organic and direct traffic would be to check if there is a referrer or not? If there is no referrer, then it would be considered direct traffic and if there is a referrer (but not utm tags), then it would be considered organic?
I read the post you linked to and understand that the above would not be 100% accurate, but it sounds like it's the closest I can get to a solution (as long as I use utm tags for everything else, such as social, paid search, referral, etc).
That being said, I would rather want to know the 'last referrer' (which is not a default field in Marketo) as opposed to 'original referrer'. I have not been able to find out a way to capture the last referrer data either though.
As I mentioned, Pardot automatically categorizes traffic as organic or direct. I wonder how they make that determination.
That being said, I would rather want to know the 'last referrer' (which is not a default field in Marketo) as opposed to 'original referrer'. I have not been able to find out a way to capture the last referrer data either though.
You can store the {{trigger.referrer}} of a Visit Web Page in a field. However, it can be hard on a busy instance to do this for every pageview. Better to use logic on the client (browser) side to determine interesting new referrers and then send a special Munchkin hit in only those cases.
As I mentioned, Pardot automatically categorizes traffic as organic or direct. I wonder how they make that determination.
They guess. 🙂 For a single pageview, no platform has any more access than another. If the referrer isn't present, you can guess that it's direct — but it could just as easily be a referral from an unknown site that suppresses the referrer.