Is UEM Visit Tag limited to 50k unique values like BTs?
Customer wants to built BTs split by username, however there are more than 50k usernames in their userbase. Username measure has been specified as the Tag Visit for UEM, however we do not see many username strings which we know exist in the system.
I also created a BT to split by Username, then realized the quantity of unique usernames in the system. This BT has been automatically shutoff from storing splits in the PW due to the number of unique splits.
Has disabling this BT possibly caused a change in the behavior of how the Visits are tagged with the TagVisit field and thus my Visits won't have the username speciifed in the TagVisit field?
Hi Joe,
The visit tag is not limited to the 50K - it is not treated as splitting. So if there are a lot of unique user names it is the preferred way to use the visit tag. Of course, not all of the use cases can be solved with just tagging the visit, but on the other hand a splitting with more than 100's of values is also not usable any more for charting etc. (because of our missing TOP-X).
So the main questions is, why are the visit tag not always being set? - One reason could be that, users are not allowing cookies or that a user uses one browser to login with different usernames.
Alex
Could it be that the login page is treated as a different applicaton? A visit can not being spawn across different applications, so if the login page is accessed with different url's or domains it could happen that this page is not a uem action (or a different app).
It could also be that the login page is not always correlated to uem actions - but if the splitting BT is a visit based BT then this can't be the reason.
What you can do is, turn on the splitting bt (server side BT I guess), but don't store the splitting in the warehouse. Then try to drill down from this to visits. If you find some splitting without visit - we have to investigate - create a support case for the dev team.
Alex
