Zephr Beta User Guide

Redirect Decision Points

0 views 0

Use this guide to understand the different decision options available to you when creating a Zephr Redirect.

The options are found in the decision bar, found above your Rule Builder canvas. Click the segment title to see further options below it.

User

  • Device Type: Define rules for users of specific devices – desktop, mobile, appliances, or crawlers.
  • Country: Define rules for users browsing in specific countries.
  • Date & Time: Define rules based on the date and time your user is accessing the site.

Content

  • Content API: When Zephr is integrated with a Content API, this allows you to enter a key-value pair to be checked for within your access decision.
  • Content API Age: When Zephr is integrated with a Content API, this allows you to enter a time-based key-value pair to be checked for within your access decision.
  • Published Date: Define rules that are older or newer than a certain time period (in hours)
  • Meta Tags: Define rules for specific meta tags and values.
  • URL: Define rules based on a specific URL or URL path.
  • Sites/Site Groups: Define rules based on the site or site group a user is accessing the site on.

Access

  • Trials: Allows you to grant a trial to the user accessing the site. Set the parameters for your trial, such as the number of views the user should receive, and the frequency with which the trial should recur. Click Add Remaining Trial Count to specify different behaviour for users based upon the number of views they have remaining. Read our Creating a Trial guide for more details.

Sub Rules

  • Sub Rule: Used to create a Sub Rule within your user journey. To use this, drag the node onto your canvas. Give your Sub Rule a title and click Save. This will open a new canvas, specifically for your Sub Rule. Build your Sub Rule as required. When you’re ready to join this Sub Rule to your main rule, select Output Option. Add an output option for every branch required to be connected from your Sub Rule, to your main Rule. Read our Sub Rule guide for more information.

Bucket Test Segments

  • Bucket Test: Used to create a rule variation based upon a Bucket Test Group, as set up via Settings > Bucket Tests.

Modify Response

  • Replace Body: Adding this into the flow of a request rule will prompt you to input details for the Body value that you wish to replace. This will replace the body on the original response.
  • Add Header: Adding this into the flow of a request rule will prompt you to input details for the header you wish to alter, in the form of a key-value pair.
  • Remove Header: Adding this into the flow of a request rule will prompt you to input details for the header you wish to remove.
  • Clear Headers: Adding this into the flow of a request rule will mean that all origin response headers for the site user are cleared, at the point that users reach this part of the rule.

Responses

  • Allow: Allows access to the request. Returns a 200.
  • Deny: Denies access to the request. Returns a 401.
  • Response Status: Allows you to set a customer response status for the request.
  • Redirect: Redirects the user to a specified URL. Choose between a Simple Redirect or a Template Redirect, which allows you to set a redirect with various values. By default, {{path}}, {{contentApi}}, and {{metatags}} are available for use.
  • Preserve Origin Status: Adding this into the flow of a request rule will ensure the response code, headers and body of the origin’s response remain unchanged.

Advanced

  • Referrer: Define rules based on a user’s referrer.
  • JWT Token: Define rules for specific JWT tokens
  • User Agent: Define rules for users based on user agent.
  • Browser: Define rules for users based on the browser they are using.
  • Run Custom Script: Allows you to write a custom script for use as a custom decision point.