The open previous versions is a good tip, but it will only work with saved versions. If you're still building a dashboard and have made multiple changes since saving, going back to a previous version would be the last saved version.

I just read and replied to your other question. This one is similar, but I think this is more focused on the events.  If each evar/prop only fires with certain events, even adding them to a segment isn't going to change that. But what you can do instead, is create a calculated metric. If you know th...

When you have multiple conditions that you want to include, it's important to check if you're using visit or hit level for your containers. In the case of using or statements, you could use multiple containers to keep it separate (might make it easier to read), or you could put everything in a singl...

I've done the same thing before with accidentally deleting a visualization or an entire panel. CTRL + Z is an absolute life saver. The idea about putting a warning - you should post that in the ideas section. That's the part where people can upvote each others ideas and hopefully the product team wi...

Have you checked to make sure that the device type identifiers are being used correctly in the data feeds? If it was just off by 2%, I would say there probably isn't anything systemic there. But since one device is up by the amount the other device is down. I would double check how you're grouping t...

There's a few things that you need to keep in mind when using data feeds/clickstream.   The first is that the data has to be added to your data lake, there could be problems with the ingestion (for example, if you have an evar capturing a search term and it has special characters in it, it could imp...

Yes, as long as each of the "visit to page A" are in their own visit container.   Visitor      Visit           PAGE = A      THEN      Visit           PAGE = A   You can also play around with the "after" condition - if you want there to be a certain amount of time or visits between each event.  Also...

There is some truth to what your friend said, but also some misconception. One of the key selling points of Adobe Analytics is that it is a self-serve data platform that anyone (who has access to the data) can use to build tables and visualizations. It's very easy to start using it. So yes, technica...

It's hard to know what's going on without knowing how you built out your segment. What metric did you put in your table with the segment? It's very possible that the logic of the segment is working differently than how the cohort table works, but it's hard to know for sure. You don't need to share a...

One of the key things with segments is understanding the different between "does not exist" and "excludes". If you set up a condition in a visit segment with "does not exist", it's going to look in that entire visit for a value that is something other than the one you want to exclude. For example, i...