Closed (fixed)
Project:
Google Analytics
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Sep 2006 at 14:59 UTC
Updated:
17 Oct 2006 at 10:30 UTC
There seems to be a problem getting segmentation data. I'm only getting colons ":" instead of profile variables.
Comments
Comment #1
buddaI've just incstalled the 4.7 version of google analytics on a clean 4.7 Drupal install.
I tested with a plain text field profile value, and a list selection value.
Both of these profile values were then selected to appear in the segmentation variable.
Tests showed them appearing as expected in the footer of the site pages.
What sort of profile values are you trying to include in the segmentation variable?
Comment #2
JoshLangner commentedDid some checking. Still getting strange ":" instead of any kind of variable. These are from custom profile fields, but only text (i.e. letters, numbers, etc.).
Also, is there a way to separate multiple profile values? Right now, multiple values look like "value1:value2" in GA. I would rather they were added separately (i.e. "value1" + "value2"), so I could filter them individually in GA.
Comment #3
buddaTaken from my source:
Hence the use of the ':' which you are seeing in the generated javascript code.
As for the bug - if you create a fresh Drupal install withthe module, and profile module, can you recreate it the problem? I couldn't.
Do you have any starange characters in your profile field names?
Comment #4
buddaMy "source" was http://cutroni.com/blog/2006/07/25/custom-segmentation-with-google-analy... (for reference)
Comment #5
JoshLangner commentedLooks like your update might have solved the ":" for non-authenticated users--perhaps this was the problem I had. I just installed the module today and am waiting to see the new data.
Comment #6
buddaYeah showing profile data for an anonymous user isn't really possible, so I added a check for this in the code to prevent the empty ':' from showing.
It would have helped locate this issue if your report mentioned it only appearing when nobody was logged in :)
Comment #7
(not verified) commented