Zephr Beta User Guide


0 views 0

Zephr’s Sites section is where you set up and configure your company sites to run through Zephr’s CDN. Each site can have multiple domains and sites can be grouped into easily managed site groups. Once added, each of your sites can be set up to use Zephr through a single admin console, meaning you can create global user journeys across each of your brands, or build out specific use cases for individual titles.

The Sites section is also where you’ll create cache rules, and set up custom error pages to be served through the Zephr CDN.

In this guide, we will discuss the different options available within the Sites page. For a comprehensive guide to going live with Zephr, read our Go Live guide.

Configuring a Site

First off, navigate to Delivery > Sites. Here you will find a list of Sites already set up to use the Zephr CDN. To add a new Site, click the Add A Site button.

A list of two sites configured on Zephr

On the Add A Site page, give your Site a title. We recommend this being in line with the core URL of your website, so it’s easy to find in your list. For example, in setting up www.zephr.com, we would title our Site ‘Zephr’.

Browser Config

Your Browser Config settings will affect things that get sent to a user’s browser. Here you can set CORS Allowed Origins, which let you use the website from a domain that isn’t the site’s domain – such as using an API through Zephr in a cross-origin matter.

This section is also where you can enable reCAPTCHA to be used on your registration forms, as an additional layer of protection, ensuring your site sign-ups are genuine. Use the toggle to turn this option on, and select which part of your form you would like the reCAPTCHA logo to appear in. For more information on your options, read our reCAPTCHA guide.


The Domains section is where you determine which domain overrides are exposed to the end-user. Put simply, which URLs will a user be able to use to access your site via the Zephr CDN. This allows you to use Zephr from a number of different domains to access the same origin.

By default, cdn.zephr.com will be available, however, for testing purposes, you may wish to set up {yoursite}.cdn.zephr.com. When you go live, you will also add in all of the domain options for your core site URL, such as www.zephr.com, zephr.com, and sub domains like shop.zephr.com.


In Zephr, your origin site(s) refers to the base website that will sit behind Zephr. This is the version of your site with no user journey rules or transformations, which your domain usually points to. Zephr’s CDN becomes a conduit between your domain and your URL, allowing us to serve your content, create custom user journeys, and add a layer of user authentication.

Set your Default Origin URL to your base origin site, so Zephr can serve the site via our CDN.

If your set up is slightly more complex, Origin Routes allow you to point different requests to different origins. For example, you may serve your /shop section via a different Origin, and you would add this here. Click Add An Origin Route, enter the Base Path, such as /shop, then enter the Origin URL this should be linked to.

Cache Rules

Zephr caches the content from your Origin as a means of improving site performance when making access decisions.

By default, website content is cached for 10 minutes, meaning updates made to your CMS will take up to 10 minutes to propagate to the end-user via Zephr.

In some cases, you may wish for this cache to be removed – for example, if you publish breaking news and want pages from /breaking-news to be excluded from the cache.

This is possible by adding a Cache Rule.

First, click Add a Cache Rule, and give your Cache Rule a title.

Next, add your URL path, for example, /breaking-news

Finally, select which Cache Exceptions you would like to make. Here you can choose to disable the Origin Cache, meaning your origin content for this path will not be subject to the 10 minute cache time.

You can also choose to Disable the User Attribute Cache. In this setting, if a user edits information stored in a User Attribute, then refreshes the page, it ensures their information is up to date when used within a decision.

Example cache rule removing the origin cache on breaking news content

Please note: Removing the origin cache could have an impact on performance (as Zephr’s cache means content can be served to visitors more quickly) and should be tested post-implementation.

502 Error Page

The 502 Error Page section is where you manage the error page your users will see if there is a 502 on your site. Chances are, you’d like your users to see a branded error page letting them know what’s happening. To display a custom 502 error page through Zephr, edit/add your HTML in this section.

Screen showing html field for editing 502 error page.

Once this is saved, when a user gets a 502 on the site, we’ll display what you’ve added in.

All Other Errors

All other error pages are managed in this section. As with the 502 Error Page, edit or add your HTML in this section, and when done, click Save.

Managing Your Sites

Once you have saved your Site configuration, it will display within your Sites list, under Delivery > Sites.

To edit your configuration, locate the Site you wish to amend within the list, and click the name.

To delete a Site, locate the Site you wish to amend within the list, and click the Delete button. You will be prompted to confirm you wish to delete this site. Note, deleting a site will remove it from Zephr, so users no longer access your site via the CDN. For live sites, there may be domain name changes you need to make following this change. We recommend speaking to your Customer Success Manager before deleting a site.