Elara Help

Appearance

Testing & launch ​

Test widgets on the same domains customers will use. Domain settings affect sign-in, checkout returns, and account redirects.

Test on a staging page first ​

Publish each widget on an unlisted page of your own website before you link to it publicly, and make sure that page's domain is in Allowed domains. Sign-in, checkout returns, and account links all depend on the domain matching, so a test anywhere else does not prove the live setup works.

Each domain is matched on its own, so list every subdomain you publish on. staging.yourstudio.com is not covered by an entry for yourstudio.com.

For the email-link sign-in check, enter an email address whose inbox you can open and follow the link Elara sends. There is no captured-email or delivery-free test mode in the CRM. If you need to test without sending a real email, ask Elara support to arrange it.

Pre-launch checks ​

  • Open each widget page on desktop and mobile.
  • Confirm a new customer can create an account and book.
  • Confirm an existing customer can sign in and book with either method.
  • Add a password in Account > Password, sign out, and sign back in with it.
  • Confirm Forgot password? allows recovery through a fresh email link.
  • Confirm paid checkout returns to the website.
  • Confirm account links return to the customer account page.
  • Confirm the CRM shows created reservations, payments, and customer records.

When a widget does not load ​

  • Check that the script URL is reachable.
  • Check that brand-id matches the brand ID shown in Website Integration.
  • Check the browser console and network tab for failed requests to Elara.

When a widget shows generic branding but will not load its content ​

With the standard brand-id-only snippet, a widget that shows the generic Sauna Studio name and blue color, then reports "We couldn't load the schedule. Check your connection and try again." or "Payment setup is unavailable. Please try again or contact the studio.", is almost always showing a domain problem rather than the connection or payment problem the message suggests. The /api/config request that loads studio branding is checked against Allowed domains. When that request is rejected, the widget uses its generic branding fallback and its content requests fail as well.

Confirm the page's domain is listed in Allowed domains in Website Integration. Requests from a domain that is not listed come back as 403 Origin or Referer host is not allowed, which the network tab shows against /api/config and the other Elara API calls.