Awesome, glad it worked @kayawalton!

@kayawalton you can actually use a breakdown dimension to generate your hyper link.  For example, let's say your dimension is product & your metric is product views.  You could use the breakdown dimension of clean url in building the hyperlinks.  The top clean url will be used to create the link.  (...

Hi @SarahDe10  What method are you using to capture the query string params?  If you're using marketing channel processing rules, you'll want to make sure you're looking for the right key as shown in the screenshot below.    

Hi @MartaSk1  When working with eVars, you'd also need to consider the persistence of the dimension.  If set to most recent | visit, for example, the values would differ than if set to original | visit. Props can have pathing set up, meaning an entry & exit version is kept.   When considering persis...

When you mention canvas, are you referring to the Journey Canvas?  I'd recommend building a Freeform table with the dataset ID (or name if you've build a derived field) and the number of events.  As mentioned, as long as your date range encompasses the full range of events in your dataset, I'd expec...

In CJA, dimensions can be numbers/integers.  However, if the data type is string, then you can't do what you're wanting to do in Workspace.  You can use Report Builder to get the numeric strings into Excel where you can treat them as numbers.

Hi @JacobC1, As @Harveer_SinghGi1 mentioned, one approach might be the bot detection rules.  There are some other attributes you can filter on in addition to IP.  Not sure if any of these would help simplify your solution.  (One note, if you enable bot detection, be sure to add the bot information f...

As Jen mentioned, the Visitor segments pull in everything and it can be hard to filter down to exactly what you're wanting sometimes.  I'm not certain this will give you what you're wanting but might be worth a shot.  Notice I changed "Include Everyone" to "Only After Sequence"  And I added an exclu...

Your logic looks good.  I tested this and it worked as expected.  All events under No value for email domain had no email address. Alternatively, you can try using regex in component substring settings.  Use this expression .+@(.+) and output $1.  That should do the same.  Perhaps that will resolve ...

As mentioned, lookup datasets are likely your best approach.  You can also use derived fields or component substring settings to do some minimal regex transformations.  But there's no 1:1 like the classification rule builder that allowed for many, many rows of regex.