You are currently viewing Using Google Analytics superProxy to Enhance API Quota Limit

Using Google Analytics superProxy to Enhance API Quota Limit

  • Post published:August 26, 2016

vteam #252 has been working on a client’s web application of tutorial videos for recording, mixing and production, which has been live for a decade. The application holds significant customer information, order history and video data over 350 GB. Users can subscribe for monthly or annual subscription and stream tutorials online, or else they can download a particular product or course. For proper monitoring of different features and rankings of the website, the client required Google analytics implementation.

This implementation was requested to view analytics report on client’s own Dashboard, so that he can analyze the flow of website and keep an eye on different users/agents, places (from where the site is getting maximum hits), mostly viewed videos and successful events. Therefore, a fast, accurate and real-time data from Google analytics was required by using Google analytics reporting API.

A problem occurred due to a limitation i.e., Google analytics reporting API limit users to 10,000 requests per day (profile per view). For real-time reporting and to run separate queries for fetching reports (for browsers, countries and other events), this limit wasn’t enough. Following three options were available to solve this problem:

  1. Multiple accounts creation to change user (if one user reaches it’s limit of per day requests)
  2. Google Analytics paid account
  3. Google Analytics superProxy

Google Analytics superProxy was selected from the available options as it allows a user to publicly share the Google Analytics reporting data. It could be utilized to empower one’s custom Dashboards and widgets, transform responses into various formats, test, etc.

vteams developers Raza Mehdi and Aaqib Javed created a query for client’s Google Analytics data. That query would make the specific reporting data available at a new URL, which could be shared publicly. Therefore, anybody who visits that particular URL will then have the access to reporting data (without any authorization).

Let’s say if the client wanted to retrieve the top 10 browsers based on pageviews for the past week, one query will be created for it and another query will be created for the number of sessions for the previous day, and so on. It’s totally on the client now to decide which queries he wants to make public and how often he wants the data to be updated. Google Analytics superProxy will take care of everything then.