Jun 24, 2021 10:24 AM
Could we find a way to resolve this? It would be wonderful if AMP traffic was actually categorized as organic search traffic instead of referral traffic.
As an agency, we work hard to generate organic traffic for our clients, but reporting in HubSpot isn't giving us that credit.
Here's an example from one of our accounts. Our top performing channels (from a conversion perspective) are Referrals and Organic Search. However, upon a closer look, we see that "referrals" aren't really referral traffic at all.
We love that HubSpot immediately takes care of AMP for us, however any sessions and contacts are being attributed under "Referral" traffic instead of organic search.
Here's what we see in HubSpot.
Additionally, there are other variations listed including "ampproject.org" and "amphubspot.net"
I know in theory, I can rebuild a custom field and some workflows that can "rebuild" the attribution, but it would be nice to use everything out of the box with proper attribution.
Jun 30, 2021 12:05 PM
I understand, technically speaking, what's happening. Still, it makes it more difficult to actually report back to our clients on what is happening. In an ideal world I'd love to be able to select how certain domains within Referral Traffic are categorized. It would be wonderful to have the ability to split Referral Traffic into sub-categories for directories, review sites, etc.
Jun 30, 2021 5:22 PM
I would highly recommend you to please post this idea at our ideas forum (here).
Our product team, who monitors the forum regularly, can read your specific use case and understand why this would be a useful functionality or change. It also helps other customers facing the same issue to advocate for its implementation on your behalf by upvoting on the thread as well.
Jun 25, 2021 11:59 AM
Hello @_ashleyquintana, Happy Friday!
Thank you for the information provided about the source of referrals in your traffic analytics reports.
To give some context regarding this,
From checking a similar case, our product team mentioned that the reason these URLs will not working when you try to go to them directly through traffic analytics has to do with the way that they get cached at Google's server level.
There's an authentication process with cached AMP content being returned which hinges upon accessing the cached data through the search engine; since we're not returning content through Google's search engine in-app, that authentication component does not work and Google's CDN returns an error.
At the moment we will not be able to trace back the exact referring site that your visitors landing on, as the user is viewing Google's cached version of the AMP content.
I hope this information helps.