New features

Standard SQL

Up until now, Journey Analytics's SQL was compatible with Google BigQuery SQL Legacy dialect. Journey Analytics now enables running freehand queries over Journey Analytics using Standard SQL, as part of a strategic plan to migrate Journey Analytics to operate solely in Standard SQL, encompassing all the advantages of the language, including performance enhancements, query optimizations and superior functionality. Writing Standard SQL is now available when creating a CQL report, aggregation table, model, CQL segment or alert. For more information, see Standard SQL documentation.

Partitioning in External Tables

Journey Analytics's events and sessions tables are automatically partitioned by time. From now on, Journey Analytics also enables the partitioning of other external tables in your project by a timestamp or date column. Partitioning makes sure you run only on the selected time range in the table instead of the entire table, improving performance and minimizing query run time. Partitioning is available only when creating aggregation tables or models using Standard SQL dialect, and are only available for querying in Standard SQL dialect

Merge data using Integrations

Integrations fetching external data can now write to a table in "Append and Update strategy", which will update existing rows (according to a unique key) and append new rows to the destination table. This can reduce the number of rows fetched and integrated in each run to only the updated and new rows.

Writing Models to your external destination

Models can now save their results to external destinations as available in aggregation tables: your Google Bucket or BigQuery dataset.

Feature improvements

Simplifying working with several projects in Journey Analytics

We've listened to our customers' requests and enabled filtering all the dashboards and reports shown on the lists filtered by the active project. Since you can add reports from several projects to the same dashboard, some dashboards might be shown in a few projects. When creating filters, make sure you choose the right project and table to filter by in the filter widget.

Chart Visualization — Choose whether or not to auto-fit your chart

We are aware that sometimes, it's the big picture showing big trends that is important in a chart, whereas in other times – it's the little details we want our data consumers to focus on. That's exactly why we have enabled auto-fitting a single chart in the report size – so you can choose how your report will be viewed in a dashboard.

Cohort Auto Captions

The cohort widget now auto-populates the cohort captions that explain to your report consumers what it is they are seeing. You can override the captions manually as you wish.

ETL auto-population by scope ignoring NULL values

​​Sending an explicit Null for a session or user scope property will be ignored and the last non-null value sent will be auto-populated ("smeared") going forward.

Column filters for Table Visualization

Filtering a single value has never been easier. Just click on a single column header and choose the value you want to see.

Lookup values for virtual properties and expressions

Lookup values are the list of values in the filter drop down. These are populated as part of the ETL, so they weren't available for virtual properties and expressions until now. From now on, all properties can have a drop down list of values in filters