The Snowplow CDN for JavaScript Assets will be deprecated on 1st March 2021. All assets loaded from https://d1fc8wv8zag5ca.cloudfront.net/ will begin redirecting on that date. If you are using assets from the Snowplow CDN, this means your Snowplow tracking may stop working unless you take action. In the future we will fully decommision the Snowplow CDN for JavaScript Assets.
UPDATE
We have moved the deprecation date to the 1st March 2021. On that date we will begin returning 301 redirects to the jsDelivr CDN to ease the transition period. This may still cause tracking to fail depending on your web site configuration - please read the replies below for more information.
Snowplow Insights Customers: This may also impact you so please do read below, however the Snowplow Customer Success team will also be in touch with you next week with more details.
As an alternative we have made all of our assets available on the jsDelivr CDN. You can read more about the impressive jsDelivr network here. More information on how to migrate to jsDelivr is available below.
Beginning on 1st March 2021 we plan to automatically redirect requests for the Snowplow JavaScript Tracker to the jsDelivr CDN. This may impact your tracking depending on your website configuration (e.g. you have a strict Content-Security-Policy (CSP)). If you’re concerned about the impact of a redirect on your implementation we highly recommend making the switch before this date.
Please read below for all alternative options, including using jsDelivr CDN.
1. Hosting sp.js
Whilst we’re offering an alternative CDN, Snowplow does not recommend using third party providers for hosting JavaScript assets that you use on your websites. We encourage all users to host sp.js
on their own servers, and this will always be the recommended best practice.
If you wish to follow our recommended best practices, please follow our guides for hosting sp.js
on AWS or GCP.
In the past, Snowplow users have had access to a Snowplow hosted CDN for JavaScript assets. We announced in September 2019 that we will stop updating this for new JavaScript tracker releases from v2.10.2. We made this change as we wanted Snowplow users to control the location of where their JS assets are being loaded from, this is deemed best practice as it gives you full control over the JavaScript that is executing on your website, removing any potential security risk. However, this has posed a hurdle for many, making trying out Snowplow and testing new versions harder as you needed to find somewhere to host sp.js
.
2. New third-party CDN option
We’ve now made all our Snowplow JavaScript assets available via the jsdelivr.com CDN. Click the link below to explore the available assets:
All versions of sp.js
have been made available on jsdelivr.com and it’s extremely easy to migrate.
How to migrate
If you are currently using: https://d1fc8wv8zag5ca.cloudfront.net/2.10.2/sp.js
you will need to switch to: https://cdn.jsdelivr.net/gh/snowplow/sp-js-assets@2.10.2/sp.js
The latest version (2.16.1) is also available: https://cdn.jsdelivr.net/gh/snowplow/sp-js-assets@2.16.1/sp.js
If you are using the Snowplow GA plugin, please consider hosting sp-ga-plugin yourself, or you can update to: https://cdn.jsdelivr.net/gh/snowplow/sp-js-assets/sp-ga-plugin/0.1.0/sp-ga-plugin.js
Be notified of future changes
Going forwards we would like to continue proactively informing open source users who opt in about relevant changes to Snowplow technology and the way we host it. If you would like to receive these notices please log your email address here.