- Changelog
Changelog
Regex match optimalizations
ImprovementWe've modified our regex match engine to be better in line with expectations. If a regex rule and full path redirect is set-up, we first check the ful path redirect, then the regex match, and fallback to the homepage. This ensures the visitor always lands at the correct destination.
API token management
ImprovementWe've reworked our API management in the redirect.pizza interface which adds some great additions:
- You may now create multiple API tokens under a single team
- You may label an API token with a descriptive name
- You can now see when an API token was last used
- You can now see how many calls per month are made per API token
- When generating an API token, you can only see the API token value once. After that, the API token is never shown again. This is conform best practice security practices.
Of course, our API keys are still automatically secret scanned on GitHub.
Query string destination variables
New featureWe’ve added the ability to use the query string parameters as a destination variable. For instance if you want to use the "page" query string from "example.com/contact?page=2" in your redirect, you can use the {query.page}
variable.
To make this even more powerful, you can also use this in the dynamic destinations to traffic steer based on exact (or partial) query string matches. For instance, want to redirect all page numbers higher than 2 to another destination, you can use the following expression: query.page >= 2
ISO 27001 certified & SOC 2 Type 2 on the way!
ImprovementWe are very pleased to announce that redirect.pizza has achieved ISO 27001 certification, reinforcing our commitment to robust data security standards.
Moreover, we are on track to attain SOC 2 Type 2 certification within the next two months, further enhancing our commitment to maintaining the highest levels of data protection for our clients.
Read more here.
IP destination variable
New featureWe've added an IP destination variable: {ip}
. This contains the IPv4 or IPv6 address of the connecting client.
This can be useful in combination with our dynamic destinations feature to traffic steer your traffic based on incoming IP addresses. For instance, redirect all the traffic from the office to destination A, and the rest to destination B.
Dynamic destination management in API
ImprovementExciting improvement to our API: You can now manage both single and multiple destinations with ease! Input a string for one destination or an array for multiple ones, including dynamic destination expressions. For more information, visit redirect.pizza/docs. Enjoy this new level of flexibility!
Tracking the full referrer URL
ImprovementExciting update for data enthusiasts! Analytics now captures the full referrer URL, offering a deeper insight into your referral traffic down to the exact page path. Enjoy the flexibility of toggling between 'host' and 'URL' views in the top referrers table. Plus, our raw analytics data now includes both host and URL options, giving you a comprehensive view of your traffic sources.
We've expanded our import functionality to support multiple destinations. Now, you can specify various redirect destinations using a JSON format, identical to the array format in our API. This enhancement allows complex destination set-up, right from your initial import sheet.