We periodically update the Google Analytics Metadata API in order to deliver new features and to repair defects discovered in previous versions. In most cases, these changes will be transparent to API developers. However, occasionally we need to make changes that require developers to modify their existing applications.
This page documents any changes made to the Google Analytics Metadata API that might affect your application. We recommend that API developers periodically check this list for any new announcements. You can also subscribe to changes via the feeds listed under the Subscribe section below.
Subscribe To Related Changelogs
Includes all Collection, Configuration, and Reporting APIs.
This release adds a new attribute
Added in API Version
addedInApiVersionis a numeric attribute which can be used to check whether a column can be used in a reporting API of a specified version; see the Metadata API - Developer Guide for details.
This release includes a naming convention change for the
- The uiName attribute for templatized columns now uses
XXto represent the numeric index instead of
1. For example,
Goal 1 Valueis now
Goal XX Value.
This release includes the deprecation of the
appUiName attribute. Review the Data Deprecation Policy for details on attribute removal:
appUiNamehas been deprecated. It is no longer required in the Metadata API because UI names for web and app views (profiles) have been unified. You should remove any code that uses the
appUiNameattribute and only use the
This is the initial release of the Metadata API:
- The Metadata API returns information about the dimensions and metrics exposed in Google Analytics reporting APIs. The metadata returned includes attributes like UI name, description, advanced segments support, and more. By using the Metadata API, your applications can automatically stay up to date with the latest data on the dimensions and metrics available for reporting queries. Visit the Metadata API Overview for more details.