Two new versions of the Google Analytics Management API into public beta released today: “a brand new version 3.0 and a backwards compatible version 2.4.”
“Both new versions migrate the Management API from the existing Google Data Protocol to Google’s new discovery-based API infrastructure. This impacts the way you request and handle data from the API,” announced Google Analytics API Team.
According to Analytics team, “The biggest changes in switching to the new versions are that you now need to register your applications via the Google APIs Console and use a developer token. Also, the URL endpoints have changed, which influence how you request OAuth authorization tokens.”
In addition, the Analytics team also announced the “deprecation of the legacy version 2.3 of the Management API. It will continue to work for 2 months, after which all v2.3 requests will return a v2.4 response.”
All future development of the API will be done to version 3.0, so we also added some interesting new data, including:
- Event goals are fully represented.
- An internal web property id that can be used to deep-link into the Google Analytics user interface.
- Profile configurations for the default page and site search query parameters.
- A faster response over version 2.3
- An improved quota policy
- Integration with the Google APIs console to manage API access and request more quota
- OAuth 2.0 is now the recommended way to Authorize users
- The URL to make requests is now at https://www.googleapis.com/analytics/v3/management/…
- The API response is more compact using JSON
- New Google API client libraries, which support many more languages
- Support for the Google Discovery API
The Analytics team writes, “The future of our APIs is to access all configuration data through the Management API and all processed report data through the Data Export API. So for now, if you are already using the Management API, we recommend you migrate to the latest and greatest version 3.0.”
“If you are still using the Account Feed in the Data Export API, we highly recommend you test out the new Management API and start planning your migration. But, you can probably wait to do a full migration until all our APIs are on version 3.0.”