![]() ![]() WHEN Previous Page Path = "(entrance)" AND Source = "(direct)" THEN "Direct" “PNF – Trigger” field for the donut chart to create 3 groups of errors (PNF prefix for “page not found”). ![]() You can also adapt each formula following which data you consider important to help to solve each kind of reason provoking the “page not found” error. So, let’s create these calculated fields, respecting the formulas and names below. Here, it is a little more complicated because we use intermediary dimensions aggregating several data. I used this principle of “responsive” dimension in the past for simple dimensions switch following the selection of another dimension (An example through this Twitter thread). Let’s configure calculated fields: We will combine the Previous Page Path and acquisition dimensions to identify in which case the error had occurred, and so, to provide the related better information. 7 calculated fields to manage page not found details.A report filter to isolate only page views corresponding to “page not found” loads.Table chart with requested URL, drilled down by error details, with the number of related errors.Donut chart with triggers group of error loads.Now, let’s create our report composed with: If your application doesn’t respect the points above, you can adapt the measurement plan (tracking) to inject the required data with the page view tag. A dedicated page title is used for “page not found” errors (“Page not found”, “404 Page error”, “Page unavailable”…), so stored as GA Page title dimension.The requested URL is kept without redirection, so stored as GA Page dimension.GA page view tag is triggered when a “page not found” error occurs.We just need a tag of page view and also confirm that our web application behaves as following, and so the related data are collected by Google Analytics: We will use a basic Google Analytics (GA) measurement plan, providing the required data. Get a first level of information to launch corrective actions with the right people (writers, SEO agency, traffic manager…).Identify the requested URLs not corresponding to an available page.Direct (marginal, taping problem or big technical problem).Internal links (content contribution & on site problem).External links (acquisition traffic & off site problem).Filter by reason groups explaining pages not found:.Focus on the pick of errors in daily or hourly basis regarding the usual & so acceptable number of errors.We just need a report addressing the following steps of reading process: With Google Analytics, in most of cases, it is easy to identify it. Not updated XML products feed for partners usages.Bad redirection plan of URL for SEO purposes.Launching of traffic acquisition campaign with some corrupted landing URLs.Unpublishing contents without taking care of side effects regarding digital ecosystem using it.To be efficient operationally speaking, we will not be satisfied by a simple flat list of 404 URLs…definitely not…Īs usual, the good combination of Data Studio features will help us to create an interactive and responsive dashboard helping us to jump inside available and, above all, prepared data to provide very quickly first information to solve our technical problem.Ī lot of reasons can provoke “page not found” errors: In this article, we will create a simple Google Data Studio report based on Google Analytics data to monitor and solve loads of pages not found by the web application. ![]() You can also use it for technical monitoring. Google Data Studio can help you to address a lot of challenges of dashboarding, reporting or data story telling. ![]()
0 Comments
Leave a Reply. |