← Back to all sparks
V

Vero

MKT AUTO
Velocity0.0

Marketing automation mid-migration, rebuilding Journeys branching on the 2.0 platform

marketing-automationjourneysplatform-migrationemailreporting
Current state
Vero is running two platforms at once and the changelog reads that way. Vero 2.0 gained True/False and Exit nodes in Journeys — real conditional branching that routes customers on behavior, properties and actions — plus an SMS node, a Cmd+K command palette, Forms, and project-level reporting on the homepage summarizing messages sent, open, click and delivery rates. CC on emails shipped to Vero 1.0 campaigns with 2.0 support described as coming.
Where it's heading
The work is about reaching parity and then passing it. Branching and exit nodes are table stakes for a journey builder, so shipping them in 2.0 marks the point where the new platform becomes usable for real lifecycle programs rather than linear sends. The CC entry shows the migration's awkward middle — a feature landing on the old platform first. Project-level reporting suggests the next concern is proving programs work, not just building them.
Prediction
Expect CC and the remaining 1.0-only capabilities to close out on 2.0, since the entries explicitly flag that gap, and reporting to deepen now that a project-level summary exists.

Recent moves

  1. 3mo ago

    Project-level messaging performance on the 2.0 homepage

    A whole-project snapshot covering messages sent with open, click and delivery rates. Aggregate reporting is what makes a journey platform reviewable rather than only configurable.

    View source ↗
  2. 3mo ago

    Add CC addresses to emails

    CC recipients on emails from Vero 1.0 campaigns, with 2.0 support still pending. A small feature that mostly documents where the migration currently sits.

  3. 3mo ago

    Add CC addresses to emails

    Duplicate record of the CC release published a day apart. Cited once above.

    View source ↗
  4. 4mo ago

    Command palette and Forms in Vero 2.0

    Cmd+K navigation, Forms, keyboard shortcuts and sorting improvements in 2.0. Interface polish on the new platform rather than capability.

    View source ↗
  5. 4mo ago

    True/False and Exit nodes in Journeys

    True/False and Exit nodes bring real conditional branching to 2.0 Journeys, routing on behavior, properties and actions. This is the release that makes 2.0 viable for non-linear lifecycle programs.

  6. 4mo ago

    March digest covering Journeys nodes and SMS

    A digest repeating the True/False, Exit and SMS node releases alongside documentation work. Cited individually below.