HiI think there is nothing you can do to hide those items from the VRS, as long as you use "unique visitors" or "visits" as metrics.what happens: basically you are looking at "unique visitors" who has seen a bunch of pages. even if you apply the segment at hit-level, the user has still seen them and...

if you talk to devs, let them implement a "language change" directly

what happens if you add those metrics to the original report suite? do you see pages and numbers for new sites?maybe compare by applying the segment from the VRS to the table (or a copy of the table to have both side by side)I assume that it has to do with the other metrics Ou use (especially unique...

I never have done this so I'm just assuming some points based on experience. maybe Gigazelle​ can add some points if I miss them...first: don't do it I know, sound strange. but based on my experience with both tools, neither naming nor counting metrics ever match up. even if its the same idea, the l...

here are some information gor your testing...segment 1 - referrer"hit segment" wherehit depth = 1orreferrer URL instances > 0ortracking code instances > 0remarks to this segment:- you need to capture the "referrer URL" somewhere, either in DTM or by processing rule- make sure you only have tracking ...

there are at least 2 options to identify re-entries:first, user comes from outside with no referrer or another domain, ideally with a tracking code. this might give you some indication.or you could try to setup marketing channels which might detect all the cases and the you just need to watch out fo...

what is your breakdown? what are you looking at as dimension rows? are there the URL's?

in the "Report Suite Manager" there is a "donwload" option, just select the desired report suite and hit "download". But I haven't seen the processing rules there when I just had a quick view... maybe you can find it somewhere.if not, do you have access to the API analytics-1.4-apis/README.md at mas...

if it is important, could you ise the "getpreviouspagename" plugin and change it to capture the language?

Copy "contextData" to eVar/prop: Copy a Context Data Variable to an eVar