Site Customization Settings
Custom User Agent String
Providing a user agent string is one way web browsers identify themselves to websites. Checking the user agent string is one way a website can determine if it is being loaded on an iPad, for example, or a full-size desktop browser.
Default: blank, defaulting to the user agent string for the current version of WKWebView or UIWebView (the browsers that Kiosk Pro is based on)
While not all sites use user agent sniffing to decide how to serve content, some choose to serve a smaller mobile site or limited functionality to phones and/or tablets based on this string.
By providing a custom user agent string, you have more control over how content is served by certain websites. Finding what works best for your kiosk will depend on the content, purpose, and design of the site itself.
If you want to use user agent strings for the mobile version of Safari for iPad or the desktop version of Google Chrome, you can easily set these using remote settings .xml files on our site:
How to set a custom user agent string through Remote Setting Control
- In Kiosk Pro settings, scroll down to the Remote Settings Control category.
- Enable = On.
- For mobile Safari: XML File Location = http://www.kioskproapp.com/mobile.xml
- For desktop Safari: XML File Location = http://www.kioskproapp.com/desktop.xml
- For desktop Chrome: XML File Location = http://www.kioskproapp.com/desktop-chrome.xml
- Run Kiosk Presentation.
These XML files contain only this user agent string setting and the settings to return the remote settings control to their default empty positions. To test which user agent string a browser is returning or if you need to find a user agent string for a different browser, you can visit UserAgentString.com
Added in version 7.6
This feature allows you to apply your own custom CSS to webpages shown in Kiosk Pro, giving you additional ways to customize how a site is displayed in your kiosk.
This can be used for third-party sites where you wouldn't otherwise have the ability to add your own CSS directly to the page or to present a custom version of your own website specifically for kiosk use. If you use this feature with a third-party site, you will want to check your kiosks on a regular basis to make sure that the underlying page has not changed and that your CSS styles are being applied as expected.
Custom CSS is added at the end of the head tag. If the page defines specific styles inline within their HTML tags using "style=" or places a style tag within the body of the page, those styles will take precedence over any custom styles added through Kiosk Pro.
This setting allows you to define one or more URLs (web addresses) where custom CSS will be inserted.
The ‘Matched URLs’ setting can accept multiple URLs, which should be separated by semicolons. It also supports wildcard characters so you can match multiple or dynamic URLs in that way as well:
- ? - matches any character zero or one time, matching only one time
- * - match any character zero or more times, matching as many times as possible
- '1' is matched by: '*' or '?'
- '12' is matched by: '*' or '**' or '*?' or '*2' or '1*' or '??' or '1?' or '?2'
- '123' is matched by: '*' or '???' and so on
For example, if you were using a URL that appended a dynamic parameter like ‘http://www.example.com/?search=term’ where ‘term’ could be any value, you could use a wildcard match.
Setting the ‘Matched URL’ setting to ‘http://www.example.com/?search=*’ would mean that any URL that matched the part of the string preceding the ‘*’ character would have custom CSS applied.
Local File Path for Custom CSS
This setting allows you to define the local file path for custom CSS to be inserted.
Custom CSS files must be stored locally in the Kiosk Pro documents folder. Instructions on moving files to the device are available here.
Added in version 6.7
This setting provides another way to easily identify traffic from your kiosks.
- On Homepage Only (default)
You can use general parameters appended to the app's Homepage to identify traffic coming from Kiosk Pro, allowing you to serve specific content to visitors coming from a kiosk or to tag outgoing data.
Please note that variables are inserted immediately following the page load event and cannot be read directly through a function assigned to the 'onLoad' event. If you need the variables in this scenario, we would recommend using a short 'setTimeout' to delay long enough that the app can insert the variables.
In Plus and Enterprise, you can also define unique parameters for individual kiosks based on their Unique iPad ID and any Group ID’s set in the app’s settings.