Hello everyone,
Choosing which container to user whether visit or hit while creating segments is always confusing - can anyone help me understand the below case?
Support I have a tracking code = abc,
I want to know how many people have come to my site via tracking code "abc" and how many people have actually ordered.
I made two segments for comparison
Rule is the same: tracking code = abc but the container is different -- one with a "hit"container, another is "visit" container.
As you can see, only order metric gives me the different result while visits, and UVs are the same.
When I filter the tracking code "abc" from the tracking code report and apply the same metrics, the number of orders are the same as the result of the "hit" bucket segement.
Can anyone help me understand why the number of orders differ when applying hit bucket and visit bucket? What does it mean?
Which one should I use? visit container or hit container?
Thank you so much in advance!!
Solved! Go to Solution.
I would advise you to read through this first : About Segments and Containers
Now here is how I understand it:
I often use the box explanation with my colleagues for segmentation.
Each box cannot see what is the box above!
Now imagine that we create a segment with container visit, in simple terms this what happens when a segment is applied:
So lets say my rule is page equals Home, then for each visit box it will open it and check that at some point during the visit page was equal to Home, if it is it will take the WHOLE content of the box for reporting. This means that if you do a page report with this segment, you will see ALL page values that were contained in the boxes that at some point had page equals HOME
Now imagine that we create a segment with container HIT, in simple terms this what happens when a segment is applied:
Only the data in this hit will be used so if you run a page report and we consider that our rule was page equals Home, then only like item Home should be present.
I would advise you to read through this first : About Segments and Containers
Now here is how I understand it:
I often use the box explanation with my colleagues for segmentation.
Each box cannot see what is the box above!
Now imagine that we create a segment with container visit, in simple terms this what happens when a segment is applied:
So lets say my rule is page equals Home, then for each visit box it will open it and check that at some point during the visit page was equal to Home, if it is it will take the WHOLE content of the box for reporting. This means that if you do a page report with this segment, you will see ALL page values that were contained in the boxes that at some point had page equals HOME
Now imagine that we create a segment with container HIT, in simple terms this what happens when a segment is applied:
Only the data in this hit will be used so if you run a page report and we consider that our rule was page equals Home, then only like item Home should be present.
Thank you so much for your comment, but in my case above,
I captured all the people who have come to site via the tracking code -- and among them I wanted to see how many people actually "ordered"
As far as I understood (maybe I'm wrong) the tracking code value should last till the visit ends, which makes sense because
the number of visit and visitors are the same when comparing the tracking code segment with container HIT and VISIT (Capture below)
I still don't understand why the number of "order" gives me a different result. Shouldn't they be the same as well? If somebody comes to my site via the tracking code "abc" and orders the product during this visit -- it should be counted for the rule (tracking code = abc) with both HIT and VISIT container?
Thank you so much in advance for your advise.
Without knowing the implementation and configuration of the report suite I would say that the order event might be sent in some instances where there is no tracking code persisting.
I would check the following:
The best solution would be for you to extract data feed data for the specific days and figure out what is going on. Open the Data Feed Interface
In terms of columns:
Once you have the data then you should be able to see where post_event_list contains the id of your event and post_campaign is empty. Once you figured out the hits (each raw is a hit) then you should apply filters to get all the hits of the specific visit, you can do that by looking at the raw columns: post_visid_high and post_visid_low (these 2 should be the unique ID of the visitor) and visit_num.
Views
Replies
Total Likes
Dear Unjib,
It is because if you select 'Visit' container, not only the selected tracking code will be in the list but all the tracking codes within the same visits and it's attributed orders.
I suggest you to breakdown the segments by Tracking Code:
In 'Hit' container you will be seeing only one Tracking Code i.e. abc.
In 'Visit' container you will be seeing few other tracking codes if it is within the visit.
So, for your request, you should use 'Hit' container.
Thank You
Arun
In your specific instance, the difference might be due to tracking code changing values mid-visit. If someone manages to stumble across two tracking codes, then make an order, they would be caught in the visit-based segment while being excluded in the hit-based segment.
Views
Replies
Total Likes
Views
Likes
Replies