{"id":4793,"date":"2014-06-09T14:47:50","date_gmt":"2014-06-09T14:47:50","guid":{"rendered":"https:\/\/www.gosquared.com\/blog\/?p=4793"},"modified":"2019-11-28T12:09:24","modified_gmt":"2019-11-28T12:09:24","slug":"api-update-trends-custom-dates","status":"publish","type":"post","link":"https:\/\/www.gosquared.com\/blog\/api-update-trends-custom-dates","title":{"rendered":"API update: Custom dates for Trends"},"content":{"rendered":"

When we re-launched our homepage last month with the headline ‘easy to use real-time web analytics’, we weren’t simply referring to the dashboards our customers use everyday. We’ve always taken great pride in providing APIs that are similarly a joy to use.<\/p>\n

For the non-engineers reading this post, API stands for application programming interface and it puts the power of our analytics engine in the hands of anyone who wants to develop with it. While this post will primarily be of interest to GoSquared developers, anyone can get started using our APIs, for example to extract historical data with live examples in our documentation.<\/a> <\/p>\n

Since launching V2 of our Trends API last October, we’ve had tons of great feedback from the community. We’re thrilled to hear that our customers love the API for its speed, developer-friendly structure and powerful data resource. We want to support developers using the API as much as possible and there was one niggling limitation that has been cropping up in feedback.. The greatest limitation with the current Trends API has been the inability to query dimension data for a custom time period (except for the “aggregate” dimension, which was supported).<\/p>\n

As a reminder, in Trends a dimension is a bunch of metrics broken down by a certain attribute. So, for example, you might have total website visits broken down by browser, and that would look like the following:<\/p>\n

https:\/\/api.gosquared.com\/trends\/v2\/browser?api_key=demo&site_token=GSN-106863-S&limit=3<\/code><\/p>\n

\r\n{\r\n  \"list\": [{\r\n    \"id\": \"chrome\",\r\n    \"browser\": \"chrome\",\r\n    \"metrics\": {\r\n      \"visits\": 245618\r\n    }\r\n  }, {\r\n    \"id\": \"firefox\",\r\n    \"browser\": \"firefox\",\r\n    \"metrics\": {\r\n      \"visits\": 45777\r\n    }\r\n  }, {\r\n    \"id\": \"mobilesafari\",\r\n    \"browser\": \"mobilesafari\",\r\n    \"metrics\": {\r\n      \"visits\": 37816\r\n    }\r\n  }],\r\n  \"cardinality\": 27,\r\n  \"dimension\": \"browser\",\r\n  \"range\": {\r\n    \"from\": \"2014-06-02T00:00:00\",\r\n    \"to\": \"2014-06-09T23:59:59\"\r\n  },\r\n  \"interval\": \"day\"\r\n}\r\n<\/code><\/pre>\n
The News<\/h2>\n
I’m glad to announce that we have implemented custom time period querying on all dimensions, now live on the Trends API.<\/p>\n
Usage<\/h2>\n
To control the start and end time for the query, include the from<\/code> and to<\/code> parameters in the request. For example:<\/p>\n
http:\/\/api.gosquared.com\/trends\/v2\/browser?api_key=demo&site_token=GSN-106863-S&from=2014-04-01&to=2014-05-23<\/code><\/p>\n