Event Tracking Dimensions Return 0 for Ecommerce Metrics

[GoogleCodeExporter]

--------------------------------------------------------------------------
NOTE: This issue tracking system is for developer products only.  If you
are not a developer/programmer and have a problem with a Google web site,
please report the problem to the appropriate group.  More information can
be found here: http://www.google.com/support/
--------------------------------------------------------------------------

Name of API affected:
Analytics Data Export API

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

Steps to reproduce issue:
1.Use :   ga:eventAction, or any event tracking dimension
2.Use any Ecommerce metric and it returns all ZEROS
3.

Expected output:
What do you expect to see after performing the above steps?
The same results as the Google Analytics Interface not just zeros.  The 
interface shows 12 
transactions and $1000 revenue but the API shows 0 and 0.

Actual results:
What do you actually see after performing the above steps?
The interface shows 12 transactions and $1000 revenue but the API shows 0 and 0.

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

Original issue reported on code.google.com by lineback...@gmail.com on 17 Feb 2010 at 5:46

[GoogleCodeExporter]

This should return all zeros.

Our data model has visitors -> sessions -> hits : where there are different 
types of hits.

Events are hits of "event" type
Transactions are hits of "trans" type

So there is no basic relationship between these two values in the backend data 
model.

The best bet would be to create an advanced segment for the event dimension. 
This will return all sessions in which the event occurred then you can create a 
report of total revenue for that session.

Original comment by nickski1...@gmail.com on 6 Jun 2011 at 4:54

• Changed state: Invalid

[GoogleCodeExporter]

Removing an obsolete label that was used when these issues were in the 
gdata-issues project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:04

• Removed labels: API-Analytics