Yes, you are correct about that GaMeur1​. There are limitations to it.

You can also use "contains any of" as the condition.This takes space as a delimiter for the different values. So if used, will act as an OR condition between all 100 or 100 IDs inserted.

Hello,So, there is a difference in how hit-depth and visit-depth are calculated, which you need to consider when selecting which to use.HIT depth considers ALL hit typesVISIT depth will increase if:The hit is a page viewThe pagename is not the same as the previous pagenameSuppose you have a followin...

Unfortunately the projects and the user cannot be restored. As for the segments, only if you have the segment ID's, Customer Care can restore them.

Okay, I understood my mistake. You can not do this by filter. You will need to create a segment.

It is Unspecified in Reports, and None in Workspace. Will work with any metric as well.Without segment:With Segment:

It should work:

Try 'exists'. If this doesn't work, can you give more information about the report(variable) you are running and the tool you are using(RnA/Workspace/Report builder)?

You may have to consider that this specific rule may not be the one classifying it. if you have just written the rule, it could also mean that it has still not reflected in the reports.Question: What part are you trying to classify in the above string in utm_campaign?

I believe your segments are HIT level segments. There is an expected difference in the results when the container on the Fallout report is greater than the one used in the segments. Maybe better explanation is required to understand how workspace calculates the values.Customer Journey - Fallout You ...