no, there is currently no official way to figure out which segments are used in workspace projects. I think the main problem is "segments" can be used both "directly in project" or "within a calculated metric". so getting all those information out of a single project seems a bigger challenge ...

your segment is looking for VISITS where the eVar81 matches SOMEWHERE within the visit. that means the user in row 5 had the login/userID set AFTER the eVar81 has been set. sounds possible?the easiest fix would be to change the segment to HIT container where "eVar81 instances = 1" (only get hits whe...

I upvoted an existing idea: Simplify archive (zip) folder structure

thebenrobb​ I strongly support the idea of thomas.amsler​ to have a flat folder structure for zip file contents. and I don't think there is a lot to change, but might be wrong.In fact, I think you just need to skip a bunch of folders and directly include the "ExtensionFolders" directly below the mai...

as far as I know there is no filter option in admin...possible solutions:1) Classificationif you use a custom prop/eVar for the URL you can create a classification with a regex rule to "rewrite" the URL. this leaves the original values unchanged (might be needed somewhere else?) while you have a new...

you can either access the "logs" in the admin section or use the API. every access of a user to a workspace project is recorder into the logs.jen.lasser​ created a great spark page about this topic: adobe.ly/aausageif you don't want to go the full way as described on the spark page (maybe because it...

no, I don't think there is any setting to prevent an overlap. the "pages" are just a split of results list by a defined number of rows, regardless what the breakdown is.what you could do is fetch data day by day to prevent a day overlap per API request...

here are some ideas about possible problems:- there are already rules for those dimensions- you selected too many RS where classification does not match- you don't have the needed permissionmost like one of the first two reasons...

agree with praschetan​: use one RS for all data, create the segments based on operating system to use as filter for VRS. I don't see any good reason to split the traffic in separate RS - you want be able to merge and grt the full view (at least until now...)

I would suggest to contact ClientCare - there seems to be something wrong. the only case where it didn't work for me were google display ads (setup in the same google ads account but they are not search ads!)