You’ll now find a handy little widget in your Vero account which will notify you when we release an update to Vero. It gives you access to a quick view of all our latest updates, including new features and small changes. It also includes a link to give you the full details of each release.
Log in to your account and check out the latest changes. You can also read about Vero’s new and upcoming features on our blog.
To kick off 2018, we’ve revamped the Reports section in Vero! It’s now sporting a smoother UI and additional filters that will enable you to access your campaign data with greater granularity. We’ve also improved the robustness of our webhooks to help you join up your data from Vero with the rest of your data, giving you access to the insights that are important to your specific business.
Previously you could view your campaign results for 7, 30 and 90 day windows – with this latest update you can select your own beginning and end dates. The results will include:
You can now drill down from the campaign level of Reports and see individual results for email variations and even languages. You can also filter this view by selecting a custom date range.
Many of you requested an overview report of your sends across all of your campaigns, both so you can track total send volume over time and fluctuations in engagement. With this release you can do just that!
The UI for Reports has now been brought into line with the rest of our UI, built on top of a modern Javascript framework. You should find navigating reports and moving back-and-forth from other components in our application a lot faster now.
Full details of the new reporting features are available in our support documentation.
To help each of our customers access the insights that are important to their specific business, we’ve also focused on improving the robustness of our webhook pipeline. Many of our customers now set up their data flow like so:
Vero’s integrations with Stitch Data and Segment allow you to extract, transform and load (ETL) all of the data that Vero generates from your campaigns to Redshift, Google Big Query and other data stores with “one-click”.
As per our webhook documentation, Vero will send a webhook for all of the data that originates from a Vero campaign:
Joining up your email campaign data with other data (such as internal application usage and payment information) in your data warehouse will provide you with a more complete and accurate data set.
Using a BI tool, like Mode Analytics, you can query your data and build custom reports that are important to your specific business. Imagine querying whether customers with higher negative churn two years into their usage of your product read your newsletters weekly. This sort of specificity requires joining data stores. With the strength of data stores like Redshift, Big Query and Snowflake, we are committed to ensuring you can build these queries by giving you your data as quickly and with as much granularity as possible.
Vero’s internal reporting feature is designed to help you:
Our webhooks enables you to join your data in Vero with other data, such as payment information, to get an even more specific picture of the results your campaigns drive.
We will continue to work on integrations and documentation to support these use cases as the technology in this space continues to improve.
If you have any questions about reports or how to use Vero’s webhooks with your own data pipeline, drop us an email at support@getvero.com. We’d also welcome your feedback and ideas.
Coming up to the end of our first quarter in 2017 we have a couple of really great product announcements to make.
Today we’re happy to announce that our new event manager is available to all customers. This whole new section in Vero gives you the ability to view and analyse your schema of incoming events. See which events trigger your campaigns, create placeholder events and even fire test events to help you debug and test out your email workflows. This feature represents our commitment to ensuring your data is transparent and easily accessible in Vero. We have even more to come. While this is still a beta release, we have made it available to everyone and think it is ready for the prime time.
Check out the events manager and let us know what you think by completing our feedback form or getting in touch with support.
Searching for a customer is now faster and more accurate throughout the app. You no longer need to search for the full ID or email address to receive results, partial searches now also work.
Email content and subject lines now support Right-to-Left written content (for languages such as Arabic). These changes are reflected not only in the emails being sent out but also in the previews so you can see exactly what the content will look like. Note: we cannot guarantee that the recipient’s email client will support RTL content but have done our best to send it in the correct format.
The main thing we’ve been working on this sprint is finalising a new reporting UI. This UI is designed to give you increased flexibility. For example, it is possible to run non-standard reports based on specific calendar dates.
The new reports also provide an overview of your entire account’s performance before letting you dive into specific campaigns, variations and language versions. You can select each of these variables as you wish.
We’re currently testing the new reports internally before rolling them out to a select group of customers. We hope that these reports will enter public beta in the next month. Our intention is to let you opt in or out of the new reports whilst in beta.
We’re excited by this release.
To reduce the risk of losing track of active campaigns, we have made an update to how campaign archiving. It is no longer possible to archive a campaign if it is “Live” or”Scheduled”. If you try to do so, you will be asked to pause or unschedule the campaign first.
This one is predominantly for new customers. When logging into Vero for the first time, new customers can now connect Vero to their Segment.com account in a single click. This makes it even easier for Segment customers to start using Vero.
vero-editable tags.Over the Holidays we’ve been hard at work finalising a few new releases and improvements to set 2017 off with a bang. Here’s to a great year ahead.
Throughout December we’ve been testing and tweaking a completely new flow for creating email campaigns. Thanks to all the customers that were involved in our beta of this feature.
Every Vero customer now has access to the updated campaign builder workflow. We’ve redesigned the process for creating a campaign from the ground up, whether it’s a Newsletter, Behavioral or Transactional email. At first glance this looks like a superficial change, but there has been a lot of work behind the scenes and this is truly the first step in a process of iteration toward supporting more complex campaign types, more campaign outputs (beyond email) and helping your Engineering, Product and Marketing teams collaborate effectively when designing and deploying email campaigns.
Our aim was to increase the speed of the entire campaign creation process, reduce errors at launch time and make it easier to understand who will get an email. We hope this halves the time it takes you to create campaigns and ensures you never have any issues.
We would love to hear your feedback on this new workflow so if you have any questions, thoughts or ideas please do get in touch.
In our last update we mentioned we’d updated the customer profiles page and that this would be live for everyone shortly. We’re pleased to announce that this is now the case!
The new customer profiles are faster, with less steps to navigate, and provide a clearer view of your customers’ data and their actions.
For those of you who have early access to the new campaign builder, we have made a number of improvements based on your feedback and ideas. One of those is the ability to see how many A/B test variations are attached to a given campaign without specifically visiting to the A/B testing page. This will help you ensure you have added and verified the contents of each active Variation.
To save confusion with customer ‘tags’ (seen in the customer profiles and added via the API) we have renamed campaign tags to ‘labels’ which more accurately reflects what you use them for – to help categorise your campaigns.
Throughout 2016 we migrated several data stores and made adjustments to our data schema to ensure Vero is more scalable and fault tolerant. Segment calculation has improved markedly over the last several months (we track it internally). In the last two weeks we migrated the first of two final migrations to ensure we can meet our growth demands this year. This paves the way for a faster Vero – we’re excited for the impact this should have on our UI and your day-to-day experience, as well as the stability of our backend.
As we begin to close out 2016 we are still hard at work improving the core experience of Vero. Here’s what we’ve been working on over the last couple of weeks.
We think the best experiences are built by people who have the ability to empathize with their users. Because of this, we’ve redesigned how we represent people in Vero. People will now feel more like, well, people. We’ve also unified multiple pages into a single view which should make understanding your users and their behaviour a more enjoyable experience. You can expect to see these changes in the next week or two as we begin moving accounts over.
Based on requests over the last two weeks, we have now enabled the new campaign flow for the first batch of Vero customers. We’re excited to hear your feedback and hope that this new update saves you a lot of time building and editing workflows, as well as troubleshooting configurations. Over the next two weeks we will enable this for more and more customers as we work to ensure a smooth transition for all – we hope to have this done by Christmas.
You can now create vero-editable HTML elements that are hidden but still editable via our content editor. Useful for things like hiding preview text in email clients.
We have now fully rolled out the current migrations enabling faster calculation times on segments across all customers. This should make calculating segments faster and easier than ever.
One of our internal goals at Vero is to be more transparent with what we spend our time on, and what we plan to spend our time on.
We realise that we haven’t done a great job of sharing our vision this year, so we are taking steps to be more open about our thoughts and efforts. From today we will be writing up release notes (like the below) approximately every two weeks, and publishing more detailed posts explaining major releases.
In each release we will also outline some of our plans for the upcoming weeks and months, which should give you more insight into what improvements you can expect in the future.
Earlier this year we began the process of redesigning our entire campaign creation process, from audience selection to content creation. The content editor we released over the last few months was the first component of this process, and this release is the second piece of the puzzle. This release achieves three key goals:
If you are interested in joining the beta, email us. Note, you can leave the beta at any time and return to the traditional flow.
We’ve finalised some engineering improvements to our segmentation backend. Segments using events or event data will now calculate in around 10% of the time they used to, or less. This has now been released to 80% of our customers, and we’re rolling the rest out in the next two weeks.
This not only affects the segments themselves, but Newsletters using those segments. One of our goals for this quarter is to optimise this further. If you’d like to hear more about the technical implementation, feel free to email us – one of our engineers will gladly blow your mind :boom:. We hope to share more about our approach in the future via our blog.
We now auto generate plain text on HTML emails by default. You can preview customize the plain text being generated by by switching to the “Plain text” tab in the content editor.
