![]() ![]() You can see some additional information as well, like the index, scope, creation date, and last modified date. Use the ga_custom_vars_list function to download a list of all of your custom dimensions and metrics. With a little partnership the Core Reporting API (see the google_analytics_4 function), check that the right data is flowing into all of your custom dimensions and metrics.Document your custom dimensions and metrics for business partners and colleagues.Check that the scope is appropriate for each custom dimension and metric.Custom Dimension and Custom Metrics To-dos In addition, you can view info about how your goals are configured – things like what urls and events you are matching off of. You can basic meta data like name, goal number, goal type, and creation and last modified date. Use the ga_goal_list function to quickly view all of the goals set up in your view. Check that all of your main business objectives are being measured by goals.Document your goal and what they mean for business partners and colleagues.Check that your destination and event-based goals are up to date and still functioning correctly.Check that your goals set up consistently across all views.The ga_filter_view_list function shows you which views these filters are applied to. You can also see some meta-data such as when the filter was created and last updated. ![]() The ga_filter_list function will return a list of all of the filters in your account along with configuration information, such as what type of filter it is, what field you are filtering on, and what filter criteria is being used. Use the ga_filter_list and ga_filter_view_list functions to view a list of the filters you have created and applied in your Google Analytics account. ![]() Double check that your internal traffic filters up to date.Identify any duplicate or unused filters that could be cleaned up or deleted.Ensure that all best practice filters are correctly set up and are being applied appropriately across all views in your account. Identify all of the filters you have in place.You will also see some meta-data such as creation and modified dates as well as various other configuration information such as time zones, excluding bots, site search settings, default page, exclude query parameters, and industry vertical. Use the ga_account_list, ga_webproperty_list, and ga_view_list functions to download a list of all account, property, and view names and ids. Check that site search is consistently and correctly set up on all views.Check that bots are filtered out of all appropriate views.Check that your time zones are set consistently across all views.Create a list of account, property, and view ids for use in other reporting automation tasks.With a little help from the google_analytics_4 function, you can see which properties are still receiving data and which could be renamed as Historical properties or views. Document all of your accounts, properties, and views.For a complete list of functions, check out the googleAnalyticsR help. Listed below are a few common “GA checkup” to-do items and which functions you can use to efficiently complete those tasks. GoogleAnalyticsR provides a number of functions that allow you to download configuration information. You can find a detailed video with instructions on how to do this on the documentation page for googleAnalyticsR. In order to use the googleAnalyticsR package, you will need to create your own Google Developer Project API Key. You will need to install this package through the packages tab in RStudio or by running this code. Java is a registered trademark of Oracle and/or its affiliates.To pull configuration data, we are going to use Mark Edmondson’s googleAnalyticsR package. For details, see the Google Developers Site Policies. POST Ī list of values for the requested metrics.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. Note: Insight reports are limited to 100 localPostNames per call. Which metrics and how they are reported are options specified in the request proto. ![]() Returns insights for a set of local posts associated with a single listing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |