Versions and compatibility

Compatibility

In short, almost everything is compatible with almost everything. We rarely change the core protocols that various components use to communicate.

You might encounter specific restrictions when following the documentation, for example, some of our data models might call for a reasonably recent version of the warehouse loader.

tip

When in doubt, feel free to start a thread on Discourse.

Upgrades and deprecation

Snowplow BDP

If you are using Snowplow BDP (Enterprise or Cloud), you don’t need to deal with upgrading your pipeline, as we perform upgrades for you.

Some major upgrades might have breaking changes. In this case, we provide upgrade guides, such as the ones for RDB Loader.

From time to time, we develop better applications for certain tasks and deprecate the old ones. Deprecations are announced on Discourse.

We still keep the documentation for legacy applications for reference, along with guidance on what they have been replaced with.

---

Latest versions

Core pipeline

Snowplow BDP

If you are using Snowplow BDP (Enterprise or Cloud), you don’t need to install any of the core pipeline components yourself. We deploy your pipeline and keep it up to date.

AWS

Component	Latest version
Stream Collector	2.9.2
Enrich	3.8.2
RDB Loader (Redshift, Snowflake, Databricks)	5.7.3
S3 Loader	2.2.7
Snowbridge	2.1.0
Elasticsearch Loader	2.0.9
Postgres Loader	0.3.3
Dataflow Runner	0.7.3

GCP

Component	Latest version
Stream Collector	2.9.2
Enrich	3.8.2
RDB Loader (Snowflake, Databricks)	5.7.3
BigQuery Loader	1.6.4
GCS Loader	0.5.4
Snowbridge	2.1.0
Postgres Loader	0.3.3

Azure 🧪

Component	Latest version
Stream Collector	2.9.2
Enrich	3.8.2
RDB Loader (Snowflake)	5.7.3

Iglu (schema registry)

Snowplow BDP

If you are using Snowplow BDP (Enterprise or Cloud), you don’t need to install Iglu Server yourself. It’s also unlikely that you need to use any of the other components in this section. You can manage your data structures in the UI or via the API.

Component	Latest version
Iglu Server	0.10.0
igluctl utility	0.11.3
Iglu Scala client	2.2.1
Iglu Ruby client	0.2.0
Iglu Objective-C client	0.1.1

Trackers

Tracker	Latest version
JavaScript (Web and Node.js)	3.14.0
iOS	5.4.2
Android	5.4.4
React Native	1.4.0
Flutter	0.4.0
WebView	0.2.0
Roku	0.2.0
Google AMP	1.1.0
Pixel	0.3.0
Golang	3.0.0
.NET	1.2.1
Java	1.0.0
Python	1.0.1
Scala	2.0.0
Ruby	0.8.0
Rust	0.2.0
PHP	0.7.0
C++	2.0.0
Unity	0.8.0
Lua	0.2.0

Data Models

dbt

Modeling data with dbt is our recommended approach.

Snowplow Web

snowplow-web version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.16.0	>=1.5.0 to <2.0.0	✅	✅	✅	✅	✅^
0.15.2	>=1.4.0 to <2.0.0	✅	✅	✅	✅	✅^
0.13.3*	>=1.3.0 to <2.0.0	✅	✅	✅	✅	✅
0.11.0	>=1.0.0 to <1.3.0	✅	✅	✅	✅	✅
0.5.1	>=0.20.0 to <1.0.0	✅	❌	✅	✅	✅
0.4.1	>=0.18.0 to <0.20.0	✅	❌	✅	✅	❌

^ Since version 0.15.0 of snowplow_web at least version 15.0 of Postgres is required, otherwise you will need to overwrite the default_channel_group macro to not use the regexp_like function.

* From version v0.13.0 onwards we use the load_tstamp field so you must be using RDB Loader v4.0.0 and above, or BigQuery Loader v1.0.0 and above. If you do not have this field because you are not using these versions, or you are using the Postgres loader, you will need to set snowplow__enable_load_tstamp to false in your dbt_project.yml and will not be able to use the consent models.

Snowplow Mobile

snowplow-mobile version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.7.2	>=1.3.0 to <2.0.0	✅	✅	✅	✅	✅
0.6.3	>=1.3.0 to <2.0.0	✅	✅	✅	✅	✅
0.5.5	>=1.0.0 to <1.3.0	✅	✅	✅	✅	✅
0.2.0	>=0.20.0 to <1.0.0	✅	❌	✅	✅	✅

Snowplow Media Player

snowplow-media-player version	snowplow-web version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.5.3	>=0.14.0 to <0.16.0	>=1.4.0 to <2.0.0	✅	✅	✅	✅	✅
0.4.2	>=0.13.0 to <0.14.0	>=1.3.0 to <2.0.0	✅	✅	✅	✅	✅
0.4.1	>=0.12.0 to <0.13.0	>=1.3.0 to <2.0.0	✅	✅	✅	✅	✅
0.3.4	>=0.9.0 to <0.12.0	>=1.0.0 to <1.3.0	✅	✅	✅	✅	✅
0.1.0	>=0.6.0 to <0.7.0	>=0.20.0 to <1.1.0	❌	❌	✅	❌	✅

Snowplow Normalize

snowplow-normalize version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.3.2	>=1.4.0 to <2.0.0	✅	✅	❌	✅	❌
0.2.3	>=1.3.0 to <2.0.0	✅	✅	❌	✅	❌
0.1.0	>=1.0.0 to <2.0.0	✅	✅	❌	✅	❌

Snowplow E-commerce

snowplow-ecommerce version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.5.3	>=1.4.0 to <2.0.0	✅	✅	✅	✅	⚠️
0.3.0	>=1.3.0 to <2.0.0	✅	✅	❌	✅	❌
0.2.1	>=1.0.0 to <2.0.0	✅	✅	❌	✅	❌

Postgres is technically supported in the models within the package, however one of the contexts’ names is too long to be loaded via the Postgres Loader.

Snowplow Fractribution

snowplow-fractribution version	dbt versions	BigQuery	Databricks	Redshift	Snowflake	Postgres
0.3.5	>=1.4.0 to <2.0.0	✅	✅	✅	✅	❌
0.3.0	>=1.4.0 to <2.0.0	✅	✅	❌	✅	❌
0.2.0	>=1.3.0 to <2.0.0	✅	✅	❌	✅	❌
0.1.0	>=1.0.0 to <2.0.0	❌	❌	❌	✅	❌

See also the dbt version compatibility checker.

SQL Runner

note

We recommend using the dbt models above, as they are more actively developed.

The latest version of SQL Runner itself is 0.10.1.

Model	Redshift	BigQuery	Snowflake
Web	1.3.1	1.0.4	1.0.2
Mobile	1.1.0	1.1.0	1.1.0

Testing and debugging

Snowplow BDP

If you are using Snowplow BDP (Enterprise or Cloud), you don’t need to install Snowplow Mini yourself. We (optionally) deploy it and keep it up to date for you.

Application	Latest version
Snowplow Micro	2.0.0
Snowplow Mini	0.17.0

Analytics SDKs

SDK	Latest version
Scala	3.0.0
Javascript	0.3.1
Python	0.2.3
.NET	0.2.1
Go	0.3.0