What is the deduped value if user's status changes in 1 visit?

[user70977]

For example, in 1 visit a user is on homepage (evar 1 = not logged in) then logins then goes to a product page (evar 2 = logged in).

I understand if we break down this metric by page url, we'll see that homepage will have 1 not logged in and product page will have 1 value logged in. What is the dedupe value at the top? Will it give attribution to this visitor as logged in or non-logged in?

[Jennifer_Dungan]

Regardless of whether the user is logged in or not, the same ECID should be used for the user... unless you are forcing your own internal User IDs as a unique identifier... then you might have some issues.

So now it really depends on your table... if you are just doing UVs and Page URL, then the user should be de-duplicated (regardless of the login state)

	Unique Visitors
Page URL	1
/home	1
/product	1

Now, if you are using segments as stacked columns, you will see the same user in both columns, on different pages:

	Unique Visitors
	Segment: Logged In	Segment: Logged Out
Page URL	1	1
/home	0	1
/product	1	0

And if you are using Segments as your breakdown, then de-duplication goes out the window... Segments will be added with no de-duplication logic:

	Unique Visitors
Segments	2
Segment: Logged In	1
Segment: Logged Out	1

[Jennifer_Dungan]

I should also mention that my Segments were based on HIT scope... Visit or Visitor scope is a whole different story.

[Vinay_Chauhan]

Hi @user70977 

In your example, the same visitor is moving through two different states (not logged in --> logged in) within a single visit. At the top-level deduplicated view of unique visitors, Adobe will still count this person as one unique visitor, regardless of the login state.

When you break it down by page, you’ll see “not logged in” tied to the homepage and “logged in” tied to the product page, as expected. But if you look at just the overall deduped count, it won’t choose one state over the other, it simply counts the visitor once.

If you want to attribute behavior specifically to logged-in vs not-logged-in states, you’d need to segment based on login status. That’s where the same visitor can appear in both groups, since segmentation doesn’t apply deduplication across states.