Microsoft Conversions API (CAPI) Export
A new export integration enables you to send first-party conversion events directly to Microsoft Advertising via the Conversions API.
A new export integration enables you to send first-party conversion events directly to Microsoft Advertising via the Conversions API.
Several privacy and compliance capabilities have been strengthened. GDPR delete operations now include audit logging for a complete compliance trail, and they also remove data from Lytics' attribute store to ensure complete data erasure. The identity delete status API now includes queue and request timestamps for better tracking. Additionally, Amazon DSP exports now support consent signals (amazonUserData and amazonAdStorage), and GA4 export error messages automatically redact secrets.
The Pinterest Conversions API integration has been upgraded with batched API calls for better performance and reliability, as well as support for additional conversion types beyond the initial set. These improvements mean more efficient Pinterest conversion tracking with broader coverage of your conversion events.
You can now export event-level and purchase data to Braze, going beyond simple audience syncing. This enables more sophisticated trigger-based campaigns within Braze and allows for direct revenue attribution, giving your marketing team more levers for personalized messaging.
The geolocation function now returns zip codes alongside other location data, enabling more granular location-based audience segmentation and targeting.
A new option for quiet time windows lets you drop events entirely instead of queuing them. This gives you more precise control over message suppression behavior -- choose whether suppressed messages should be delivered later or simply discarded.
Three new capabilities give you deeper control over personalization journeys. The Flow States API is a new endpoint that exposes personalization keys, enabling external systems to query what personalization state a user is in. Flow Exit APIs provide programmatic control over when and how users exit flows. And Pathfora now supports targeting on-site experiences based on a user's personalization key. Together, these let you coordinate experiences across channels -- for example, showing a specific web experience to users who reached a certain stage in an email campaign.
You can now configure Quiet Hours within Lytics jobs â giving you control over when outbound event syncs are allowed to run.
Weâve made locationâbased rules easier and more intuitive to set up. You can now find a location on an interactive map and click to automatically generate latitude and longitude values â no manual entry required.
Weâve made a broad set of visual, layout, and content improvements to create a cleaner, more consistent experience throughout the app.