Oh yes, that is something that is really important to note. When you use data warehouse and/or data feeds, it doesn't low traffic bucket any of the variables, you see all the values in the dimension, unlike in workspace. Glad that you figured it out!

In this screenshot you've got a visit segment nested in a hit segment. So your data is going to return any hit with page categories exists that is tied to a visit where they did the path specified. In the hit section, you want to specify the page that you want to see the previous page for, which wou...

The main difference between visit_start_time_gmt and first_hit_time_gmt is that the first one is at a visit level and the second is at a visitor level. We've noticed that user ID's (post_visid_high and post_visid_low) can get resused over time (often it happens at least a year apart). This means tha...

Data feeds are an interesting beast. The thing to keep in mind with them is that every hit comes in on a separate row. So if you're trying to get "x THEN y", you're going to need to look across multiple rows.  First, determine if you want both conditions to exist within the same visit or visitor. Fo...

With the select, it doesn't have the intelligent alerts, which is what uses the % thresholds. Also, with Select you won't be able to use hourly alerts, daily is your only option.  (There's also a few other differences between the two packages with stuff for segments, report builder, etc.)

Neither of the screenshots you shared are of sequential segments. A sequential segment will use the "then" operator between conditions, not the "and" or "or." Also, sequential segments need to be at a visit or visitor level. This means that if you have a segment where someone sees the "contact us" p...

Single page visit is what we use for our bounce rate metric. It takes into account the fact that there could be more than one server call on the same page. But it's still just a single page, which we consider to be a bounce.    You could try making a segment that counts the number of hits that aren'...

So there’s a few things with your segment here. First, as was already mentioned, it does need to be at a visitor level, not visit. The level that you put your segment at determines where it’s going to look for the conditions and what it’s going to return. A visit container means that everything that...

The reason is because for your metric 'revenue', you have the attribution set to 'linear'. The definition from Adobe's documentation about linear allocation is: Gives equal credit to every touch point seen leading up to a conversion.   This means that the credit for the success (in this case, revenu...

Hi @ShiwaniSh, it's possible that the complexity of your segments is too much for workspace to handle. Try saving your dashboard, close it and reopen it. Does it still give you the same error?  Try replicating the issue with a different set of segments, try simpler segments. If it still happens, the...