DataUnlocker Announcements
13 members
8 photos
5 links
A channel with the latest news and announcements from Contact for any questions.
Download Telegram
to view and join the conversation
Channel photo updated
๐ŸŽ‰ Welcome to DataUnlocker!

After months of engineering, DataUnlocker is finally here. We are happy to announce its beta version, which is being rolled out gradually to our early subscribers.

This Telegram channel is all about DataUnlocker: we will use it to communicate different product updates and possible maintenance windows during the beta period. For any possible critical updates which may impact you we will additionally send an email notification.

Jump straight in:
Read more about DataUnlocker:
Talk to us:
Leave your feedback: or

๐Ÿงจ Oops! Due to misconfigured networking in our cloud provider, DataUnlocker's cluster nodes were unexpectedly disconnected from the Internet, resulting in service downtime. Both DataUnlocker Admin and proxy nodes were inaccessible earlier this night.

Now the service is back up! We apologies for any inconvenience it could cause.
๐Ÿ“œ DataUnlocker's script, the front-end heart of DataUnlocker, is expected to receive updates during the beta period. This, however, doesn't mean you need to update the script every time the new version comes out: if DataUnlocker works for you at the moment, it will continue to work, at the same pace. However, we recommend to always use the latest script.

For instance, in the script version 2.8.0, which was released today, we enhanced the support of "unblocking" <img> and <script> elements. Previously, URLs of blocked images and scripts were just replaced with new "unblocked" URLs. The new DataUnlocker's script is now additionally aware that these elements could have onload and onerror listeners, and they will now be triggered once the data is proxied, just like you would expect. Practically, this means that there will be no duplicated analytics hit requests in some edge cases, as well as no noticeable impact on img or script elements, from the JavaScript code perspective.
๐Ÿ“บ Lately, DataUnlocker received these useful and important updates:

โ€ข We've made a video tutorial about installing DataUnlocker. Watch it on YouTube:
โ€ข Answered additional questions in our FAQ, such as "Does DataUnlocker support X"
โ€ข Updated DataUnlocker's script to version 2.9.2. It includes some important fixes to XMLHttpRequest (along with a better Image patching support) which may have prevented your web application from working as intended.
โ€ข Other minor or invisible updates.
๐Ÿ”” We've added a configurable email notification setting for DataUnlocker properties. Now you can set the prepaid traffic threshold below which an email notification will be sent to your email address. By default, this threshold is 100 MB.

Later, we will bring notifications to other platforms like Telegram. If you prefer to get notifications in any other way, let us know by submitting your feedback at

Also note that you can always set up automatic traffic purchases by adding a card ๐Ÿ’ณ, and thus you will never miss the moment when the prepaid traffic runs out.
๐Ÿ“œ Another DataUnlocker's script update is out! This time, it brings a complete rewrite of XMLHttpRequest patching, which accounts for many of its advanced use cases. For instance, now not only loadend and similar event handlers are thoughtfully handled, but also XHRs with multiple open/send and so on. As always, this update isn't critical, but it might fix some unwanted side effects DataUnlocker's script could introduce.

But why can't DataUnlocker automate its script updates? Due to the nature of the problem DataUnlocker solves, the script (its patching part) must be synchronous. Hence, DataUnlocker is not able to always download the newest script's version. However, still, getting the latest script can be automated: DataUnlocker may soon introduce an API to get the latest script of your property, and you will be able to f.e. integrate this API into your front end build pipeline, which will always bring the latest (f.e. minor/patch) DataUnlocker script's version to it. Let us know if you need it.
๐Ÿ“ฆ DataUnlocker now groups proxied services. You will see a refreshed view of the Proxied Services table on the Dashboard page, which is easier to understand and navigate through. Also, services which have additional configuration options (like custom dimensions in Google Analytics) now appear with an icon and a tooltip.

Pro tip: with numerous improvements made under the hood, we also silently added wildcard proxy configurations. You most likely won't need them, but if you do, here's an example: you are now able to disable proxy for and all its subdomains by adding a configuration for "*". Moreover, the wildcard configuration will appear automatically when a large number of different subdomains is proxied.
๐Ÿš€ DataUnlocker has just got two very important updates!

1๏ธโƒฃ DataUnlocker's latest script version 2.16.2 is now able to bypass all most popular ad blockers, unlike its previous versions. By installing the newest script, you will notice a significant increase in the proxied traffic (more than 50%!).

2๏ธโƒฃ DataUnlocker now offers continuous integration of its script to your web application, which will allow to always keep DataUnlocker's script up to date. Read more about this feature:

What's next? We are listening carefully and improving gradually. Soon, we will be rolling out DataUnlocker Status page, which will test DataUnlocker against the most used content blocking software on a daily basis.
๐Ÿ“ˆ Here is the demonstration of the significant increase in the proxied traffic you will get by installing the newest script version (read: version 2.16.2), which was rolled out just a few days ago. This increase happens from versions 2.14.*, however, only with the latest version it will be fully effective.

Remember that you can always measure DataUnlocker's end-to-end impact by using this feature for Google Analytics: