StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10089698
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
24
CommunityOwnedDate
CreationDate
2012-04-10T13:26:22.680
FavoriteCount
0
LastActivityDate
2014-01-07T22:53:56.757
LastEditDate
2014-01-07T22:53:56.757
LastEditorUserId
594319
OwnerUserId
594319
ParentId
9863509
PostTypeId
2
Score
107
ViewCount
0
LastEditorDisplayName
text
Body
<h2>UPDATE July 21st, 2012</h2> Google Analytics API V3 now supports OAuth2 tokens returned by a .p12-signed JWT request. That is, we can now use the Analytics API w/ service accounts. Currently pulling 4 years of day-by-day metrics, just for the hell of it. Here's a quick 'n' dirty step-by-step: <ol> <li>Go to the <a href="https://code.google.com/apis/console/">Google API Console</a> and create a new app</li> <li>In the Services tab, flip the Google Analytics switch</li> <li>In the API Access tab, click Create an OAuth2.0 Client ID <ul> <li>enter your name, upload a logo, and click Next</li> <li>select the Service account option and press Create client ID</li> <li>download your private key</li> </ul></li> <li>Now you're back on the API Access page. You'll see a section called Service account with a Client ID and Email address <ul> <li>Copy the email address (something like ####@developer.gserviceaccount.com)</li> <li>Visit your <a href="https://www.google.com/analytics/web/#management/Accounts/">GA Admin</a> and add this email as a user to your properties</li> <li>This is a must; you'll get cryptic errors otherwise.</li> </ul></li> <li>Get the latest <a href="https://github.com/google/google-api-php-client">Google PHP Client API</a> via Github <pre><code>git submodule add https://github.com/google/google-api-php-client.git google-api-php-client-read-only </code></pre></li> <li>Rock 'n' roll (thanks all for tips on updated class names): <pre><code>// api dependencies require_once(PATH_TO_API . 'Google/Client.php'); require_once(PATH_TO_API . 'Google/Service/Analytics.php'); // create client object and set app name $client = new Google_Client(); $client->setApplicationName(APP_NAME); // name of your app // set assertion credentials $client->setAssertionCredentials( new Google_Auth_AssertionCredentials( APP_EMAIL, // email you added to GA array('https://www.googleapis.com/auth/analytics.readonly'), file_get_contents(PATH_TO_PRIVATE_KEY_FILE) // keyfile you downloaded )); // other settings $client->setClientId(CLIENT_ID); // from API console $client->setAccessType('offline_access'); // this may be unnecessary? // create service and get data $service = new Google_Service_Analytics($client); $service->data_ga->get($ids, $startDate, $endDate, $metrics, $optParams); </code></pre></li> </ol>   original workaround below <hr> <blockquote> It seems that, despite ambiguous documentation, <a href="https://groups.google.com/forum/#!topic/oauth2-dev/NBQoOrtcC6A">most Google APIs do not support service accounts yet</a>, including Google Analytics. They cannot digest OAuth2 tokens returned by a .p12 signed JWT request. So, as of right now, you cannot use Google Analytics API V3 with a service account. Workaround: <ol> <li>In the <a href="https://code.google.com/apis/console/b/0/?pli=1">Google API console</a>, create a client application.</li> <li>Follow the steps in the <a href="https://github.com/google/google-api-php-client">Google PHP Client API</a> examples to generate a <code>client_auth_url</code> using your <code>client_id</code>, <code>client_secret</code>, and <code>redirect_uri</code></li> <li>Login to <a href="https://accounts.google.com/ServiceLoginAuth">Google</a> using cURL. (Be sure to use a cookie file!)</li> <li>Open the <code>client_auth_url</code> in cURL and complete the form. Make sure you set <code>curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 0);</code> and <code>curl_setopt($ch, CURLOPT_HEADER, 1);</code> as the <code>authorization_code</code> will be in the <code>Location:</code> header of the response.</li> <li>Using your <code>client_id</code>, <code>client_secret</code>, <code>redirect_uri</code>, and the activation code from Step 4, post a request to the <a href="https://accounts.google.com/o/oauth2/token">Google's OAuth2 Token machine</a>. Make sure you include <code>grant_type = "authorization_code"</code> in your post fields.</li> <li>Hurray, you now have a <code>refresh_token</code> that never expires, and a working <code>access_token</code>! Post a request to the <a href="https://accounts.google.com/o/oauth2/token">Google's OAuth2 Token machine</a> with your <code>client_id</code>, <code>client_secret</code>, <code>redirect_uri</code>, and <code>refresh_token</code> when your <code>access_token</code> expires and you'll get a new one.</li> </ol> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POService Applications and Google Analytics API V3: Server-to-server OAuth2 authentication?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmoon prism power
UserOwnerUserId
1. USmoon prism power
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POService Applications and Google Analytics API V3: Server-to-server OAuth2 authentication?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.