Google Analytics Error On Page
Contents |
Google Analytics Trainings Google AdWords Trainings Google Tag Manager Workshop Reviews From Attendees Convince Your Boss Meet Our Trainers Training FAQs Training Email Reminders About About About Us Clients Case Studies Careers LunaLabs Testimonials Contact Blog GTM Book 1.877.220.LUNA Access google analytics 404 report 404 Error Metrics Using Google Tag Manager By Samantha Barnes / August 19, 2014
How To Find Broken Links With Google Analytics
Analytics Google Analytics Google Tag Manager Share on Facebook Share 54 Share on TwitterTweet 158 Share on Google Plus Share 21 Share
How To Find 404 Errors
on LinkedIn Share 53 As analysts and marketers, we always want to track positive performance metrics and conversions in Google Analytics. However, tracking errors is also important to monitor the health of your site and
Google Analytics View Exceptions
keep track of signals indicating a negative user experience. Accessing this data gives us a better idea of what's causing users to get lost and wander into the dark, unattached voids of your domain. Knowing where these problem spots are makes it easier to fix internal links or set redirects. I'll show you different ways to view where people are hitting these error pages and where they are coming from, either through google analytics error tracking your existing setup or by using Google Tag Manager to fire events or virtual pageviews. 404 - User Not Impressed As a web user, there’s a good chance that you've been acquainted with the ominous "404 Page Not Found" error. They come in many flavors, sometimes with illustrations, sometimes with a site search to help find what you were looking for and sometimes it is just a white page with unfeeling black, bold letters. Some causes of 404 errors come from A manually mis-typed URL path Third-party sites linking to nonexistent or removed pages Old links from social media platforms (scroll down your Facebook page to 2006, some links you shared might not be valid anymore!) Errors with internal links No matter how cute or whimsical the page is, a ‘page not found' error disrupts the user experience. These 404 pages are not actual pages on a site - they are a result of a status code response on the server side and can be thought of as an alert rather than a fixed page. So how can you know if visitors to your site are experiencing these errors? Easy, Existing Options In Google Analytics, you may already see the page path that the user attempted to access. If it is an old
DataSending Data to Google AnalyticsUsing PluginsDebuggingTracking common user interactionsPage TrackingEvent TrackingSocial InteractionsApp google error 404 / Screen TrackingUser TimingsException TrackingAdvanced TopicsCookies and google analytics api User IdentificationCross-domain TrackingCustom Dimensions and MetricsRenaming the Global (ga) ObjectWriting PluginsTasksIP AnonymizationUser webmaster tools google Opt-outOfficial PluginsDisplay FeaturesEcommerceEnhanced EcommerceEnhanced link attributionLinkerSolutionsSingle Page ApplicationsContent ExperimentsResourcesCookie UsageLimits and Quotas FundamentalsAdding analytics.js to Your SiteHow analytics.js WorksCreating http://www.lunametrics.com/blog/2014/08/19/404-errors-google-analytics-google-tag-manager/ TrackersGetting and Setting Tracker DataSending Data to Google AnalyticsUsing PluginsDebuggingTracking common user interactionsPage TrackingEvent TrackingSocial InteractionsApp / Screen TrackingUser TimingsException TrackingAdvanced TopicsCookies and User IdentificationCross-domain TrackingCustom Dimensions and MetricsRenaming the Global (ga) ObjectWriting PluginsTasksIP AnonymizationUser Opt-outOfficial PluginsDisplay FeaturesEcommerceEnhanced EcommerceEnhanced https://developers.google.com/analytics/devguides/collection/analyticsjs/exceptions link attributionLinkerSolutionsSingle Page ApplicationsContent ExperimentsResourcesCookie UsageLimits and Quotas Products Google Analytics Tracking analytics.js Guides Exception Tracking This guide describes how to send exceptions using analytics.js. Exception tracking allows you to measure the number and type of crashes or errors that occur on your property. Implementation Exception hits can be sent using the send command and specifying a hitType of exception. The send command has the following signature for the exception hit type: ga('send', 'exception', [fieldsObject]); Exception fields The following table summarizes the exception fields: Field Name Value Type Required Description exDescription text no A description of the exception. exFatal boolean no true if the exception was fatal. Example The following command wraps some log
Products Google Analytics Reporting Core Reporting API Reference Error Responses There is an updated version of the Google Analytics Reporting API. We recommend migrating your code today to https://developers.google.com/analytics/devguides/reporting/core/v3/coreErrors take advantage of the new API's key features. Standard Error Responses If a Core Reporting API request is successful, the API returns a 200 HTTP status code along http://www.forthea.com/google-analytics-tutorial-how-to-find-404-errors-on-your-website/ with the requested data in the body of the response. If an error occurs with a request, the API returns an HTTP status code and reason in the google analytics response based on the type of error. Additionally, the body of the response contains a detailed description of what caused the error. Here's an example of an error response: 400 invalidParameter { "error": { "errors": [ { "domain": "global", "reason": "invalidParameter", "message": "Invalid value '-1' for max-results. Value must be within the range: [1, 1000]", "locationType": google analytics error "parameter", "location": "max-results" } ], "code": 400, "message": "Invalid value '-1' for max-results. Value must be within the range: [1, 1000]" } } Note: The description could change at any time so applications should not depend on the actual description text. The following list shows the possible error codes, reasons, corresponding descriptions, and recommended action. Code Reason Description Recommended Action 400 invalidParameter Indicates that a request parameter has an invalid value. The locationType and location fields in the error response provide information as to which value was invalid. Do not retry without fixing the problem. You need to provide a valid value for the parameter specified in the error response. 400 badRequest Indicates that the query was invalid. E.g., parent ID was missing or the combination of dimensions or metrics requested was not valid. Do not retry without fixing the problem. You need to make changes to the API query in order for it to work. 401 invalidCredentials Indicates that the auth token is invalid or ha
Guides Blog About Our Name Our Philosophy & Process Our Team Careers Contact (713) 568-2763 Services Pay Per Click Advertising Search Engine Optimization Analytics & Reporting Web Design & Development Media Planning & Buying Social Media Marketing Interactive Marketing Consulting & Strategy Portfolio Digital Marketing Guides Blog About Our Name Our Philosophy & Process Our Team Careers Contact Google Analytics Tutorial: How to Find 404 Errors on Your Website Forthea Interactive Marketing > Analytics > Google Analytics Tutorial: How to Find 404 Errors on Your Website Google Analytics Tutorial: How to Find 404 Errors on Your Website Posted by Ryan Chauvin on May 28, 2014 in Analytics 6 Comments Share this article: 5 Every webmaster knows that 404 errors are simply a part of life on the web, and while they're easy to ignore, there's real value in learning how to find 404 errors on your website. Together, these isolated problem spots can paint a larger picture and help you identify areas in which you can improve your website. How to Find 404 Errors on Your Website with Google Analytics If you're looking for a solution to this ubiquitous problem, you've come to the right place. We've devised an eloquent way to take the first step in identifying the 404 errors on your site. This incredibly handy error report works on any Googel Analytics (GA) account and can save you the hassle of digging to find active 404 errors. Before we start, make you're logged into the GA account in question and click here: https://www.google.com/analytics/web/template?uid=Vwha4sfrRxS2Qg7f6Mokqg Select the profile view you'd wish to run the report with (we'll wait). Now initially, the report will show no data, but don't panic. We're not done yet. Find the edit tab at the top left of the report: This will bring you to the edit custom report screen. You'll need to scroll to the bottom and find the Filters section. To make this report work for you, you'll first need to go to your website and navigate to a page that doesn't exist. We’re fond of http://www.yourwebsite.com/whatever, but feel free to run wild with creativity here. Once you've found a 404 screen, just identify the page title (highlighted below). At Forthea, we've kept things simple and gone with the classic "404 Error" title. We like to think we made up for it with the ever-adorable basket full of kittens. Returning to the GA custom report edit screen, you'll just need to include the 404 error title as a filter and save the custom report, and voila! A complete list of all the URLs that prod