An enduser can be redirected

  • before the login page is shown
  • after a successful login


  • hours or days after a successful login with Planned redirect


Redirect before login

This redirects a user to an external website before the login page is shown.


  • Free to use (walled garden): It’s important to understand, that a device is still offline.
    All needed URLs (including it’s dozends of dependencies) need to be added to the Free to use links.
  • The external website has to link back to the login page (see below) otherwise users don’t know how to reach the login page again

To add a link back to the IACBOX login page, add this special parameter to avoid redirect loops:

Exchange the domain if a custom domain is used.

Optionally a device can be taken online immediately with a link back to the login page. It uses the Free login login method, so ensure it is enabled
To use this feature the autologin URL parameter needs to be set:

Redirect after login

This redirects a client to a certain URL after a successful login.

Android 11+ and higher

With some Android 11 and most Android 12 devices there is support for the so called Venue URL in the CAPPORT API. With an udpated IACBOX v21 the redirect after login URL is set as Venue URL which will popup as notification. In contrast to a real automated redirect after login the user has to tap on that notification. The big advantage here is, that this URL is now opened in the normal browser (and not the captive browser with limited functionality).

Example notification displayed on Android 12 after a successful login:



For the redirect after login URI, Placeholders can be used to transmit certain information from the client’s browser with the redirect. Following options are available:

$IPThe IP address of the client device
$MACThe MAC address of the client device
$PSEUDOMACA hash of the original MAC address, for GDPR reasons
$VLANThe origin VLAN of the client device
$LANGThe full language code of the client device, e.g. en_EN
$LANGSHORTThe short language code of the client device, e.g. en

These placeholders are meant for endpoints which support these parameters and can work with them. An example of usage would be an endpoint which expects the language code, the IP address and MAC address of a client device:$LANG&ip=$IP&mac=$MAC

The placeholders will get replaced with their respective values on redirect.

Planned redirect

Planned redirect allows to

  • bypass the problem, that Android does not support Redirect after login
  • execute a delayed redirect after some time (hours to days). For example to collect in-stay guest feedback (ReviewPro)


A special version of Planned redirect is an integration with our technology partner ReviewPro which allows in-stay guest feedback. The advantage of a delayed redirect is that guests need some time to know what’s good or bad during their stay. With Planned redirect guests are taken offline in the night after 1 or 2 days. After opening their device again they see a page. They can decide to give feedback or get immediately online again.