> ## 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. # Maximizing app engagement: your strategy guide > Keep your company's app active with fresh content, a useful home screen, training, targeted announcements and daily, weekly and monthly routines. Turn your company's app into a place your reps open every day. Whether you're managing content, watching results or building community, this guide helps you create an app experience that keeps people coming back. ## Build your engagement foundation Engagement starts with compelling content and a clear design. Your app needs regular care to stay useful. ### Keep your content fresh Your content library drives engagement. Keep it fresh in three ways: **1. Refresh regularly** * Review your content every week. * Remove outdated material promptly. * Highlight new products. **2. Organize it** * Create clear categories. * Build targeted playlists. * Tag content so it's easy to find. * Feature your most popular items. **3. Share success stories** Nothing drives engagement like real results from real people. Feature your reps' and customers' genuine stories, with their permission. ### Think mobile first Your app should feel like a personal assistant in every rep's pocket, not a scaled-down website. Build the Home screen in the admin's [Home Tabs](/help/admin/mobile/home) from widgets that put the most-used tools up front: | Feature | Purpose | Result | | - | - | - | | **Quick Links** widget | One-tap access to key screens | Less friction | | [Announcements](/help/admin/announcements) with push notifications | Targeted updates | More engagement | | Announcements for specific countries or ranks | Content that fits the reader | More relevance | Test your app on different devices and screen sizes. What looks right on your phone might need adjusting on others. ## Track and improve engagement Your numbers show what's working. ### Daily signs to watch Check these every morning: * How many reps are active. The **Field** tab of the admin's [Home](/help/admin/home) dashboard shows reps active yesterday and this month. * How much reps share * When the app is busiest * How much your team communicates * How often customers interact with reps These numbers are your app's pulse. They tell you whether your engagement strategy is working. ## Training and development A good training program is built in layers, from a strong foundation up. ### Map the learning journey | Stage | Focus | Outcome | | - | - | - | | Onboarding | Platform basics | Confident navigation | | Core skills | Essential features | Daily tasks mastered | | Advanced | Strategic tools | Business growth | | Leadership | Mentoring others | Community building | ### Build your resource library Make your training as dynamic as your platform. Include: **Quick guides:** * Feature walkthroughs * Task checklists * Tips and tricks * Troubleshooting guides **In-depth content.** The best training explains why something matters, not just what to do. Real success stories make training more engaging. ### Learn by doing 1. **Live demonstrations** * Show real-world uses. * Address common challenges. * Share insider tips. 2. **Practice sessions** * A safe place to experiment * Immediate feedback * Learning from peers 3. **Success workshops** * Share winning strategies. * Discuss real examples. * Build best practices. Record your live training sessions. They add to your resource library and help people who couldn't attend. ## Key engagement features ### MySite Help reps turn their MySite into a sales tool: * Guide their theme choices. * Encourage regular updates. * Showcase the right products. * Track how well it captures leads. ### Contacts Help reps build relationships at scale: * Import and organize their contacts. * Follow what contacts engage with. * Set follow-up tasks. * Keep nurturing relationships. ### Announcements [Announcements](/help/admin/announcements) can go to everyone, or only to certain countries or ranks, and you can send a push notification about each one. For a team or one person, use [Messaging](/help/admin/messages) instead. | Audience | Best for | How often | | - | - | - | | Everyone | Major updates | Monthly | | A country or region | Local events | Weekly | | A rank | Recognition and rank-specific news | As achieved | | A team or one person | Coaching | As needed | ### Shopping experience Make buying easy: * Feature products strategically. * Promote current offers. * Keep checkout smooth. * Follow up on abandoned carts. See [Cart abandonment](/help/playbook/optimizing-your-cart-abandonment-strategy). * Watch what people buy. ## Keep the home screen working The Home screen is mission control for engagement. Useful widgets in [Home Tabs](/help/admin/mobile/home) include: * **Quick Links**, for one-tap access to key screens * **Analytics**, showing each rep's visitors, views and shares * **Calendar**, for upcoming events * **Leaderboard**, ranking reps by shares, order volume or web traffic * **Catchup** and **To-Do List**, for each rep's follow-ups Refresh it regularly: * Update your announcements. * Feature upcoming events. * Spotlight achievements. ## Communicate well Great communication is the heartbeat of engagement. Build it in layers: 1. Essential communications that everyone needs 2. Regular engagement 3. Feature updates 4. Targeted announcements ### Choose the right channel | Channel | Best for | Timing | | - | - | - | | Push notifications | Urgent updates | Immediately | | In-app announcements | Feature and company news | While people use the app | | Email | Detailed information | At planned times | | Chat | Personal conversations | In real time | ### Keep your community informed * Share platform updates promptly. * Announce new features with clear benefits. * Highlight results. * Recognize achievements regularly. * Give constructive feedback. ## Build a rhythm Different tasks need different rhythms. ### Every day **Morning:** * Check recent activity. * Handle urgent follow-ups. * Review your key numbers. **Midday:** * Add fresh content. * Reply to messages. * Watch your results. **End of day:** * Plan tomorrow's content. * Schedule announcements. * Note your wins. ### Every week | Day | Focus | Actions | | - | - | - | | Monday | Strategy | Review results, plan content | | Tuesday | Content | Refresh featured items | | Wednesday | Community | Share leaderboard highlights | | Thursday | Growth | Plan upcoming events | | Friday | Celebration | Share success stories | ### Every month 1. **Content** * Review your whole library. * Archive outdated content. * Plan next month's themes. * Review engagement. 2. **Performance review.** Look for the stories behind your numbers, not just the numbers. ### Every quarter 1. **Strategy review** * Look at long-term trends. * Find growth opportunities. * Plan major updates. 2. **App improvements** * Roll out new features. * Improve existing tools. * Refresh training materials. 3. **Community building** * Celebrate the quarter's wins. * Recognize top performers. * Launch new initiatives. Try spending 20 minutes each morning reviewing contact engagement and planning follow-ups. ## Run a sharing contest Contests can drive app adoption and growth. ### Set it up | Part | Details | Result | | - | - | - | | Goals | Clear, measurable goals | Focused effort | | Timeframe | Weekly, monthly or quarterly | Sustained engagement | | Tracking | Shares and engagement | Measurable results | | Lead generation | New contacts | Business growth | | Conversion | Sales from shares | Return on investment | ### Write clear rules * Who can take part * Minimum shares * Which content counts * How results are verified * What the prizes are ### Keep it exciting * Post leaderboard updates. The **Leaderboard** widget can rank reps by shares. * Highlight successful sharing strategies. * Celebrate milestones. * Share progress regularly. * Share examples of what works. Consistent communication and recognition keep excitement high. ### Recognize and reward 1. **Right away** * Announce winners promptly. * Share their stories. * Deliver prizes quickly. 2. **Over time** * Recognize more than one category. * Write down what worked. * Turn it into a playbook for next time. ## Business tools ### SmartLinks * Encourage reps to share with SmartLinks. * See who engages. * Watch which shares lead to orders. * Improve your landing pages. * Share what works. ### Analytics * Review your results regularly. * Share insights with your team. * Find growth opportunities. * Measure the return on your initiatives. * Watch how many reps use the app. App engagement comes from steady attention to what your users need, and regular improvements based on results. ## Your path forward Engagement works like a flywheel: better features lead to more use, more use brings more feedback, and feedback leads to better results. ### Your next steps 1. **Start small, think big** * Choose one area to improve first. * Measure where you are now. * Make improvements step by step. * Write down what works. 2. **Build momentum** | Week | Focus | Goal | | - | - | - | | 1 | Review | Find opportunities | | 2 | Plan | Create action items | | 3 | Act | Make the changes | | 4 | Measure | Check the results | 3. **Scale what works** * Share wins with your team. * Document best practices. * Train others on what works. * Repeat and refine. The most successful apps aren't built in a day. Focus on steady progress over perfection. ## Frequently asked questions The targets below are examples. Set your own from your starting numbers. **User activity** | Metric | What to track | Example target | | - | - | - | | Active users | Reps active each day and month | Up 5% a month | | Shares | How often reps share content | 3 to 5 shares per rep | | Busy times | When people use the app | Use them to schedule posts | **Team performance** | Metric | What to track | Example target | | - | - | - | | Team activity | How much your team communicates | Most of the team taking part | | Customer engagement | How often customers reply | A rising response rate | | Response time | How fast you answer | Within a couple of hours | | Follow-ups | Relationship building | Several touches a week | **Business impact** | Metric | Purpose | How often to review | | - | - | - | | Conversion rate | Sales effectiveness | Daily | | New leads | Growth | Weekly | | Return on investment | Program value | Monthly | | App adoption | Platform success | Monthly | Focus on numbers that lead to action. Every metric should point to something you can improve. The admin's [Home](/help/admin/home) dashboard shows revenue and rep activity, and each rep's **Analytics** widget shows their visitors, views and shares. See [Daily signs to watch](#daily-signs-to-watch). ## Related pages * [Home Tabs](/help/admin/mobile/home) * [Announcements](/help/admin/announcements) * [Home](/help/admin/home) * [App design essentials](/help/playbook/essential-elements-for-successful-app-design) * [Push notifications vs SMS](/help/playbook/push-notifications-vs-sms-mastering-multi-channel-communication) ## 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.