> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Elevating customer experience in e-commerce > Build support, personalization, mobile and content experiences that keep customers coming back, and measure what matters. Customers expect a smooth, personal experience at every step. This guide shows how to build one with Fluid, from support to content, and how to measure it. ## Build your foundation Like a well-designed building, a great customer experience needs solid foundations, thoughtful design and regular maintenance. ### Make support easy to reach Support is where customer relationships are won or lost. A well-run support setup turns problems into chances to build loyalty. Add a chat button to your store in the admin, under **Settings** › [Floating Action Buttons](/help/admin/settings/floating-action-buttons). The button opens a short form, so: * Write a welcoming form title and description. * Set the button text and the message people see after they send. * Match the button's colors to your brand. Then answer quickly. Reps can also be reminded about unanswered messages: if your company turns on the **Unresolved WebChat** catchup in [Catchups](/help/admin/settings/catch-ups), reps get a reminder in the mobile app about web chat messages to them that are still waiting for a reply. ### Make a great first impression Pop-ups and banners can guide visitors toward meaningful engagement without getting in their way. They should feel like a warm, well-timed handshake. **Craft your message:** * Write headlines that speak to what visitors need. * Time them so they feel natural. * Test and refine your approach. **Use them for:** * Time-sensitive promotions * Category highlights * Trust signals * Personal recommendations ## Personalization that converts One size fits nobody. Great customer experience comes from understanding each person and responding to what they need. ### Know your contacts Every interaction is an opportunity. In the admin's [Contacts](/help/admin/contacts) screen, each contact has a status, such as **New** or **Cold**, and a rep. Use them to send the right message at the right time: * **New:** fresh leads, ready for a first message * **Cold:** contacts who need re-engaging. See [Warming up cold leads](/help/playbook/warming-up-cold-leads). Assign each contact to the rep best placed to help, and keep the assignment up to date. ### Mobile first: meet customers where they are Mobile is now the main channel for many customers. Your app should feel like a personal concierge, not a scaled-down website. Set up your company's app in the admin's [Mobile App](/help/admin/mobile) screens. Make sure it has: * Product catalogs with an easy checkout * One-tap access to common tasks * Events, training and team updates * Offers and recommendations that fit each person ## Content that captivates Content is the currency of digital engagement. Manage your images, videos and documents in the admin's [Media](/help/admin/media) screen. ### Look great on every screen Use sharp images, and check how each one looks wherever it appears, on large screens and on phones. ### Build pages that convert Build pages that guide visitors naturally toward action, in the admin's [Pages](/help/admin/pages) screen. High-converting pages have: 1. Compelling headlines 2. A clear value proposition 3. Well-placed calls to action 4. Social proof that builds trust 5. A layout that works on phones ### Extend your reach on social media * Encourage reps to share their MySite and playlists. * Share transformation stories. * Celebrate customer successes. * Build community through engagement. ## Measure what matters The admin's [Home](/help/admin/home) dashboard shows revenue, orders by type, sales channels, subscriptions and live visitors. Measure the rest with the tools you already use. A useful rhythm: **In real time:** * Website traffic * Completed checkouts * Support response times **Weekly:** * Conversion rates * Return visits * Satisfaction scores **Monthly:** * Customer lifetime value * Cost to acquire a customer * Brand loyalty **Quarterly:** * Process reviews * Business reviews * Strategy alignment ## Your roadmap Great customer experience comes from steady, step-by-step work. **Foundation:** * Set up your core systems. * Configure the basic tools. * Record your starting metrics. **Growth:** * Add engagement tools. * Smooth out the paths customers take. * Start personalizing. **Excellence:** * Refine based on data. * Scale what works. * Keep innovating. ## Best practices ### Put customers first * Set up clear notifications. * Follow up automatically where you can. * Offer more than one way to get support. * Track customer interactions. * Monitor engagement. ### Keep your technology current * Keep admin access up to date. * Keep your payment gateways current. * Watch how your systems perform. * Review your security settings. Every improvement in customer experience affects your bottom line. Start with high-impact, low-effort changes, and build from there. Track these measures of success: * Customer satisfaction * Net Promoter Score (NPS) * How many carts become orders * How many customers come back to buy again ## Frequently asked questions **Set up chat** In the admin, under **Settings** › [Floating Action Buttons](/help/admin/settings/floating-action-buttons), turn on the chat button and fill in its form: **Form Title**, **Form Description**, **Button Text** and **Success Text**. Keep the form short, set clear expectations for when you'll reply, and match the button to your brand colors. **Plan support levels** | Level | Who handles it | Best for | Response target | | - | - | - | - | | 1 | Self-service, such as FAQs or an AI assistant | Basic questions, product information, order status | Immediate | | 2 | Your support team | Complex issues, custom requests, technical help | Within minutes | | 3 | Specialists | Strategic support, key accounts, escalations | Within hours | **Cover after-hours requests** | Situation | Automatic reply | Follow-up | | - | - | - | | Evenings | "We'll reply by \[time]" | Priority the next day | | Weekends | A note about weekend coverage | Reviewed Monday morning | | Holidays | Your holiday schedule | Confirm your return date | | Technical issues | Status updates | Let people know when it's fixed | Always offer a clear path to a person, even in automated replies. See [Make support easy to reach](#make-support-easy-to-reach). ## Related pages * [Floating Action Buttons](/help/admin/settings/floating-action-buttons) * [Contacts](/help/admin/contacts) * [Mobile App](/help/admin/mobile) * [Home](/help/admin/home) * [Landing pages](/help/playbook/landing-page-conversion-best-practices) ## Get help Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.