🚀 Jitsu v2.8.4

What's New

• 🎯 Redshift destinations: support for IAM role based authentication.
• 🎯 S3 destinations: support for IAM role based authentication.
• 🪲 ingest: Fixed bug introduced in v2.8.1 when messages sent using Site Id instead of Write Key were treated as coming from server
• 💅🏾 Live Events UI: Added search field to find events with specific payload

Other significant changes

• 💅🏾 Live Events UI: Entity selector now is searchable: #1148
• 🎯 Redshift destinations: retry batches after "Serializable isolation violation" errors
• 🎾 @jitsu/js: added support for$doNotSend flag for group and identify calls
• 🎾 @jitsu/js: jitsu no longer throws errors by default. errorPolicy is configurable #1146
• 🎾 @jitsu/js: context parameters may be overridden for identify call: #1149
• ⚙️ Self-hosted: console image now applies database schema updates by default
• ⚙️ Self-hosted: MongoDB got back to being an optional dependency
• 🚀 bugfixes and UI improvements
• 🛡️ dependencies upgrade

🚀 Jitsu v2.8.3

What's New

• ⚙️ Functions: Functions code can now refer to Environment variables provided on Connection level
• 🔄 Sync API: Added API for managing Sync connectors

Other significant changes

• ⚙️ Functions: Added partial support for crypto module
• 🎾 @jitsu/js: url and path properties of page events now can be overridden #1135
• 🎯 Data Warehouses: spaces in field names now properly replaced with the underscore _
• 🎯 ClickHouse: it is now possible to provide ClickHouse connection parameters on Connection level. E.g.: to enable Async Inserts feature for specific connection only
• 🎯 Facebook Conversion API: Improved events payload.
• 🎯 SegmentDestination: fixed an issue where an incorrect writeKey was being sent to the Segment endpoint #1143
• 🚀 bugfixes and UI improvements
• 🛡️ dependencies upgrade

🚀 Jitsu v2.8.2

What's New

• ⚙️ Pixel API: Added support for sending event via image pixel
• 🎯 Data Warehouses: added "Keep Original Names" option to the connection settings to disable automatic conversion of property names to snake_case
• 🎯 Redshift destination: support for syncing JSON data using SUPER type

Other significant changes

• ⚙️ Self-hosted console image: added cron task that periodically deletes old data from events logs table
• ⚙️ Self-hosted console image: logging fix
• 🚀 ...other small fixes

🚀 Jitsu v2.8.1

What's New

• ⚙️ HTTP API: Deprecated /api/s/s2s/{event-type} endpoint
• ⚙️ HTTP API: Ingest mode (server or browser) is chosen based on Write Key type
• 🎯 Braze destination added

Other significant changes

• 🎯 Snowflake destination: atomically replace tables during Full refresh Syncs
• 🎯 Posthog destination: improved events payload
• 🎯 Facebook Conversions destination: fill app_data for destinations with actionSource=app

🚀 Jitsu v2.8.0

What's New

• 🔒 @jitsu/js support for Privacy Settings to comply with with GDPR and other privacy regulations
• 🧭 @jitsu/js support for Safari Intelligent Tracking Prevention solution
• 🔄 Syncs: UI: It is now possible to cancel running task
• 🔄 Syncs: UI: Display intermediate statistics or the progress of ongoing tasks
• 🔄 Syncs: Support for "namespaces" – allow to sync streams to warehouse schema or database other than configured in destination
• 🔄 Syncs: Improved compatibility with various source images. Support for concurrent streams.
• 🎯 Google Analytics 4 destination: fill user_properties from user traits
• 🎯 Posthog destination: support for screen events
• 🎯 Posthog destination: fill geo ip properties

Other significant changes

• 🚀 bulker: improved support of JSON type
• 🚀 HTTP API: support for passing write key as query parameter
• 🔄 Syncs: Preserve the order of table columns as specified in the source catalog
• 🔄 Syncs: Normalize Names option that syncs table and column names in case insensitive fashion
• ⚙️ Self-hosted: syncctl,sidecar services no longer depends on bulker service. Bulker library is nested into sidecar image
• 🚀 ... a lot of bug fixes and UI improvements

🚀 Jitsu v2.7.0

What's New

• 🔄 Attio: New source connector added.
• 🎯 Google Analytics 4 destination: support for Firebase Apps measurements
• 🎯 HubSpot destination: added option to automatically create custom properties for Contacts and Companies based on traits.

Other significant changes

• 🪲 @jitsu/js: fixed not working reset() method
• 🎾 @jitsu/js now can be used in Next.js middleware #1103
• 🪲 Redshift: fixed bug where connectors syncs failed with Redshift destinations
• ⚙️ console: added CLICKHOUSE_CLUSTER env to enable creating of distributed table for Events Log
• 🚀 bulker: performance improvements
• 🚀 ...other small fixes

🚀 Jitsu v2.6.0

What's New

• 🎯 HubSpot destination
• 🚅 Mixpanel batch mode support that improves performance and reduces traffic usage for projects with high events number
• ❄️ Schema Freeze connection option that disable automatic schema management. Read more

Other significant changes

• 🎯 Amplitude destination: added support for Screen events
• 🎯 Intercom, Google Analytics 4, Google Tag manager destinations: improved event payload
• 🔄 Syncs: added option to customize destination table name for every stream
• 🔄 Syncs: respect original source data schema when syncing to data warehouses
• 🪲 Redshift, Postgres destinations: fixed bug when destination table couldn't be updated when database schema was provided in upper case
• 🪲 @jitsu/js #1098 fixed bug: setAnonymousId not working
• 🚀 bulker: general performance improvements for batch uploading
• 🚀 rotor: performance optimization for connection having multiple Functions attached
• 🚀 memory leak fixes for bulker and rotor

🚀 Jitsu v2.5.0

Note

Upgrading from Jitsu 2.4 requires infrastructure changes. Details below.

What's New

• Live Events: Now you can see sync tasks' batch logs right in the Data Warehouse Events tab.
• Rotor: We've tuned the performance for configurations that use multiple functions per connection, making things smoother and faster.

Upgrading from 2.4

We've made a couple of significant changes:

• Live Events: We've moved from Redis to ClickHouse for better scalability and performance.
• Persistent Storage: We're now using MongoDB instead of Redis, which means more robust data handling.

Redis is no longer in the picture.

For Live Events, we didn't set up a migration path because we see it as a nice-to-have, not a must-have.

If Persistent Storage is part of your setup, enable "double reading" by setting up both MONGODB_URL and REDIS_URL. Jitsu will read from both but only write to MongoDB. This way, you won't lose any data during the transition. After a while, when all your data is happily living in MongoDB, you can say goodbye to Redis.

It's best to switch to MongoDB and ClickHouse sooner rather than later. We're planning to drop Redis support after a few more releases, so keep an eye out.

For detailed configuration instructions and further assistance, please se the configuration guide or the reference Compose file.

🚀 Jitsu v2.4.6

This hotfix release includes the following changes:

• 🔄 console: fixed bug with Sign In page not working on some setups
• 🔄 console: Live Events now has the toggle to enable Functions debug logs
• ⚙️ GTM destination fix for GTM tag initialization
• ⚙️ rotor: another fix for graceful shutdown

👉 Full changelog

🚀 Jitsu v2.4.5

This hotfix release includes the following changes:

• 🔄 console: fixed bug in anonymous telemetry system that could cause error and timeout on some UI operations.
• ⚙️ rotor: token authorization can be enabled for rotor endpoints
• ⚙️ rotor: graceful shutdown now must work properly
• 💅🏾 @jitsu/js. Jitsu processing queue now accepts arrays in addition to callbacks
• unified format of AUTH_TOKENS for all components.

👉 Full changelog