AbdFatah / analytics-issues

Automatically exported from code.google.com/p/analytics-issues
0 stars 0 forks source link

Transaction Metric values incorrect when using pagPath Filter #287

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
---------------------------------------------------------------------------
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.):

Issue summary:
Provide a brief summary of the issue you're experiencing.

When Querying on the metric ga:transactions with a filter using ga:pagePath 
regex to filter results the number of results increases instead of being a 
subset.

Steps to reproduce issue:
1. Query API without filter: 
https://www.google.com/analytics/feeds/data?oauth_version=1.0&dimensions=ga%3Aye
ar%2Cga%3Aweek&start-date=2012-11-01&max-results=10000&sort=ga%3Ayear%2Cga%3Awee
k&end-date=2013-04-27&metrics=ga%3Atransactions
2. Query API with filter: 
https://www.google.com/analytics/feeds/data?oauth_version=1.0&dimensions=ga%3Aye
ar%2Cga%3Aweek&start-date=2012-11-01&max-results=10000&sort=ga%3Ayear%2Cga%3Awee
k&end-date=2013-04-27&metrics=ga%3Atransactions&filters=ga%3ApagePath%3D~search
3. compare total metric count in the results xml

Expected output:
What do you expect to see after performing the above steps?

The query with the filter should contain a lower value than the one without the 
filter.

Actual results:
What do you actually see after performing the above steps?

The query with the filter has a much larger value: 21602 vs 5437

Notes:
Provide any additional information which might be useful here. Feel free to
attach screenshots or sample code which demonstrates the issue being
described.

We are using an old version of the API and will be upgrading to the latest 
version soon. I will redo this test and update this ticket when we complete the 
upgrade.

Original issue reported on code.google.com by nvecchia...@rjmetrics.com on 22 Apr 2013 at 3:10