Users created based only on identification events who never turn into customers with identified email addresses to be removed from the data base after a certain timeframe to keep data clean.

As long as Vero can be used for transactionnal emails and not only marketing ones, we need to identify user who are not subscribed to our marketing emails. Actually we have to "identify" them and then "unsubscribe" over the API with 2 separate calls. It could be a good improvement in network to be able to do this in a single API call with some specific parameter in identify endpoint.

Add the ability to import events with properties, not just events themselves (which is already supported).

Please, see screenshot.

Add a node that lets me craft and send events to Segment.

With "Shopify tags, customers and events". If I could code better I'd make the plugin myself. You will practically print money, competition : https://www.omnisend.com/

Allow some key:value pairs to be stored at the Project level, available to all templates within. My initial use-case is having Fusion url (including credentials) in one place, but usable throughout a Project {% fetch_json user ={{globals.user_endpoint_url}}?id={{user.user_id}} %} would make managing that kind of thing a little safer and a lot easier.