Changelog

Added

Spotify — export Lytics audiences for audio advertising

The new Spotify integration lets you activate Lytics audiences against Spotify's listener base, so the same first-party segments you already use for email and display can drive audio campaigns in Spotify Ad Studio.

Added

Databricks — three new exports for events, system events, and audience changes

The Databricks integration now ships three new export workflows — Export Event Data, Export System Events, and Export Audience Changes — bringing it to parity with the Snowflake and BigQuery destinations. If Databricks is where your team already does analytics, modeling, or BI, you can now keep raw Lytics activity right alongside the rest of your lakehouse data.

Added

Snowflake & Databricks — export Lytics platform metrics type: added

The Snowflake and Databricks integrations now include an Export Metrics workflow that lands raw time-series metric data — segment sizes, stream volumes, job activity, and the rest of the /v2/metric catalog — directly in your warehouse for analysis and reporting. Same controls as the existing BigQuery metric export, now available against two more destinations.

Added

LINE Ads — audience export integration

The new LINE Ads integration pushes Lytics audiences into LINE Ads as Custom Audiences for targeting in your LINE campaigns. Identifiers are normalized and SHA-256 hashed by Lytics before upload; values that are already hashed pass through unchanged.

Added

Google Cloud Storage — export raw activity data to a GCS bucket

The Google Cloud Storage integration now includes an Export Activity Data job that writes raw events from your Lytics streams to a GCS object as CSV. Use it to archive event history, hand data off to downstream tools that read from GCS, or run analysis outside of Lytics.