Publish your web app to a custom subdomain, so users can access it at a professional, branded URL you control. A custom domain builds trust with your audience, reinforces your organization’s identity, and lets you take advantage of deep linking functionality if you also publish your app as a native iOS or Android app.

Before you start

Custom domains are available on paid plans only. You also need access to your domain’s DNS settings through your domain registrar or DNS hosting provider (e.g., GoDaddy, Namecheap, Cloudflare).

Contents

Configure your custom domain in Fliplet Studio

  1. Open your app in Fliplet Studio.
  2. Click the Publish button in the top right corner.
  3. Select the Web publishing option from the dashboard.
  4. Click Add Custom Domain. This opens the domain setup overlay.
  5. In the Domain name field, enter the subdomain you want to use — for example, app.example.com.
  6. Click Next to save your subdomain and proceed.

Note: You must use a subdomain (such as app., portal., or info.) of your primary domain. You cannot use a root domain (e.g., example.com) directly.

Verify domain ownership and enable SSL

This step confirms you own the domain and triggers automatic SSL certificate setup.

  1. After saving your subdomain, Fliplet Studio displays the “Setting up domain DNS records” screen with a table of CNAME record details.
  2. Copy the Name / Host and Value / Data values from the table. Use the copy icon next to each value for convenience.
  3. Log in to your domain registrar or DNS hosting provider’s control panel.
  4. Navigate to your domain’s DNS settings. This is typically found under “DNS Management,” “DNS Records,” or a similar section.
  5. Add a DNS record with the type CNAME.
  6. In the Host or Name field, enter the Name / Host value you copied from Fliplet Studio.
  7. In the Value, Target, or Points to field, enter the Value / Data you copied from Fliplet Studio.
  8. Save the CNAME record in your DNS provider’s settings.
  9. Return to Fliplet Studio and click I have copied the CNAME record to my DNS provider.
  10. Fliplet Studio verifies the CNAME record. When successful, the status changes to “Verified” and you receive a confirmation email.

Note: Some DNS providers automatically append your domain name. If so, enter only the subdomain part (e.g., app instead of app.example.com).

Finalize subdomain association

Once domain ownership is verified, Fliplet Studio provides a second set of CNAME records to associate your subdomain with your web app.

  1. Return to your domain provider’s DNS settings.
  2. Add another DNS record of type CNAME.
  3. In the Host or Name field, enter the Name / Host value of the second CNAME record from Fliplet Studio.
  4. In the Value, Target, or Points to field, enter the Value / Data of the second CNAME record from Fliplet Studio.
  5. Save the CNAME record.
  6. Return to Fliplet Studio and click I have copied the CNAME record to my DNS provider.
  7. Fliplet Studio performs a final check to confirm the subdomain is correctly associated with your app.

Your custom domain may take a few minutes to publish. The web app goes live automatically, and you receive an email notification when it is ready.

Once both verification steps are complete:

  • Your custom domain is linked to your Fliplet web app
  • An SSL certificate is automatically applied
  • Your app is accessible at your custom domain (DNS propagation can take up to 72 hours)
  • You can optionally configure SEO settings for your web app

Change or remove a custom domain

If you modify or remove a custom domain, take these additional steps to ensure continued functionality:

  • Republish native apps — If your app is published to Apple or Google, republish to the App Store and Google Play so they reference the updated domain.
  • Update SSO settings — If Single Sign-On (SSO) is enabled, update the callback/redirect URL in your SSO provider to match the new domain. For setup instructions, see Single sign-on (SSO) with SAML2.
  • Verify access — Confirm that users can access the app and log in via both web and native platforms without errors.

Deep linking for native apps

A custom domain enables deep linking for native iOS and Android apps. When users tap a link or scan a QR code that matches your custom domain, their device opens the content directly in your native app instead of the browser. If the app is not installed, the link opens in the browser as a web app.

Deep linking requires a custom domain — without one, the operating system cannot verify that your app owns the domain, and deep linking does not work.

For setup instructions, see Deep linking for native apps.

Troubleshooting

If domain verification does not succeed:

  • Review CNAME records carefully — Confirm that the Name / Host and Value / Data values match exactly what Fliplet Studio provided. Typographical errors are the most common cause of verification failures.
  • Allow time for DNS propagation — After adding or modifying CNAME records, wait at least one hour before retrying the verification step in Fliplet Studio. In rare cases, full propagation can take longer.
  • Check for typos — Re-examine the subdomain you entered in Fliplet Studio and the CNAME records in your DNS settings for spelling mistakes or extra spaces.

If issues persist, contact the Fliplet support team or your DNS provider for assistance.

Related articles

Was this article helpful?
YesNo