v2.4 API - Metric / dimension name changes

[GoogleCodeExporter]

Name of affected component: Core Reporting API

Issue summary:
Hey, guys!
We have an old app that uses the v2.4. API.
Yesterday it had heap of problems - mostly connectivity issues.
They seem to be resolved today (06/06/2013) but there seem to be changes to the 
metric names / dimension names.
While we fixed the mapping from dimension / metric name to our internal enums 
to happen case insensitive we are a bit worried if there will be other changes 
/ outages for the v.2.4 API?

Steps to reproduce issue:
1. Create an app that uses the dimensions / metrics shown in 
https://developers.google.com/analytics/devguides/reporting/core/dimsmets#cats=p
agetracking
2. You will notice some of the metric names / dimension names differ (capital 
vs. small letters). For example "ga:pageviews" (in the manual) vs. 
"ga:Pageviews" from the service.

Expected output:
Metric names / Dimension names should be the same in the documentation and the 
service output. Also it will be great if changes to the API output are 
mentioned in an official document so developers can 

Actual results:
Difference in the metric / dimension names.

Notes:
We're aware that we can just check things case insensitive, we're worried if 
there will be other changes (like renaming existing metrics / dimensions) or 
removing any of them. Adding new dimensions / metrics won't affect us.

Thanks a lot!

Original issue reported on code.google.com by donchevp@gmail.com on 6 Jun 2013 at 1:46

[GoogleCodeExporter]

can you provide an example? The query and the response received that shows the 
behavior you're describing.

Original comment by pfrise...@google.com on 6 Jun 2013 at 3:22

[GoogleCodeExporter]

Thanks for the fast response.
Attached is a file with the response (some ids stripped).
Note the metric ga:Pageviews returned. It starts with capital P which isn't the 
same as in the documentation.

Although on a second look it seems to me that the service echoes the dimension 
names / metric names you passed with the request so the whole story may be just 
a bad input issue and slightly.

Also how much time do we have to switch to 3.0? 
Will the 2.4 service be retired anytime soon and should we expect any changes 
to it in the near future?

Once again thanks a lot for your time! 

Original comment by off...@eveliko.com on 6 Jun 2013 at 4:58

Attachments:

• sample_file.txt

[GoogleCodeExporter]

this is expected behavior. it is case insensitive.
As you discovered, whatever input you use will then be returned in the response.

Original comment by pfrise...@google.com on 6 Jun 2013 at 6:26

• Changed state: WontFix