If you are looking for general Analytics help such as help with installing or troubleshooting the tracking code, you can visit our Help Center
http://www.google.com/support/analytics/
For users of our Data Export API, we have a list of FAQs in two categories:
The Google Analytics Data Export API is free. We intend to always provide a basic level of service for free. As we continue to build out more advanced features and functionality, we may revisit this later.
The Google Analytics Data Export API is designed to allow you to export your data. Once you have it, you can visualize it however you'd like. There are a few Google projects that might help you:
Yes, the API exposes the vast majority of the data in your account, but there is some data we are still working to provide. Some of our beta features, like Event Tracking, are not yet available through the API. If you have feedback for us, we invite you to leave feedback on our Google Group.
The API does have some quota limits in place to make sure we provide everyone with an equitable level of service. For more information, see: http://code.google.com/apis/analytics/docs/gdata/1.0/gdataProtocol.html#requirements.
The API data is refreshed as frequently as the data you'll find in our Web UI, which is updated throughout the day.
No, the Analytics API does not provide access to raw hit-level data; it only exports the same level of data found in our Web UI.
A small subset of all AdWords data is available in Google Analytics. This data can be exported with the Analytics API. To export all your AdWords data or manage your ad campaigns, you must use the AdWords API.
Yes, the API will provide the same data you'll find in the Analytics Web UI. When the Web UI returns you sampled data, so will the API. For more information on sampling, see our documentation on Sampling.
While in labs, our API will remain subject to change. In most cases, we will do our best to give customers at least one month advance notice to migrate to new API releases before we remove or deprecate old functionality. In unusual cases such as where our internal systems are affected or our ability to provide a high level of service to our end users, we reserve the right to make changes on shorter notice. As usual, usage of our API is governed by our Developer Terms of Service.
You can use _setVar(newVal) in your ga.js file (http://code.google.com/apis/analytics/docs/gaJSApi.html) to set the session ID, and use the dimension ga:userDefinedValue to extract the value. Then you can then use this dimension value to correlate with your database. See the documentation on custom visitor segments for details.
|
com.google.gdata.util.ParseException: Invalid root element, expected
(namespace uri:local name) of (http://www.w3.org/2005/Atom:feed). . .This is usually the result of a typo in the URL to the Analytics feeds service. Be sure to check that your URL uses feeds in the plural form. For example, instead of
using
String url = "https://www.google.com/analytics/feeds/data?ids=ga:1174"
you might have
String url = "https://www.google.com/analytics/feed/data?ids=ga:1174"
The second fragment uses feed instead of feeds. This causes a redirect to the main Google search page at http://www.google.com/, which the client library tries to parse and fails. The path component of the URL should be exactly /analytics/feeds/data or /analytics/feeds/accounts/default.
It's better to use the client library to login, and then use a regular java.net.HttpURLConnection to connect to the server to get the XML. For example,
AnalyticsService service = new AnalyticsService("RawFeeds");
String token = service.getAuthToken("username", "password", null, null, "analytics", "RawFeeds");
URL url = new URL("https://www.google.com/analytics/feeds/data?ids=ga:1174"
+ "&start-date=2008-10-11&end-date=2008-10-12"
+ "&dimensions=ga:city&metrics=ga:pageviews");
HttpURLConnection conn = (HttpURLConnection) url.openConnection();
conn.addRequestProperty("Authorization", "GoogleLogin Auth=" + token);
InputStream in = new BufferedInputStream(conn.getInputStream());
// now you can read the XML from this input stream, or pass it to a parser,
// or transform it with XSLT, or whatever
Most likely, you need to add an img tag that loads an image from the same path as the HTML document. For example:
<img style="visibility:hidden" src="__utm.gif" alt="required for GData"/>
This is a requirement for all Javascript GData products. See http://code.google.com/apis/gdata/client-js.html#AuthenticationAuthSub.
A 503 response means for some reason we can't process your request right now and you should wait and try again later. The most common reason for this is that you have exceeded your quota limit. Please see the quota limit policy for more information.
A 500 response means we've encountered an internal error. Don't worry, we log and monitor all errors. If you want to, you can also share your results with us on our Google Group.
A 400 response is most likely a bug in your code. Most of the time a parameter in the URL query string is invalid. For example, you might have dimension parameters listed twice, a malformed regular expression in the filters parameter, or a start date that precedes the end date. Check the body of the HTTP response for additional information.
Not all metrics and dimensions are compatible. For example, it is not possible to combine ga:city and ga:CPC. Google analytics does not calculate cost per click data by city. See the Dimensions and Metric Reference for the complete description of which dimensions and metrics are compatible.