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...

The best practice is to test and modify as needed. It's very likely that the first set-up for your alerts will need to be modified at least once, especially if you don't have a lot of historical data captured yet. Also, getting the sensitivity right is important. Something might be an anomaly - but ...

The reason it still happens within the hit is because "previous page" is captured at a hit level, not a visit level. So in your hit for a particular page, the prop/evar that captures the previous page will be fired in the same hit. Regardless of if you use a visit or hit level segment, it's going to...

There was another similar question about bounce rate recently.  Solved: Engagement metrics - Bounce rate - Adobe Experience League Community - 701410   Basically, when there is a bounce that means there was one hit on your site, and then the visitor left. In order to calculate a time spent on site t...

When you have a generic metric and you place a dimension on it to filter it, it's going to apply that to every part of the metric. For example, with conversion rate, I have the example here of putting conversion rate against page names (having it on the side will do the same as if you were to put it...

Yes, the segment is using the same logic as the flow.  When data is captured on your site, each hit in the visit is captured sequentially, and it doesn't differentiate between tabs. So if you have two tabs open and are switching between them, both of those are going to get counted into the same visi...