Comments on: What are our members doing? http://www.elephantsandanalytics.com.au/blogposts/what-are-our-members-doing/ "Elephant in the corner" is an English idiom for an obvious truth that is being ignored or goes unaddressed. Wed, 02 May 2012 02:59:10 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Lisabeth Evers http://www.elephantsandanalytics.com.au/blogposts/what-are-our-members-doing/comment-page-1/#comment-1039 Lisabeth Evers Mon, 19 Dec 2011 02:55:00 +0000 http://www.elephantsandanalytics.com.au/blogposts/what-are-our-members-doing/#comment-1039 That is a really good bit of information you have written up there. I really think you have a great site here - Picture Perfect That is a really good bit of information you have written up there. I really think you have a great site here – Picture Perfect

]]> By: Marina http://www.elephantsandanalytics.com.au/blogposts/what-are-our-members-doing/comment-page-1/#comment-659 Marina Fri, 21 Oct 2011 12:02:05 +0000 http://www.elephantsandanalytics.com.au/blogposts/what-are-our-members-doing/#comment-659 Hi Tim, thanks for the post. I was recently trying a similar segmentation on our website and found a different solution, which admittedly works in Discover only (or Data Warehouse). In an eVar we collect the CustomerID, which is set every time somebody logs in. So I have created a segment which contain only visits where the CustomerID is null. This of course can still contain some existing customers, who in that specific visit did not log in, but I expect the pollution to be relatively small. Another solution might be to create a segment which excludes the visits where the log-in event was triggered, if such an event is collected (and we do). I guess it really depends on your website's profile to what degree the "non-customer" segment is polluted with "customer" data. Hi Tim,
thanks for the post. I was recently trying a similar segmentation on our website and found a different solution, which admittedly works in Discover only (or Data Warehouse).
In an eVar we collect the CustomerID, which is set every time somebody logs in. So I have created a segment which contain only visits where the CustomerID is null. This of course can still contain some existing customers, who in that specific visit did not log in, but I expect the pollution to be relatively small.

Another solution might be to create a segment which excludes the visits where the log-in event was triggered, if such an event is collected (and we do).

I guess it really depends on your website’s profile to what degree the “non-customer” segment is polluted with “customer” data.

]]>