Converging Branches in Workflows

We're happy to announce that we've now released the ability to converge branch nodes in a workflow. This has been one of our most popular feature requests relating to Workflows, so we're delighted to unleash this feature to everyone today.

Since releasing Workflows, and with the addition of the 'Branch' node, it has been apparent that converging branches back into a single path would be a logical next step. Where branches let you split customers on to different paths based on their activity or state, converging allows you to bring those customers back onto a common path. This makes for less duplication of message nodes, and allows you to arrange your customer journeys into more logical workflows.

To converge an existing branch node, simply choose the 'Converge' node from the add (+) menu below the last node on either branched path. Converging will connect paths from the closest branch node above it, this makes following the path that your customers will take straight forward.


If you have nested branch nodes, you will need to converge the last branch first, so that the parent branch node above it has only two paths to connect.

Additionally, from now on, when you add a nested branch node midway along an already converged path, the new branch will already be converged, this makes sure there are no unwanted breaks in the path.

Scoped Conditions on Workflows

Today we've released Scoped Conditions on workflows. Using this feature you can filter out or branch on customers with event-based conditions scoped by the same properties as the trigger event.

This has many applications, for example: Sending a follow up about a product if the customer has not purchased the specific product since they viewed it. In this example, without the scope by option, your automated campaign would not be able to tell if the viewed product event and purchased product event were for the same product.

You can find the scope feature in the advanced settings portion of the side panel on any workflow, as shown below:

Screenshot 2019-10-15 10.59.08.png

When you add a scope property on a workflow, every filter and branch node is scoped by the same event property, meaning you don’t need to add the scope to each node individually.

To learn more, read our help doc on scoping a campaign by event property.

Thanks to everyone who voted for this on our feature requests board.

Bulk export for campaign reports

We're delighted to introduce the ability to bulk export campaign stats from the campaigns list. This means you can now select multiple campaigns from the campaign list and select to export a CSV report of their stats. We've also included the ability to export stats from the selected campaigns for a custom date range.

To show the Export Stats button, simply select one or more campaigns and the bulk actions toolbar will appear. We've also moved the 'add tags' action into this toolbar and we'll be adding more bulk actions here in the future.

We've also added a few shortcuts to let you select multiple reports more easily, like Shift-Select, which lets select one campaign, then while holding the SHIFT key select another campaign further down the list to select all campaigns in between. There's also a new 'select all campaigns' option. These shortcuts will also work with our existing filtering, to make it easier to select only the campaigns you need to export.


Negative variation stats in reports

If you have a negative variation set on a campaign with an A/B Test, we now show conversion stats alongside the other variations when viewing the breakdown in the reports section.


Add a new event from the Trigger node in Workflows

Sometimes you want to create a workflow before the event that will trigger it has been tracked yet. To help with this scenario, we have made it easier (and more apparent) to create a placeholder event from the trigger node of a workflow.


Added support for IP pooling on Sendgrid providers

We've added support for Sendgrid's IP pooling functionality. Simply add an IP Pool name to your Sendgrid provider details on the email provider settings page in your Vero project.

Show customer ID on logs

Depending on how your account is set up and how you track customers, you might not always have an email address assigned to a customer. To accommodate this, on the Logs page when a customer does not have an email address, we now show the customer ID instead.

Updated conversion type labels

We've updated the names of each type of conversion mentioned in the UI and inside exported reports to be consistent with how we've described them in our help docs. Open/Click/Indirect conversions are now labelled Viewed/Direct/Indirect respectively. Read our help doc on conversion tracking for more details.

Editor toolbar bug fix & more

Here's a quick list of bugs that we've fixed over the last few weeks:

Dragging nodes into the last position of a workflow

Fixed a bug that prevented you from dropping a node into the last node position of a workflow.

Exit delay bug

Fixed a bug where the 'Here now' stat on a workflow was not accurate for the last node of a workflow in some cases.

Attachments size limit

Fixed a bug where attachments added to an email would be rejected if it was above 7MB but below 10MB. This has been fixed so all attachments below 10MB are accepted.

Editable toolbar fix

Fixed a bug where the editable toolbar would disappear after scrolling the page making it difficult to edit your content.

Better Logs on Customer Profiles

A few weeks ago we released an overhaul of the Logs feature. We have now made the same changes to the Customer Profiles page, ensuring consistency.

This release also improves upon the prior logs on the Customer Profiles page, adding visibility over event properties and sub-properties, and providing clearer information regarding email interactions.