> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/developer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/developer/guides/deploy-a-loyalty-microsite/configure-a-microsite-domain.md).

# Configure a microsite domain

When your microsite is provisioned, it is accessible using a [default URL on a WLL domain](#user-content-fn-1)[^1].

To provide a fully white-labeled and seamless experience, configure the microsite to be served from a subdomain of your own domain.

{% hint style="info" %}
Your custom domain should be setup before you do any work to [embed the microsite](/developer/guides/deploy-a-loyalty-microsite/embed-a-microsite-in-a-website-or-app.md) or [authenticate users](/developer/guides/deploy-a-loyalty-microsite/authenticate-users-in-a-microsite.md).
{% endhint %}

***

## Setting up a custom domain

To set up a custom domain for your Loyalty Microsite, follow these steps:

{% stepper %}
{% step %}

### Choose a custom domain

Determine a subdomain where you'd like the microsite to be accessible, considering your staging microsite too if applicable.

If embedding the microsite in a webpage, this should be the [same domain that webpage is served from](#user-content-fn-2)[^2]. 

We recommend the following subdomains:

* Production microsite: <kbd>loyalty.yourdomain.com</kbd>
* Staging microsite: <kbd>loyalty.staging.yourdomain.com</kbd>
  {% endstep %}

{% step %}

### Raise a support ticket

Raise a support ticket with [WLL Support](https://kbase.whitelabel-loyalty.com/product/services-and-support/wll-support/how-do-i-contact-support) using the template below, filling in the blanks:

> **To: <support@whitelabel-loyalty.com>**\
> **Subject: Custom domain setup for TENANTSLUG**
>
> ***
>
> Please begin the custom domain setup for our microsite and provide back:
>
> * the CNAME domain records which need adding
> * the SSL verification records which need adding
>
> I am aware that these records will need adding to our domain configuration within 48 hours of WLL supplying them back to us.
>
> **Tenant details (found in Loyalty Console > Settings > Tenant)**
>
> * WLL Tenant Data Centre: EU/US (delete as applicable)
>
> * WLL Tenant Name:
>
> * WLL Tenant Slug:
>
> **Microsite details (found in Loyalty Console > Interfaces > Microsites)**
>
> * Production Microsite Slug:&#x20;
> * Production Microsite Custom Domain:&#x20;
> * Staging Microsite Slug:&#x20;
> * Staging Microsite Custom Domain:
>   {% endstep %}

{% step %}

### SSL certificate request and microsite configuration

The WLL Support team will initiate the SSL certificate request and configure the microsite to allow access from your chosen custom domain. They will then send you a CSV file with DNS records which must be added to your domain within 48 hours.
{% endstep %}

{% step %}

### Add DNS records

Add the DNS records supplied by WLL Support to your domain's DNS configuration. This consists of:

* [x] Two **SSL verification records** (added as <kbd>CNAME</kbd> records). These are essential to secure your site and <mark style="color:red;">**must be added within 48 hours of receiving them**</mark>, or the verification will timeout. They must remain in-situ after being added – do not delete them after verification is complete or the SSL certificates will stop working.
* [x] Two <kbd>**CNAME**</kbd>**&#x20;records** to point to the microsite.

You can find instructions on how to add records to your DNS by searching the internet for 'Manage DNS records for x', where x is the name of your hosting provider i.e. GoDaddy or Hostinger.
{% endstep %}

{% step %}

### Confirm with WLL Support

Once you’ve added all **four records** to your DNS settings, reply to WLL Support to confirm as further actions are required on our side to complete the process.
{% endstep %}

{% step %}

### Adding additional domains (optional)

If you wish to use multiple custom domains for the same microsite, set up redirects in your own domain configuration for all secondary domains to your primary custom domain. This ensures consistency and improves user experience.
{% endstep %}
{% endstepper %}

[^1]: * Production microsites: <kbd>sitename.web.wlloyalty.net</kbd>
    * Staging microsites: <kbd>sitename.staging.web.wlloyalty.net</kbd>
    * Microsites served from our US data centre exist on <kbd>web.us.wlloyalty.net</kbd>

[^2]: So, if you're embedding the iframe on a webpage on `example.com`, the subdomain for the microsite would be something like `loyalty.example.com`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kbase.whitelabel-loyalty.com/developer/guides/deploy-a-loyalty-microsite/configure-a-microsite-domain.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.