Advanced Segments - 403 User does not have sufficient permissions for this advanced segment.

[GoogleCodeExporter]

---------------------------------------------------------------------------
NOTE: This issue tracking system is for Google Analytics developer products
only.
If you are not a developer/programmer visit:
http://www.google.com/analytics/support.html
---------------------------------------------------------------------------
Name of affected component: Core Reporting API

Name of related library and version, if applicable (e.g. Java, Python,
HTTP, Objective-C, etc.): N/A

Issue summary:
Google.Apis.Requests.RequestError User does not have sufficient permissions for 
this advanced segment. [403]

We generated an API Project/Access at the console - via Google Account that is 
an Administrator on the GA Account.  It is an "Installed Application". We have 
all Oauth2.0 requirements working as designed for the refreshing of tokens and 
processing requests.  Once we attempt to use advanced segments we hit this bug.

Dynamic segments or filters are out due to the maximum 2048 characters. 

The same requests do not work within the API Query Explorer. 

In "Steps to reproduce issue:" below, I am obtaining the values for gaid via 
the GA portal when editing an advanced segment: "asset>Advanced Segment>" found 
in breadcrumb.  I find the 752476149 segment under another administrator user 
log-in (not used to generate API Project) within the accounts and profiles.  I 
find the 80375959 segment when I use the log-in that generated the API Project.

Steps to reproduce issue:
1.Log In https://code.google.com/apis/console/ as user that generated API 
Project 
2.Segment (gaid::752476149) works in API but not in the Query Explorer.
3.Segment (gaid::80375959) works in API but not in the Query Explorer.
3.

Expected output:
Same results

Actual results:
Different results

Notes:
This has been documented here: 
https://groups.google.com/forum/?fromgroups=#!topic/google-analytics-data-export
-api/nN0dpgUPp40

Advanced segments and their unique ID used in the API request URL.  When I 
share a segment, it generates a unique ID - sharing does not rectify this 
issues.  We wish to "silo" an Advanced Segment to the GA Account so if we are 
not longer administrators the API will continue to function as designed. 

Original issue reported on code.google.com by okiebug1...@gmail.com on 21 Mar 2013 at 12:20

[GoogleCodeExporter]

Once I perform the OAuth with the credentials of the owner of the GA advanced 
segments, it works.  Not a bug if this is the intended treatment for GA 
advanced segments.  Confusion on GA Advanced Segments use in the API and what 
is supposed to be exposed for an account/profile via the users added to the 
account and subsequently authenticated via OAuth for the API's functions in 
reporting data. 

Original comment by okiebug1...@gmail.com on 22 Mar 2013 at 11:32

[GoogleCodeExporter]

Was the problem solved?

Original comment by a.bori...@artox.com on 24 Apr 2013 at 1:43

[GoogleCodeExporter]

Comment #1 outlines how we were able to work with the mandate of advanced 
segments ownership.  Our OAuth token is generated for the user profile that 
owns/created the advanced segments. 

Original comment by okiebug1...@gmail.com on 24 Apr 2013 at 2:31