Loyalty Microsite setup

Learn how to set up and customise your Loyalty Microsite, covering deployment, authentication, domains, language, profile schema, and branding options for a seamless, branded loyalty experience.

Setting up a Loyalty Microsite

This setup guide outlines the six essential steps to configure, deploy, and brand the microsite for your users. By completing these setup steps, you’ll configure a fully branded, seamlessly integrated Loyalty Microsite that delivers a cohesive user experience.

For detailed instructions on any of the steps, follow the links to each dedicated article. Your onboarding manager should give a recommendation of which approaches to take during the relevant phases of setup. Work closely with them to ensure setup is completed correctly.

Each step should be completed for both your production and staging microsite using the relevant custom domain you setup. The default web address, noted below, should not be used as standard unless otherwise specified by your onboarding manager.

  • Production (Live): $micrositeSlug.web.wlloyalty.net

  • Staging (Test): $micrositeSlug.staging.web.wlloyalty.net


Deployment Checklist

The following checklist provides a step-by-step overview to guide you through each required task for launching your Loyalty Microsite. Refer to the linked articles for more in-depth information on each item in the checklist:


1. Deployment type

Your deployment type determines how users will access the microsite. Options include:

  • Standalone Website / PWA: The microsite operates as a standalone website, accessible through a custom URL like rewards.domainname.com.

  • Embedded in a Website: The microsite is embedded within an iframe on an existing webpage of your website, allowing users to access the loyalty program alongside other site content.

  • Embedded in a Mobile App: The microsite is displayed within a web view of a native mobile app, accessible to users within the app’s interface.

For more information, see 1. Deployment type.


2. User authentication

Authentication allows users to log in to the microsite and access their rewards, points, and profile. The choice of authentication approach depends on the deployment type and user experience you want to provide:

  • Interactive Authentication: Users create a dedicated account for the microsite, going through a separate sign-up and login flow specifically for the loyalty program.

  • Embedded Authentication: Best for embedded deployments, this option allows for a seamless experience by automatically logging users in using their existing app or website credentials.

Refer to the 2. Microsite authentication article for a step-by-step setup guide.


3. Custom domain

The microsite is hosted on a default White Label Loyalty domain (sitename.web.wlloyalty.net). However, most clients prefer to use a custom domain (e.g., loyalty.yourdomain.com) for a cohesive, branded experience.

If you’re using embedded authentication or embedding the microsite within an iframe or mobile app, setting up a custom domain is essential. This ensures that authentication functions properly across modern browsers, as many browsers block cookies and session data from third-party domains.

Learn how to configure a custom domain in the 3. Custom domain article.


4. Language support

The Loyalty Microsite supports multiple languages, ensuring users see content in their preferred language if it is available. You can set a default language for instances where a user’s device language does not match an available translation.

For configuration details, see the 4. Language support article.


5. Profile schema

The profile schema defines the user profile fields required for the program, such as name, email, and location. Primarily relevant for interactive authentication, the profile schema specifies what information a user must provide when first accessing the microsite and when updating their profile.

For clients using embedded authentication, profile fields are typically managed directly in the host app or website’s profile section, making the microsite’s profile schema optional.

See the 5. Profile schema article for further details.


6. Customization

The Loyalty Microsite can be branded and customised to align with your brand guidelines, ensuring users enjoy a cohesive, recognisable experience that fits seamlessly with your app or website. The microsite’s layout and theming options allow you to adjust colours, fonts, and key layout features to match your brand and user interface.

Refer to the 6. Customization article to explore the full range of customisation options.


Common implementation approaches

While the Loyalty Microsite allows for flexible configurations to meet your specific requirements, three common implementation approaches are widely used:

  • Standalone: The microsite functions as a standalone website, with users creating a dedicated account specifically for the microsite. This approach is ideal if you want to direct users to a separate loyalty program website without embedding it in an existing app or site.

  • Full-Embed: The microsite is fully embedded within an existing website or mobile app, serving as the dedicated “rewards” or “loyalty” section. With this approach, users are seamlessly authenticated using their existing login credentials, creating a cohesive experience where users access the loyalty program within the familiar interface of the host app or website.

  • Partial-Embed: In this setup, only certain parts of the microsite are embedded within your existing app or website. This approach is beneficial if you want to handle simpler loyalty program elements directly within your custom interface but prefer linking to the microsite for more complex flows, such as reward redemption or payout processes.

Last updated

Was this helpful?