Here’s a round up of some of the fixes and minor releases we’ve made over the last few weeks. We’re currently running QA over our new Journeys feature in Vero 2.0 and will release this as soon as we’re comfortable it’s ready for production. Stay tuned!

Vero 2.0

• Fixed: Minor Segments UX issues. Fixed several small but noticeable UI and UX issues with the new Segments 2.0 release.

• New: Snowflake key-based authentication. Added key-based authentication for Snowflake connections.

• Improved: ETL speed. Improved performance of initial syncs for ETL transfers from Vero to BigQuery, Snowflake, and other data warehouses.

Both Vero 1.0 and Vero 2.0

• Improved: Webhook speed. Migrated several high-traffic data lookups to a faster, more scalable backend. This reduces latency in overall webhook processing (for webhooks sent from Vero to our customers, Twilio Segment, etc.)

• Fixed: Edge case regarding inaccurate merges. Improved “locking” to ensure reliability of person merges and prevent some (very) rare merge concurrency edge cases.

• Improved: Provider statistics integration. Configuring external sending providers like Sendgrid and Mailgun now runs through new infrastructure, improving reliability during setup and ensuring smoother delivery of message results (sent, delivered, opened, clicked, etc.)

Bonus extra
Our CEO, Chris, released a little tool that enables you to convert Markdown or MDX files to fully-rendered HTML emails.

Check out Chris’ LinkedIn post here.
Check out the code repository here: github.com/getvero/mdx-to-email.

Whilst not part of the core product, this is a powerful, fun internal tool we use have started using ourselves and hope it resonates with others (in which case we’ll build into Vero).