Josh,Good points overall and I don't have much to disagree with.You're right of course that extensions should be type checking and flexible, though I think the "launch does not cast DE's to strings" answer you got on the slack was only half true. If you look here: https://developer.adobelaunch.com/guides/extensions/views/#supporting-data-elements​ under the heading "Data element token replacement methodology" it looks like the value is left alone (can be an array, even a function) if a single da...

On the surface this sounds great. I was eager myself to do something similar myself and started digging around the Launch source code to see if it was feasible. Unfortunately there are a few concerns:1) Any data element can be passed to the configuration of any extensions. This means that if you allow a data element to contain an array, you don't just need to update the launch core to handle it, but all extension providers would need to take into account that they might be passed arrays and offe...

Hi Stefan,That's definitely a great application for rule conditions/exceptions in Launch. It looks like there are currently three extensions in the launch catalog offering to help manage user consent. One by Evidon, one by One Trust and one by TrustArc.I'd be curious to hear if one of those meets your needs or not.