Release Notes

We have performed some security maintenance on our systems and updated our infrastructure to the latest in-support packages.

This update only affects enterprise customers performing security audits on Linkly, and improves security.

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 released an update today that requires SSL (https) on all short-links.

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.

Linkly's infrastructure has had a major upgrade.

Our primary service has moved to the IP address `34.133.74.21`.

Most users will not notice any change. We have migrated all CNAME based domains to this IP.

Domains on the old A-record IP will continue to function.

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.

We've updated our default QR code domains (for accounts not using custom domains) to make scanning more reliable in some regions.

We strongly advise users attach a domain before printing QR codes as it reduces scanning errors significantly.

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.

We have adjusted our billing system so account downgrades are effected at the end of the billing cycle.

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 improved the API to return zeros where traffic figures for that date or hour are zero. Previously, the API would omit rows that had no data.

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

Full documentation is available via OpenAPI here:

We've updated the way we count unique users to make it more accurate.

Uniquessness is determined by the combination:

• Click Date (UTC timezone)
• Linkly Link ID
• Remote IP Address

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 have added the ability to purchase domains from Linkly, and have them automatically attached to your workspace.

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 updated our login page to use Sign in with Google as the default login.

This is to help facilitate one-click, passwordless login to our service.

You can still use a valid email address to login, using our passwordless authentication.

If you are using an email and would like to attach a Google account, you can add it as a user under Users in your workspace.

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.

We've removed a footer component in the app that was blocking some text on some devices.

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

We've updated our domain admin page to load faster for workspaces with many domains. You can add up to 50 domains to your Linkly workspace, to create custom branded short links.

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

We've made some improvements to our dashboards that should allow them to load substantially faster.

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 datepicker's functionality for different timezones.

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 fixed a bug today that caused the 'search' field to disappear when searching for parameters that didn't exist in traffic reports.

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.

Linkly's pricing will change on 15 May 2024.

The new pricing will be:

• 25000 clicks $34/month
• 50000 clicks $59/month
• 100000 clicks $94/month
• 200000 clicks $154/month
• 500000 clicks $289/month
• Unlimited $499/month

We know price increases are never welcome. We've done our best to minimize the impact; this is the first increase since 2019.

Switch to an Annual Plan and Save

In addition, for customers who switch to an annual plan before 15 May 2024, they will be able to retain their current pricing for a further 12 months.

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

We've made our link shortening API available on RapidAPI. Find our integration here.

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.

Since the deprecation of Linkly's Recaptcha Click Fraud detection, we have now updated the API to reflect this change.

Users can still detect bots and inorganic traffic using Linkly's bot detection.

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 fixed an issue where multiple IP addresses couldn't be excluded from the traffic logs.

You can exclude IPs from being logged by going to Settings -> IP Exclusion.

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 removed 'saved searches' in the search box on the dashboard, as it was causing significant confusion amongst users.

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.

We've improved our domain adding instructions and built an interactive wizard to help you set them up quickly.

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.

Linkly's dashboard now features persistent sort, so now you can always view your links the way you would like to.

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

Users who previously had a password on Linkly can now login using a passwordless login.

Users old passwords have been discarded entirely.

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

Today we’ve significantly improved our CSV import functionality. Now, Linkly will return a spreadsheet of imported links, or link creation failures. In addition, it’s now possible to set up rotators, device and geo-targeted links directly from a spreadsheet.

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 link generation API to automatically generate slugs for custom domains. It works for spreadsheet uploads and API requests.

Now, if you select a domain, but leave the slug field blank, Linkly will automatically generate a slug for you, and return the complete link in response.

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

You can now go straight to reports or open a link from the ‘Edit link’ page.

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.

We’ve updated the ‘random’ button on the ‘Create New Link’ page to have a wider choice of random possibilities for users with a large number of links. It can now generate 14 million possible combinations, so a collision is less likely!

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.

Today we are removing Linkly’s conversion tracking functionality.

We’re doing this as there are better solutions for tracking conversions, which both require javascript to be installed on the target website.

We recommend all users enable Goals/Funnels in Google Analytics if they would like to track conversions. You can still join this data to Linkly, using UTM tags.

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 made some backend improvements that significantly increase the loading speed of the dashboard for users with high-traffic workspaces.

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.

We’re deprecating our support for the Google Sheets Addon, available via the Chrome Web Store, in favor of the Google Sheets Live Data Feeds from Linkly.

These provided added reliability and flexibility. The feeds are standardised and can also be imported into other tools, such as Google Data Studio. Feeds are available as JSON & CSV.

Find out how to use the Google Sheets feeds here.

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.

Report tabs now remember their position when changing settings

Tabs in Linkly’s traffic reports now remember their previously selected location when changing settings/dates/links.

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.

Today we’ve upgraded our systems to remove Google’s deprecated Google Analytics 3 (Universal Analytics).

Google Analytics 4 is now the preferred way to track Linkly campaigns using GA.

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.

Links are now shown in the order of descending 30-day traffic by default.

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.

We have removed the old OpenAPI reporting URLs, as they have been superseded by the copy-and-paste API requests available inside Linkly.

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.

We’ve long monitored our uptime internally. Quick responses to outages are particularly important for an URL shortener processing millions of clicks per day. We’re now publishing our uptime and system status here.

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

When you search in the dashboard, the export links will now update a search parameter, meaning these API endpoints now allow filtering of your links. It also works for Google Sheets.

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.