Solved! Go to Solution.
Views
Replies
Total Likes
I don't think the segment you created is quite right... the problem is that "does not equal" is very different from "excludes"
Think of a visit flow like this:
You are looking for a hit on SSA followed by a hit on "not SSB", to which SSC, SSD and SSA) all qualify for, since you also didn't specify a time frame / number of hits between SSA and SSB.
Even this flow would meet your segment criteria:
Since SSC is a hit that does not equal SSB and follows SSA in the Visit.
However, creating a segment like this should get you what you want:
VISIT [
Page equals SSA
AND
VISIT level EXCLUDE container [
Page equals SSA
THEN
Page equals SSB
]
]
This should get you all Visits that the user hit SSA, but then excludes the Visits where the user hit SSA then SSB.
Then if you are looking at Visitors who never reach SSB in any visit, you can use the following:
VISITOR [
Page equals SSA
AND
VISITOR level EXCLUDE container [
Page equals SSA
THEN
Page equals SSB
]
]
Basically, I just changed the main segment scope and the container scope to Visitor....
So now it reads as: Get all Visitors that hit SSA, and exclude Visitors that hit SSA then SSB, i.e. exclude visitors that at some point hit SSB after SSA....
However, the problem with this is that is looks at the entire time frame... if you are looking at the last 3 months, and the user completed the flow 2.5 months ago, then started the flow again a few weeks ago and didn't complete it, the Visitor will still be considered a "complete" based on their first completion....
Hi Prince_lathwal,
Hope this is Helpful.
Views
Replies
Total Likes
Hey Srikrishna! Thanks for the answer, that was immensely helpful.
Now, if I want to create a Visitor segment of just the visitors who never reach step B, i.e. exclude people who reach SS B during any visit in a given period. How would one go around that? What changes do I need to do in my segment?
-
Thanks!
Views
Replies
Total Likes
I don't think the segment you created is quite right... the problem is that "does not equal" is very different from "excludes"
Think of a visit flow like this:
You are looking for a hit on SSA followed by a hit on "not SSB", to which SSC, SSD and SSA) all qualify for, since you also didn't specify a time frame / number of hits between SSA and SSB.
Even this flow would meet your segment criteria:
Since SSC is a hit that does not equal SSB and follows SSA in the Visit.
However, creating a segment like this should get you what you want:
VISIT [
Page equals SSA
AND
VISIT level EXCLUDE container [
Page equals SSA
THEN
Page equals SSB
]
]
This should get you all Visits that the user hit SSA, but then excludes the Visits where the user hit SSA then SSB.
Then if you are looking at Visitors who never reach SSB in any visit, you can use the following:
VISITOR [
Page equals SSA
AND
VISITOR level EXCLUDE container [
Page equals SSA
THEN
Page equals SSB
]
]
Basically, I just changed the main segment scope and the container scope to Visitor....
So now it reads as: Get all Visitors that hit SSA, and exclude Visitors that hit SSA then SSB, i.e. exclude visitors that at some point hit SSB after SSA....
However, the problem with this is that is looks at the entire time frame... if you are looking at the last 3 months, and the user completed the flow 2.5 months ago, then started the flow again a few weeks ago and didn't complete it, the Visitor will still be considered a "complete" based on their first completion....
Thanks a lot, Jennifer! The exclude container completely missed my mind. That does seem like a much better way to approach the problem. I think you answered everything that concerned me.
However, the last point you mentioned, if I limit the scope of container to visit level then I'll get all the visits that didn't complete the flow which is something I want to look at - as in what else did they do in that particular visit in which the flow wasn't completed
and
for a visitor level container I'll get all the visitors who did try to start the flow but just never completed it in the given timeframe.
Is my understanding correct?
Again, thanks for your help!
Views
Replies
Total Likes
Yes, since you first started looking at Visits, I provided that.. This is a much easier check, since your scope is limited to the Visit...
But then you asked about completing the step in the next Visit,.. (i.e. Add to Cart in Visit 1, Checkout in Visit 2, or something like that)...
Once you look at Visitor scope things get tricky in this, if the flow is repeatable, then any completion would trigger the exclude.. the risk gets bigger the longer the time frame becomes...
Views
Replies
Total Likes
Yeah, got it! Thanks a lot, have a nice day!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies