Agreed, on my 13inch macbook pro I don't even see the top of the buttons on the bottom.  First few times it made me think there was a bug.

You can put the percent difference calculated metric within the greater than field.

It won't be perfect, but you could try unique visitors / ceiling(approximate count distinct(days))

Would you be able to share a specific example of what you are trying to achieve?  If this is visitor based you could use a sequential segment, marketing channel = channel1 or marketing channel = channel2 THEN success metric exists.

One option is to wrap the metric in both if and greater than functions, so that if percentage is greater than 30, return the percentage, else return zero.  You can then set the column settings to not show a value for 0.  This won't eliminate the other rows, but make it clearer to users about which m...

Have you tried building the segment on '::unspecified::'?  The api value thats used includes some extra characters that are not visible within analysis workspace.

How are those custom attributed ingested into Adobe today? Via the 'customer attributes' functionality or within eVars, props, and events?

Adobe does not make that report suite available for sandbox use.

I'd actually recommend keeping your existing rule as is, but within the custom code add a snippet to print the data element values to console. Then you will be able to see in your browser what the values are at when your rule is executed. If they are empty or incorrect then you'd know its likely a t...

It would be helpful if you explained the use case and or outcome.