Page Specific Analytics
Hello,
I'm looking into our page specific analytics and it shows a surprising number of pageviews to “/” which I assume is our home page. However looking through GA4 and Microsoft Clarity they show much lower views and visits to our homepage. As our homepage has a far lower impressions per view than our other pages which are more suited for ads, I want to understand further how this could be affecting revenue.
Is there any way to dig into page specific data on Journey? It would be great to understand a little more about how people are getting here, or the number of sessions/users a page sees as opposed to just page views.
In addition, if this by chance is just a reporting error, does it affect revenue? Or are metrics such as pageviews, impressions per pageview, etc, tracked and calculated independent of revenue?
Having issues with reporting isn't ideal as we want to be able to use Journey's metrics to help improve our site and ad performance, but I would rather just a reporting issue rather than revenue taking a hit in some scenario where pages are being tracked/recognized incorrectly.
-
Hey Nicole,
These are fantastic questions so I wanted to jump in here. When you see / as a page in your Top Page report it is referring to your homepage. If you're looking to understand how to best utilize the Top Page report, I'd recommend checking out our help article here.
At this time, there isn't a way to specifically dig into where these views are coming from within your Grow Analytics. You mentioned you have GA4 so you can dig into Google Analytics a bit more to see where that traffic is coming from. One common place is social media profiles where it's linked in the description.
There will always be a bit of difference when you're looking at traffic between your Grow Publisher Portal and Google Analytics. This help article discusses that more in detail. I do want to reassure you that impressions and revenue are tracked separately by the ad server so all of that is independent of any analytics.
Having direct traffic to your homepage isn't necessarily a bad thing, since readers are using this page as a jumping point to get to your content. I always recommend making sure that, when it comes to your homepage, any content you want your readers to go to is placed closer to the top to drive users toward that post….and then of course make sure your posts are as optimized as possible!
0 -
Hello,
I am facing 2 problems.
1. On my dashboard → Analytics: The pageviews are showing 0 since I have applied ads again.
2. The RPM - The rpm is way way too low than what I had earlier few months back. Can't believe such low RPM.
There is surely some issue causing above 2 things.
Quickly fix this and let me know the issue.
0 -
Hi Akshay Thapliyal ! RPM drops in January are normal across the industry, and you can read more about that in our official post here.
As for your analytics, if you're not seeing sessions data in your dashboard, that would likely indicate the Grow script isn't successfully connected to the site anymore, is being optimized, or is being blocked by some sort of crawler firewall or security setting since this is the script that tracks all of your data.
The Grow script is separate from the Journey script – you can add the Grow script following these instructions, and then the reporting numbers should hopefully return to normal. If not, you'll want to ask your host if there are any firewalls or security settings that could prevent crawlers from crawling the site, and also make sure the script isn't being optimized by following the instructions in this help article. You can also refer to this open thread on the same topic for additional information and troubleshooting advice.
Thank you!
0 -
Ahh Okay. Thanks Rachel. Just one doubt, Do I have to keep this Grow script on all pages or on only 1 single page?
0 -
Akshay Thapliyal It needs to be applied to all pages, so we recommend installing the script in the <head> section of the site to ensure it's installed globally.
0
Journey is Self Supported
Please sign in to leave a comment.
Comments
5 comments