Open GoogleCodeExporter opened 8 years ago
By reading the GA docs I came to the conclusion that this is a limitation of
the measurement protocol and therefore GA itself.
You can find the relative document here:
https://developers.google.com/analytics/devguides/collection/protocol/v1/paramet
ers
The description of the "Product Action List" parameter says that the product
list of a product impression object only gets attributed to the "detail" and
"click" actions.
In other words, if you send the "Product Action List" parameter alongside a
"Product Action" parameter whose value is anything else except "detail" or
"click", then it's highly likely that the issue you described will appear in
the "Product List Performance" report.
Using the example illustrated here:
https://developers.google.com/analytics/devguides/collection/analyticsjs/enhance
d-ecommerce
This command won't work in our case:
ga('ec:setAction', 'add', {list: 'Search Results'});
But this will:
ga('ec:setAction', 'click', {list: 'Search Results'});
The problem occurs when the user inserts the product to his cart ("add" action)
without interacting ("click" action) or viewing the details of ("detail"
action) of it.
One solution would be to send two events with similar GA ecommerce parameters
when a user adds the product directly to his cart. The prior would be an
interactive and the latter a non interactive event or vice versa.
Here's an example:
I'm logged into a ecommerce website, just landed on a web page and viewed all
of the page's products (pageview with relevant enhanced ecommerce impression
data is already sent). I now add a product with the product list "TVs" to my
cart. At this moment two GA events should be fired:
1) One with ga('ec:setAction', 'click', {list: 'TVs'});
2) The other with ga('ec:setAction', 'add', {list: 'TVs'});
Original comment by george.p...@gmail.com
on 5 May 2015 at 9:00
I managed to get this working by adding the action field attribute to the
dataLayer call. Like this:
dataLayer.push({
'event': 'addToCart',
'ecommerce': {
'currencyCode': 'EUR',
'add': {
'actionField': {'list': 'Search Results'},
'products': [{
'name': 'Triblend Android T-Shirt',
'id': '12345',
'price': '15.25',
'brand': 'Google',
'category': 'Apparel',
'variant': 'Gray',
'quantity': 1,
'list': 'Search Results'
}]
}
}
});
That worked for me.
Original comment by ardent.a...@ardentleisure.com
on 8 Sep 2015 at 3:51
I had the same problem and was stuck for hours.
My issue was that I had the checkout process on a different subdomain than
where the product impressions was listed and clicked on.
By simply adding a field on the GA page view tag i GTM, "cookieDomain" =
"auto", all started working.
http://www.lunametrics.com/blog/2015/06/16/cross-domain-tracking-with-google-tag
-manager/
The only places I needed to add information about the list, was:
- product impressions list. "'list' : 'Search result'"
- product click (from impressions list). 'actionField': {'list': 'Search
Results'},
I did not add it for product detail, or anything in the checkout process (add
to cart, checkout, purchase).
For other external domains in the checkout process I guess you will need cross
domain tracking.
Original comment by asgaut.m...@cityhotels.no
on 11 Sep 2015 at 10:46
[deleted comment]
We're having the same problem.
We've tried all of the suggestions above, but are still seeing a large number
of (not set)'s showing around (45%) for the product checkouts list.
Original comment by lee.jaco...@gmail.com
on 5 Nov 2015 at 5:50
Issue 750 has been merged into this issue.
Original comment by mcoh...@google.com
on 6 Nov 2015 at 9:40
I have the same problem,
Original comment by thebabyc...@gmail.com
on 18 Nov 2015 at 2:20
[deleted comment]
Same here. Currently experiencing a very high volume of revenue associated to
product list name set as "(not set)". Looking forward to see if GA tech team
will be fixing this soon.
Original comment by johnan...@gmail.com
on 18 Nov 2015 at 9:21
Original comment by pfrise...@google.com
on 6 Jan 2016 at 11:36
553
Original comment by Jason.Su...@gmail.com
on 5 Mar 2016 at 9:26
Original issue reported on code.google.com by
vincent....@gmail.com
on 18 Dec 2014 at 9:41