Sequential Segment And Event Hits

[prachij81038608]

I am trying to understand better on the following

I am looking at Event3 Hits where prop22 = "ABC" and it give me 100 Event

I further enhance that by sequential segment saying "Pageviews Exist" and Prop22 = "XYZ" then within 1 pageview Event 3 exists and Prop22 ="ABC" where I get the 200 Events. 

Could someone elaborate why we see this different when it comes to a sequential segment. 

[PratheepArunRaj]

Dear @prachij81038608 ,

Kindly share the segment details (screenshots of the segments would be especially helpful) along with the report where those segments are applied. That will allow us to provide accurate support.

While we can offer input based on our understanding, it won't be precise without seeing the actual segments and the corresponding report data.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[MandyGeorge · Accepted solution]

When you have a sequential segment it's going to be made at a visit or visitor level. This level is important as it is not just the level where it looks for your conditions, but it is also the amount of information that will be returned. If your segment is a visit level, then it's going to look at each visit for that sequence, if it matches, it will return the entire visit. 

For your first segment, if you can share a screenshot that would be helpful. But from what you've said, my guess is that those other events are firing in the same hit as event3. Even if you limit to a hit condition, it's going to return everything in that hit. 

What is it that you're trying to see? We can try and help you figure out the logic of the segment that you need to build.

[Jennifer_Dungan]

In addition to what @MandyGeorge said, segment scope plays a big part of what is happening...

Let's look at the first segment, I assume it is something like:

And in your sequential segment, I assume something like:

While yes, you are looking for this sequence, you are pulling back ALL hits from all visits that have this sequence... even if you are looking only at "Event3" in your table, you will be seeing all Event3, not just the Event3 that pair with "abc"

Example:

• Page A
  • prop22 = "xyz"
  • Event3 = 1
• Page B
  • prop22 = "abc"
  • Event3 = 1
• Page C
  • prop22 = "abc"
  • Event3 = 1
• Page D
  • prop22 = "hey"
  • Event3 = 1

Because you have the sequence across Pages B to C, ALL these pages will be returned as part of the visit. 

Now, in your sequence, if you want any "abc"/event3 pairings... or if you specifically need only the abc/event3...

You might want to try pairing a HIT level segment, with a visit level container with the sequence:

This should limit the returned data to only "abc" event3, but in the sequence...