Analytics
2.5K members online now
Understand information in your reports and troubleshoot reporting issues such as self-referrals, (not set) data, and inaccurate information
 
Guide Me
star_border
Reply

Segments Not Fully Working

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Has anyone experienced an issue with segments where small amounts of data are included that clearly do not fit the segment?  I am segmenting by event label and it seems to filter out 90%+ of the data, but always leaves behind some stragglers that have nothing to do with the data I want.  I scoured the event labels thinking that maybe it was confusing the numbers (i.e. finding the numbers somewhere in the label and mis reporting), but they are not similar at all and share no details at all in some cases.

 

This is particularly vexing because if I do it manually (i.e. set event label as a primary or secondary dimension and use the search or filter to input the exact same text) it works and eliminates even the small stragglers.  Isn't that exactly what Segments should be doing automatically?  How is it different if I manually type it in?

 

Example (fabricated, but indicative of the problem): 

  

Segment Definition: Event Label: contains "1234567"

 

Will return:

 

Event Label: mode: standalone | title: Lorem Ipsum | programId: 1234567 | cardId: 123 | source: https://loremipsum.com/d/324

Event Label: mode: standalone | title: Lorem Ipsum | programId: 1234567 | cardId: 122 | source: https://loremipsum.com/d/328

Event Label: mode: standalone | title: Lorem Ipsum | programId: 1234567 | cardId: 120 | source: https://loremipsum.com/d/115

Event Label: mode: standalone | title: Lorem Ipsum | programId: 1234567 | cardId: 119 | source: https://loremipsum.com/d/318

Event Label: mode: standalone | title: Lorem Ipsum | programId: 1234567 | cardId: 156 | source: https://loremipsum.com/d/319

Event Label: mode: standalone | title: PLACEHOLDER | programId: 331658 | cardId: 25 | source: https://loremipsum/d/1001

 

95% of my data is limited to the various cards that include 1234567, but a small percent shows what seems to be a totally random number of events.

 

Any thoughts? 

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by topic author Mark A
June 2016

Re: Segments Not Fully Working

Rising Star
# 2
Rising Star
Segmentation works on the session level so during any given session if the data matches all data from that session is included. So in your case one or more sessions contained the 1234567 but also contained the 331658 as well.

View solution in original post

Marked as Best Answer.
Solution
Accepted by topic author Mark A
June 2016

Re: Segments Not Fully Working

Rising Star
# 2
Rising Star
Segmentation works on the session level so during any given session if the data matches all data from that session is included. So in your case one or more sessions contained the 1234567 but also contained the 331658 as well.

Re: Segments Not Fully Working

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
Thanks, that actually explains it quite concisely. Is there a way to easily work around that? I really like the segments because they are simple and a quick way to filter, but manually removing that data is a problem.

Re: Segments Not Fully Working

Rising Star
# 4
Rising Star
You can use filters which will do exactly what you want but you can not save them unless you set them up in the admin section which unless you have at least three views is not recommened (the most important thing with GA is to insure you have at least one view that is nothing but RAW data no filters at all). The good news about segments is that you can save them and use them over and over so you can segment the data and use its filtering to remove the unwanted data. I do 90% of my analysis in excel I export the entire data and then use excel to manipulate and filter it much more powerful, then I can feed it into our BI program and get much greater insights and find the outliers much more easily.