Support Combinations of Ecommerce Dims/Mets with Visitor and Content Dims/Mets

[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

Request summary:
Provide a brief summary of the the feature you'd like to see implemented.

http://groups.google.com/group/google-analytics-data-export-api/browse_thread/th
read/1314abd76c6979b0

Use Cases:
Describe how you will use this feature if implemented.

GA Ecommerce collects a transaction ID. This ID is also sent to a
customer's backend ecomm system. Being able to query Campaign by
TransactionID would allow developers to join campaign data with other
(internal to the developer) data on the transaction id key.

Original issue reported on code.google.com by nickski1...@gmail.com on 3 Sep 2009 at 9:14

[GoogleCodeExporter]

Original comment by nickski1...@gmail.com on 4 Sep 2009 at 9:36

• Changed state: 2049398

[GoogleCodeExporter]

This data can be generated in a Custom Report, with a drilldown dimension, but 
the 
drilldown cannot be exported. Is this part of a larger issue with not being 
able to 
export drilldown data - or is this specific to this combination?

Original comment by dowgirl...@gmail.com on 7 Sep 2009 at 12:52

[GoogleCodeExporter]

This may, or may not, be a related item but It seems very similiar. To me that 
when you are using campaign tagging to the full extent on your site; Campaign 
name, source, terms, content and keywords - You should be able to use the api 
to query this same data.  This seems to be a huge flaw.  I can successfully 
combine name, content, source and terms to generate reports, but as soon as I 
use the AdContent field to distinguish my last level of details between tracked 
links I receive the dreaded "Illegal combination of dimensions and metrics".  

I am not sure why this occurs since i can parse this data using the web client. 
 We have a custom CMS in my work place and all redirect and campaign tracking 
URLS are tracked and reported through a centralized interface.   

Original comment by jason.sc...@gmail.com on 15 Jul 2010 at 8:31

[GoogleCodeExporter]

Jason-
Can you be more specific?
Your Dimensions are:
ga:campaign
ga:source
ga:adContent
"terms"
"content"
ga:keyword

what are the dimensions you're referring to as "terms" and "content", if not 
keyword and adContent?  And what metrics are you querying for?

Original comment by api.alex...@gtempaccount.com on 15 Jul 2010 at 10:25

[GoogleCodeExporter]

Hello,

I am also being affected by this issue:
The analytics group at my company populate their datawarehouse with Google 
Analytics Ecommerce content in order to perform in-house marketing analysis & 
reporting. 

To save them time, I am trying to create an automated tool that will save them 
the time from having to manually export the report and populate the db.

Dimensions:
ga:transactionId,ga:source,ga:medium,ga:campaign,ga:keyword,ga:adContent,ga:visi
torType,ga:landingPagePath

Metrics:
ga:itemRevenue,ga:transactionTax,ga:transactionShipping,ga:itemQuantity

The data needs to be organized with ga:transactionId as the key.

Taking the 7 dimension limit into consideration, my queries to the DataExport 
API fail anytime time I include ga:adContect or ga:landingPagePath in the 
'dimensions' argument.

Error: Bad request - Illegal combination of dimensions and metrics

For the team, it is very important to have ga:adContent and ga:landingPagePath 
keyed to ga:transactionId.

Is there a work-around for this issue? What are the chances that this will be 
fixed in the near future?

Any feedback would be greatly appreciated.

Thank you!
-Ivan

Original comment by ivan.len...@gtempaccount.com on 24 Sep 2010 at 8:35

[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

[GoogleCodeExporter]

Changing the issue type to match the organization desired in this project.

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

• Added labels: Type-Feature

[GoogleCodeExporter]

i am also affected by this.

is there any workaround?

Original comment by royc...@singtel.com on 25 Jan 2012 at 8:57

[GoogleCodeExporter]

I have found this issue by trying to analyse the average purchase price from a 
split test campaign where the separating variable was ad content. I was 
surprised to see that medium, source, campaign are linked to transactions but 
not ad content.

I add my vote to this as well.

Original comment by appleana...@gmail.com on 20 Jun 2012 at 4:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi,

We would like to query ecommerce metrics ga:transactions and ga:itemRevenue 
with the dimension combination 
ga:date,ga:source,ga:medium,ga:campaign,ga:adContent,ga:productSku. With the 
above combinations getting the error as 'Selected dimensions and metrics cannot 
be queried together'. Is there a workaround for this issue?

Thank you!

Original comment by sbga.2...@gmail.com on 7 Feb 2013 at 1:20

[GoogleCodeExporter]

Same here, especially with Google's focus on ecommerce it seems like adContent 
which is  one of the campaign tracking dimensions should be queri-able with 
transactionId. 

Original comment by anto...@wavonomics.com on 30 Jun 2014 at 5:12

[GoogleCodeExporter]

What exactly can be queried with transaction id?  I am working on an automated 
SSIS package to pull transactionid, hour of day, campaign, adgroup, and keyword 
with the clicks, cost, and impressions metrics, but keep getting invalid 
dimension and combination errors.  Which of these can I query together?

This issue has my vote as well!

Original comment by michael....@citrix.com on 2 Dec 2014 at 4:32