Skip to main content

Lesson 6 of 6 · 1:46 · Beginner · Webflow

Go live

The checklist for switching from test mode to live before real members arrive.

Where this fits

Your plans, payments and gated content are all set up in test mode. Now it’s time to launch.

By the end of this lesson you can

  • Go through what to do before your membership site launches
  • Switch from test mode to live before real members arrive

Lesson notes

How it works

How Memberstack decides between test mode and live mode

Every new Memberstack app starts in test mode. Your site switches to live mode based on its domain, not on the Test Mode or Live switch in the dashboard header. That switch only changes which data you're looking at in the dashboard. When someone visits your site, Memberstack checks the URL against the Application Domains list in Settings, Application. A domain marked Live Mode runs live, with real payments and live members. A domain marked Test Mode shows the Test Mode badge and accepts test cards.

Your .webflow.io staging domain should stay in test mode. That gives you a safe place to keep testing after launch.

What carries over and what doesn't

Your plans, gated content, permissions, custom fields and metadata fields carry over when you go live. Members don't. Test mode and live mode keep separate data, so test members won't appear in live mode and can't be moved across. Test mode is also capped at 50 members.

Test and live use separate API keys. If you installed Memberstack with the standard Webflow script, the key is handled for you. If you used custom code or the @memberstack/dom package, swap the sandbox public key, which starts with pk_sb_, for your live key, which starts with pk_. Tools like Make or Zapier that use your secret key need the live key too.

Going live, step by step

Live mode needs a paid Memberstack subscription. Sandbox apps stay locked to test mode. You don't need to finish the Custom Domain (DNS) section to go live. That is only for custom domains on social login, SSO or staying logged in across domains.

  1. Upgrade to a paid Memberstack plan.
  2. If you have paid plans, switch the dashboard to Live Mode and follow the prompts to connect Stripe.
  3. In Settings, Application, add your domain under Application Domains and set it to Live Mode.
  4. Add the www version as a separate entry, also set to Live Mode.
  5. Swap in your live API keys anywhere you used custom code or integrations.
  6. Publish your Webflow site to your custom domain, then hard refresh or open it in a private window to check the Test Mode badge is gone.

Before you move on

0 of 5

Tick these off on your own site. Done with all of them? You’re ready for the next lesson.

Up next: Your site is live with email and password logins. Next you’ll add the login options members expect, starting with Google.

Common questions

Why does my Memberstack site still show the Test Mode badge?

Usually because the domain you're visiting isn't listed as Live Mode under Settings, Application, Application Domains. Add both yourdomain.com and www.yourdomain.com, then check in a private window. Sandbox apps without a paid subscription always run in test mode.

Do my test members move to live mode?

No. Test mode and live mode keep separate member data, and members can't be switched between them. Plans, gated content and custom fields do carry over.

Do I need to set up Custom Domain (DNS) to go live?

No. It's optional. You only need it for custom domains on social logins, SSO or keeping members logged in across several domains.

Keep going

Checked against the Memberstack docs

This is v1 of Memberstack University, built from the tutorials we’ve put so much work into over the years. We’d like to make a more organized series.