don't think they are all "session refresh" if you think as "reload the browser". could as well be people coming from within the "internal domain" but haven't been tracked (yet) or the tracking was sent to a different report suite.Since the "marketing channels" (and thus the corresponding "session re...

Not all visits have a referrer type, see here: Referrer Type Your segments will show at least all visits from internal URLs, where the URL matched the "internal domains" filter. could be Email as well ...hope that helps

As far as I know there are no test accounts available.All you need is somebody giving you access (maybe to test database). Speaking for myself I would need a lot more information before giving any access.what sort of information do you download? whats the idea of your tool?Maybe you can send me a DM...

I can give you some tips which might help:1) Only "public" segments will appear in the panel list (if it is created by you or shared with you). if you create "local segments" (by dropping a dimension in the top panel head) the segment will never appear in the segment list on the left side. You can e...

What do you mean by "it does not work"? why not?the solution in the first link maps a single dataelement to any desired query string parameter. read here: Get value of URL parameter for data elements I think this is exactly the same as you try with your custom code ... so just change your dataelemen...

Hi paulinamb​To get a single query string parameter in a dataelement, simple change the dataelement to fetch the value directly (no javascript needed). see here: Get value of URL parameter for data elements need an improvement?Some time ago I wrote an answer to get all utm parameters in one dataelem...

Hi JoeBlackwell​I see your problems and I agree that restricting the creation of new workspaces to "beginners" might help. But if you cancel the "create" option it is still possible for end users to create/move tables with the shared project until they get completely wrong numbers. I think you can't...

Hi JoeBlackwell​I made some testing and I think it works quite well. I managed to restrict access to metrics and dimensions as needed. The only thing I couldn't control is that an end user can create new workspace projects. But I don't mind if somebody creates a new one as long as he is not able to ...

You can restrict access to workspace projects as read only by change of permissions (product profiles).Here are two links which are worth having a look:Manage Experience Cloud users and productsProduct Profiles |In case you are still in the old legacy world, just go to user groups and change permiss...

looks like the current release will fix the problem! great news ...