Release Notes

On March 14, 2025, Linkly was subject to a denial-of-service attack that resulted in our app being offline for approximately 65 minutes, in two chunks.

The attack was targeted at one of our customers.

During the attack, over 1 billion requests were sent to our servers, in minutes.

This affected a number of our customers, whose links were offline or suffered from degraded performance during this time, and our web app was inaccessible.

We mitigated the attack by applying Cloudflare's WAF at our edge, which was able to block the attack while allowing legitimate traffic through.

Actions for Future Mitigation

We will be applying Cloudflare's edge throughout our network, which will help mitigate future denial-of-service attacks as they happen, without interruption of service.

You can monitor Linkly's uptime here: https://status.linklyhq.com.

We have increased the maximum parameter length to be 36 characters.

We have added specific filters to drop click IDs from ad networks such as Google, Meta and TikTok. The full list of stripped parameters can be found here.

Starting in January 2025, Linkly will be required to collect VAT for customers based in the EU.

Businesses in the EU do not need to pay VAT if they present a valid European VAT number.

You do not currently have a VAT number on your account.

If you have a valid VAT number, please update your billing details to include it by following the instructions here:

https://linklyhq.com/support/add-a-vat-number

Please note, it isn't possible for us to refund VAT collected if a VAT number wasn't provided at the time of the charge.

If you have any questions, please don't hesitate to contact us through the chat widget in your account.

We've rolled out improvements today to the query times for aggregate based queries such as parameters, ISP and robots.

These should load significantly faster, especially for workspaces with large amounts of data.

We've stopped tracking parameters with value lengths longer than 30 characters.

We've made this change due to the unique IDs some ad networks set, which distorts analytics results for parameters designed for marketing attribution.

This change should make params queries faster, and easier to navigate on the params tab.

Our API now allows you to set start/end times using datetime. This allows you to query data by hour inside a day, if you would like to.

As we continue to upgrade our systems for greater scale, we have adjusted our clicks database to use UUID4 as unique identifier, instead of sequential integers. This has been backfilled.

We've added the ability to get hourly breakdowns of traffic via the API.

Full documentation is available via OpenAPI here:

We've added support for timezones in our analytics reporting API.

You can now select the timezone for your query in the `clicks` method.

It is available in our API specification here.

We've improved the export of raw click data from Linkly as a CSV file.

We now include all the additional metadata we collect about a click (including location), and the query string, which is now encoded as JSON key-value pairs.

This is specifically for the 'all data' export.

We've dramatically improved the performance of large workspaces, including those with many millions of links.

In the past, loading and sorting these links could take too long and timeout.

We've significantly improved the way this works and now workspaces can handle millions of links with ease.

Our dashboard now updates in realtime, allowing you to monitor the flow of clicks as they arrive.

We've improved our shareable dashboards (public analytics) layouts to be more readable on wider screens.

Following our ending of the Call-To-Action beta, we've upgraded our Zapier integration to reflect the most recent version of our API.

There are no other changes.

We've improved our domain adding wizard so that it will wait til it sees your DNS records.

We recommend all customers attach a domain to use Linkly.

We've added the ability to share analytics for a particular link with a third party, without having to invite them to become a user.

We have added annual options for billing for customers who would prefer to pay in a single transaction.

We've made it easier to build API requests. You can now use a generator that will create a request for you, right inside Linkly.

Click the API Request button at the bottom of the Create New Link form to see a fully-formed `curl` statement you can use to add Linkly to your apps.

We've made it easier to find bulk import. You can now find it on the 'Create New Link' form, in the top right.

We've added inline help and 'Learn more' links in the 'Create New Link' form to make it easier to understand specific features.

We've moved the data export buttons (CSV/JSON/Sheets) to the top of the traffic detail tabs on the analytics reports, to make them easier to find.

You can use these to get the current view's data in a live feed.

If you're not using a custom domain with Linkly, you can now select one of our mirror domains from the dropdown on the show link page:

We still always recommend users attach a domain to Linkly for best results.

Our API has been upgraded to support arrays, so you can generate thousands of links in a single request.

Logins on Linkly will now last for 30 days, up from 24 hours. This should reduce how often you need to login.

We’ve ended our beta of Call-to-Action, and the feature will be discontinued.

Links using this feature will continue to function as normal, after which they will be converted to normal redirects.

We’ve improved the way dashboard buttons work. It works better for smaller screens and many data columns.

Previously Linkly QR codes all downloaded with the same name; now we’ll use the link name to make it clearer what the destination is.

Linkly now supports non-ASCII domain representations to shorten links with vanity URLs.

To use a non-ASCII international domain, just enter the ASCII representation of the domain into Linkly, and everything else should work perfectly.

We’ve improved the behaviour when generating reports with groups of links.

Changes:

• GET requests for grouped links now use a hyphen to separate link IDs. It should be possible to group several hundred links.
• Improved layout when displaying reports for many links.

We’ve recently added a feature to allow links to expire after a certain date & time, and optionally to specify a destination once they expire.

This feature can also be accessed via the API.

Today, we’ve significantly expanded our backend infrastructure, as Linkly continues to grow to be one of the largest global link tracking solutions available.

Traffic reports for large workspaces now load instantly (with some speedups being in excess of 100x), and dashboards load 10x faster.

These are just some of the improvements we’re making. There are millions of Linkly links generated each month, serving billions of clicks.

We’ve upgraded the reporting API endpoints for click tracking data in CSV, JSON & Google Sheets formats.

Performance is much faster for workspaces with large traffic volumes.

We’ve improved our Zapier Click Triggers to now include details of the link that was clicked.

This should make it easier to build actions without requiring an explicit Link ID. Old zaps should continue working without interruption.

We’ve made the dashboard export links more visible. You can now get the data from the dashboard as a live feed to use in Google Sheets.

As we proceed to move towards getting our Zapier Integration our of beta, we’ve made some improvements.

Previous versions of the integration have been deprecated, and users will need to upgrade to version 2.1.0 to keep their zaps running.

This should be last major update before getting our integration live. If you’d like to use our Zapier Integration, you can join the beta here.

You can search view and sort expiring links on the dashboard, by adjusting the column visibility.

Today we’re deprecating our Recaptcha traffic monitoring feature.

Our network based bot detection has improved. It is faster and more reliable, and supercedes the capabilities of ReCaptcha.

You can see our bot differential in the ‘Robots’ tab on the traffic reports.