Solved

Segments with a visitor container and breakdown by day dimension

Forum|Forum|3 years ago
July 13, 2022
2 replies
4504 views

I created a segment of users who had credit application clicks using a visitor container. I used the month of April as the panel date range. And there're about 4 million users (unique visitor). When I added a day dimension there're about 160K unique visitor each day. What does the 160K mean? Active unique visitor in each day who had made credit application in the month of April? Because if I switch the segment container to visit level, the total is still 4 million users (unique visitor), but the daily visitor is much lower about 80K.

If I want to build a dashboard for the IT team to improve the engagement of credit applications, which segment container is better? I feel like the visit level contain provides better information on the day level. Is that right?

Analytics

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Jennifer_Dungan

Just to add to this fine answer, when you create a segment at visitor level.. this is lifetime of the visitor (did this user ever do this action.... when you pull that into your report, it will limit the data to the "users that ever performed that action" that came to the site during your time frame.

Visit is definitely more focused, cause they need to have performed the action within the time frame...

In many cases, I still prefer to use "hit" level in a lot of my segments... if I pair this with the UV metric, I still get the data I need (UVs who did X) but then if I want to get the count of actions (I don't get all the PVs in the entire visit that need to be filtered out)

leocwlau

Community Advisor and Adobe Champion

When you use 'visitor' as the container, the table will match any visitor who had credit application clicks regardless of when that happened. It means there are 160K visitors on a particular date visiting your site and they had credit application clicks at any point in time.

When using 'visit' as the container, it limits the credit application clicks to the corresponding visit. So the 80K means there are 80K visitors visiting your site and had credit application clicks on that day as well.

Jennifer_Dungan

Accepted solution

Community Advisor and Adobe Champion

Just to add to this fine answer, when you create a segment at visitor level.. this is lifetime of the visitor (did this user ever do this action.... when you pull that into your report, it will limit the data to the "users that ever performed that action" that came to the site during your time frame.

Visit is definitely more focused, cause they need to have performed the action within the time frame...

In many cases, I still prefer to use "hit" level in a lot of my segments... if I pair this with the UV metric, I still get the data I need (UVs who did X) but then if I want to get the count of actions (I don't get all the PVs in the entire visit that need to be filtered out)

Jennifer_Dungan

Community Advisor and Adobe Champion

Hi @Jennifer_Dungan ,

Can you please elaborate the statement " it looks like Adobe has changed the logic.... the Panel Date Range is providing definition... " ? Is it related to "Make date ranges components relative to panel calendar"?

As per my understanding if I have a Visitor level segment checking orders >10, all the visitor's lifetime orders by user will be counted as part of this segment not only the orders done in the reporting period. Has this logic changed now?
If you have an Adobe document handy that has an explanation for this update and you can share it , that would be great.

Thanks,

Rishabh

As per my understanding if I have a Visitor level segment checking orders >10, all the visitor's lifetime orders by user will be counted as part of this segment not only the orders done in the reporting period

That is how it worked until recently!

I discovered a few weeks ago (and am still working with Adobe to understand what happened).. but right now, at this moment.... all Visitor Level segments are bound by the panel date!

So your "orders >10" is now more than 10 orders within the reporting period

😞

Biggsy50

Level 3

@jennifer_dungan Related to this I saw your tip of turning fallout funnels into tables ... and then further breaking them down by time periods at 22:20 in the Rockstar video - https://business.adobe.com/summit/2024/sessions/2024-adobe-analytics-rockstars-top-tips-and-tricks-s104.html.

This works well looking at the aggregated behaviour for the whole month, e.g. July.

Question - However, does using a VISITOR segment to further break down the panel date range, e.g. July, into say weeks unfairly boost the later weeks in July?

Segment = 'VISITOR - All Page Track (v6) equals product detail'

For example you may have a VISITOR going to the site on W/C Monday 1st July, and in that visit they see a Product Page (step 1). So far so good.
They then return to the site W/C 22nd July but ONLY visit the Home page. However, in this case the segment asks “Has that VISITOR seen a Product Page in July?” and this will be true, even though they didn't actually see a product page in W/C 22nd July.
W/C 22nd July will then “incorrectly” record a VISITOR seeing a Product Page & there will then be an inflated % of VISITORS seeing a Product Page in that week.

Instead should any fallout segments that are going to be further split out by day or week be HIT (or VISIT) segments to prevent this?

Thanks,

Steve Biggs

Jennifer_Dungan

Community Advisor and Adobe Champion

Well to be fair.. regular fallouts will have this same issue when you are looking at Visitor scope....

But of course, a normal fallout will be in aggregate, whereas breaking the table down by times could cause the same user to be in "step 1" in day/week/etc 1, and "step 2" in day/week/etc 2, which could cause some "interesting" challenges in the data.

While I might use Visitor segments for an aggregate "table replication", I think it could cause confusion with time breakdowns... and you might be thinking, why would I use a table for aggregate, when Fallout already does that? Well for that, I would consider readability and consistency with other reports... or just having more control over the success rates (since I have more control over the math in the table - like doing a step to step success, rather than a start to step each time....)

But to answer your question in general, I've really only used Visits when using this method (you can't use HIT for sequential)... but since our "purchase flow" is for a subscription and not a full shopping cart experience, that works well for me...

But maybe you can get creative and use Visit segments, but maybe have a Visitor segment inside of that... like maybe you could include visitors that have added content to their cart during the period, but look at the checkout flow within a visit? Get creative! I would love to see what you come up with!

Biggsy50

Level 3

Top stuff! Thank you. I just wanted to make sure I wasn't going down the wrong avenue. If I understand the output better then my clients will understand it better too. I will explore further next week 🙂

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded