The V2 data model config form now brings back Activated Fields from V1, letting you declare them directly when you build a Cloud Connect audience, and it adapts the Field Mappings section to your permissions so the form is clearer about what you can edit.
Wait & Personalize steps in Flows can now hold users until a specific clock time, not just a relative duration. Instead of "wait 24 hours," you can now say "wait until 9:00 AM" or "wait until Monday at 9:00 AM" — evaluated in the timezone you choose. This makes it easy to align flow actions to business hours or a recurring weekly cadence regardless of when each user enters the step.
The Attentive integration exports your Lytics audiences to Attentive in real time, so you can trigger personalized SMS and email journeys off of Lytics audience membership — and the cross-channel behavior, data science scores, and content affinities behind it.
The new AppsFlyer integration lets you drive AppsFlyer in-app conversion events straight from a Lytics audience, without waiting for the event to fire on a user's device. Send events like af_purchase, af_complete_registration, or a custom name — backed by the cross-channel behavior, data science scores, and content affinities that power your Lytics audiences — and they land in AppsFlyer's reporting to feed attribution, retargeting, and analytics.
Schema Patches are the new way to make schema changes in Lytics. Instead of editing fields and mappings directly into a shared draft, every change now goes through a patch — a named changeset where you can group related changes, review themas a complete diff, and publish them all at once. Once the Patches feature is activated for your account, all schema changes will go through this new publishing flow.
Account admins can now tune profile culling directly, deciding which profiles the nightly cull job drops from the profile store without routing the change through an account manager. Author the cull rule with the same segment builder you use for audiences, see how many profiles currently match before you save, and adjust the anonymous-only retention window on your own schedule — handy for keeping the profile store focused on identifiable people and for trimming the long tail of stale anonymous traffic.
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.
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.
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.
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.
