---------------------------------------------------------------------------
NOTE: This tool is not designed to request help. It is only for reporting
issues and requesting features for the Google Analytics libraries.
If you are a developer and you need help, visit:
https://developers.google.com/analytics/help/
If you are not a developer and you need help, visit:
https://support.google.com/analytics
---------------------------------------------------------------------------
Name of affected component: Core Reporting API
Name of related library and version, if applicable (e.g. Java, Python,
HTTP, Objective-C, etc.): Ruby gem 'google-api-client' v. '0.7.1'
Issue summary:
Some custom segments began to stop working when used in an API call. These
custom segments are returned by the API when a list of them is requested for a
certain Analytics account, but they do not work when the segmentId is used in a
metric request.
Steps to reproduce issue:
1. Make an API metric call using the segmentId: "gaid::3KIi0B95QtSA_TDqROwmvA"
(one of the custom segment IDs that stopped working).
Expected output:
A 200 result with a value.
Actual results:
A 403 error with error message: "insufficient_scope".
Notes:
Making an API call using the segment definition works as intended, but not
every segment definition can be used in an API call.
Original issue reported on code.google.com by keet...@automatedinsights.com on 13 Jan 2016 at 7:16
Original issue reported on code.google.com by
keet...@automatedinsights.comon 13 Jan 2016 at 7:16