From “Welcome, User” to“Welcome Back, Sarah — You're 80% Complete”

If a custom field is empty, the element shows your fallback text (the placeholder you define in Webflow). This ensures your layout never breaks if data is missing and that logged-out visitors still see something sensible. For example, `

Yes. You can store JSON in a custom field and then use MemberScripts (our free code snippets library) or your own JavaScript to parse and render it. This is useful for complex data like quiz results, multi-step forms, or nested analytics. For example, you might store quiz answers as JSON and then render a custom “results” section on a member dashboard.

Use the JavaScript API to update custom fields or JSON whenever events occur in your app or course. For example, when a lesson is completed you can call something like `$memberstackDom.updateMemberJSON({ json: { lessonsCompleted: 12 } });` and then display that value anywhere on your site with `data-ms-member="lessonsCompleted"`.

No. Personalized content only displays for logged-in members whose identity and data Memberstack can access. Logged-out visitors see your fallback content (the default text or design you added in Webflow), so your pages still look complete without exposing any private data.

Yes. You can combine multiple conditions inside a single data-ms-content attribute, including plan level, subscription status, and custom fields. This supports AND/OR-style logic like `data-ms-content="plan:pro,status:active"` to show content only for active Pro members. You can also invert conditions (e.g. `!status:trialing`) to hide or show content for specific segments.

Minimal. Personalized content adds only a small amount of overhead on top of your existing Webflow site. Member data is fetched and cached client-side, and we’ve tested with sites serving 100K+ members without noticeable slowdowns. In most cases, you’ll see well under 50ms of additional load time per page.