Fallouts can be a bit tricky, as each step is mandatory to move on to the next step. Check to make sure that all of your conditions match. As well, there's 'next hit' and 'eventual' options for between the rows - that is another thing that could cause differences.  It is possible it's related to the...

Props are typically referred to as "traffic variables" because they capture what the customer is currently seeing in whatever step of their journey they are in. eVars are referred to as "conversion variables" because their values can be persisted throughout the visit to different conversion/success ...

I've never seen any segment show up with "Target" in that preview area, only 'workspace', 'reports and analytics', and 'data warehouse.' I would assume this is because Target is technically outside of Analysis Workspace, and it's just showing the compatibility within the analytics tool. Just because...

I think we need a bit more information here. If you're looking for people who saw a product what is the page name doing? Also, in your example, what operator is between the two hit containers? Is it an 'and' or an 'or'?   Generally, if you're only looking for a single product, you just need the prod...

There's a dimension called "hit depth" that counts how deep into the visit a particular hit is. If you make a hit level segment excluding hit depth = 1, that should return all the hits after the first one. One caveat to that is that it counts page views as well as custom link hits. So in the case th...

Description - When an organization has a large amount of report suites, it can sometimes be difficult to find the correct one to work in. In order to make it easier to find report suites (especially if you typically rotate through a few different ones), have the ability to either mark them as a fav...

When you open a dashboard, by default that will always be open if they have the ability to edit the report. If you give them read only access I believe it should open the report with no component menu at all. I think the 'share with anyone's links do the same thing.

That's one of the difficult things with a lot of the functions in calculated metrics. They require the information to exist in each individual row to be able to do calculations.   If you want to get an average across all visitors, take the distinct days metric and put it inside the "mean" function. ...

Hi @VidhyaAk1, The instances metric that is associated with an evar counts the number of times that evar fires. Occurrences counts all hits. So for example, you have this visit Hit 1: evar110 fires Hit 2: evar110 persists Hit 3: evar110 is expired   You would get a value of 1 for the evar110 instanc...

To do this you could use the "count distinct" function in a calculated metric. To build it you just need to put the dimension "day" in there, and it will count the unique dates that appear. When you put this against a visitor ID of some type, the day will only populate if they visited the site on th...