Premises options
The Premises Options section outlines how to manage content access for end users using tags and IP addresses, allowing for customized access and user journeys.
The Premises Options section defines how to identify the content access provided to the end user based on tags and IP addresses.
A single account can have multiple tags, and multiple accounts can include the same tags. Tags group accounts, and are used to automatically grant access to any end user whose IP address matches one configured for that tag.
You can only use the
{{blaize.request.premisesAccountName}}
mustache variable in both custom component blocks and component templates. This variable relates to your matched IP addresses. When rendered on your site, the variable is either populated with the name of the matched account name or remains blank if no account is matched. For further information on using mustache variables, see the User Variables in Component Templates
topic.
If the hotel or cafe in the example above allows only ten free views each day and the anonymous end user uses their free views one day, they can return the next day and enjoy a further ten free views. If cookies are not cleared, the end user’s session is retained; that is, they are considered to be the same anonymous user as the previous day.
You can use the On-premises decision node in your rules canvas to customise the user journey based on whether the end user’s IP address matches any accounts. If you have grouped accounts using tags, the decision node can also check whether any account matches the specified tag. The logic of this decision node matches the IP address and, if specified, then matches the tag condition. For further information on the On-Premises decision node, see the Access topic under Features or Redirects .
To complete the Premises Options, complete the following steps: