Rules can be configured to be evaluated only for the page where the Redirect Toolkit module was added or they can be configured to be evaluated for all pages/requests.

Redirect users based on the website they came from.

Redirect users by matching criteria in their profile (such as First Name, Email Address or any Profile Property).

Redirect user by targeting roles they belong to.

Redirect Toolkit integrates with geobytes.com to support redirects based on geographical information (geobytes offer 20 free checks per hour, if you need more look at their pricing)

Redirect users based on parameters passed to current request in GET Query String, POST Data or Browser Cookies.

Redirects are matches against current URL (either the domain name or full URL)

This type of redirect provides a large number of options to target specific browsers, browser versions, mobile devices, browser capabilities (such as JavaScript support or Cookie support), Operating System and so on.

Use date picker control to select date periods when redirect should happen. Or create redirects based on time of day or day of week.

Redirects are matched against the page view count (this is actually maintained by Redirect Toolkit per rule and it represents how many times the rule was evaluated)

The random is specified as a probability, so for high traffic this allows redirecting a percentage of users.

Follow SEO good practices, redirect using Temporary HTTP redirect (302) or Permanent HTTP redirect (301) whenever you're moving pages around.

Run an SQL Query, evaluate the result and redirect based on that.

Regardless of their type, Redirect Rules can be ordered so that the first rule that matches selected criteria for current user is executed.

Each Redirect Type exposes a number of properties. Each property supports several operators that can match strings, compare numbers, run regular expressions, match substrings and more.

If MyTokens is installed, Redirect Toolkit will call it to replace tokens in value and URL fields.

Using this function makes it fast to create many redirects that are similar.

A Redirect Rule can be configured to redirect either to a user provided URL or an existing page from the portal.

Redirect Toolkit allows specifying POST data that will be sent to target URL using POST. My Tokens can be used in POST data to basically pass anything you can think of.

This option allows for creating exception rules in Redirect Toolkit to prevent other Redirect Rules to match down the stack. So the user stays on current page.

If user is logged in, this option grants/removes the selected security roles. This is a very powerful option to enforce workflows.

Redirect Toolkit allows tracking how many times each redirect was executed.

Redirect Toolkit can be easily extended with new reports which are generated from SQL queries.

Redirect Toolkit provides logging capabilities per rule, so it can give a detailed report of what users where affected by each rule.

Before the Redirect is executed, Redirect Toolkit can save the referrer for you in Browser Cookies or Server Session so you can reference it at a later time (for example, by using it in conjunction with MyTokens).

This option allows saving any value in Cookies/Session/User Profile just as Save Referrer function, except you can save anything (especially using My Tokens integration)

Redirect Toolkit can be instructed to logout user before doing a redirect.

Redirect Toolkit can be configured to redirect user either from the Server Side or from JavaScript after a number of Seconds have elapsed. Additionally, a countdown timer can be displayed on screen.

Redirect Toolkit has a decoupled interface that, based on configuration files, it loads redirect types dynamically (even from external assemblies), therefore making possible to extend or even remove condition types.

Redirect Toolkit operators handle most common scenarios, but when more is need it also has a decoupled interface for operators too that allows extending it with new operators or rewire existing ones.

Redirect Toolkit has a decoupled interface for additional actions too, loading actions at runtime based on configuration. This is where you'll want to extend Redirect Toolkit most.

Preferred method for granting support is through our Forums. We also respond via email and Snowcovered Help Desk.

After the 1 Year of Updates subscription ends, it's possible to extend it for another year at 25% of the cost of a new license.

We stand up for our products and will grant support for the entire lifetime of a version; as new versions reach the market, older versions will be marked as obsolete and support will end. Our policy warrants that there will be at least 1 year of support for each version.