Skip to main content

Week of October 12, 2026

A big week for plans, billing and integrations. Partner packages for Mews, Shopify, Square, Toast and Printful install from the dashboard, and members can now refer friends with a referral code. Each plan has clear limits, webhooks and single sign-on became add-ons, and billing now follows your plan from sign-up through to a lapsed payment. For integrators, every API error now shares one format with a request id you can quote to support, and list endpoints accept at most 100 rows per page.

Highlights​

Partner packages in the dashboard​

Organization > Packages lists industry and partner packages with their state, and you can search and filter them. Preview an install as a dry run to see every record it will create, then install. A partner install sets up an identifier type, a role with only the scopes it needs, an API client and, for Shopify, a webhook source that turns paid orders into retail-purchase events. Copy the API key before you close the dialog, as it's shown once. In the API, use /package-installations. Learn more

Referral codes​

Call POST /customers/{customerId}/programs/{customerProgramId}/referrals to get a member's code, and pass referralCode to POST /customers to enroll a friend with it. Each referral sends a referral.referrer and a referral.referee event, so a rule can reward either side. In the Hub, the Customer 360 Membership tab shows each code with a copy button, who referred the customer and how many customers enrolled with it.

Plan limits and add-ons​

Each plan now has limits on published segments, sync event types and included events per month. Trial organizations that go over their events get 429 with PLAN_EVENT_CAP_EXCEEDED until the next UTC month, while paid plans are billed for overage and never blocked. Webhooks are included with Tailored Fit and Custom Fit and are a $250/mo add-on for Ready Fit. Single sign-on and domain verification are one $150/mo add-on, and Turnkey is billed in the dashboard at $95/mo or $1,026/yr. Learn more

Billing from sign-up to renewal​

New organizations pick a plan and accept Loom's agreements when they sign up, and Loom can create an organization for you and invite its owner, who goes through checkout on the agreed terms at first sign-in. When an agreement changes, organization admins are asked to accept it again before they continue; in the API, use POST /organizations/{id}/agreements/accept. You get an email before a trial ends and when a payment fails. When billing lapses, write requests return 402 with PAYMENT_REQUIRED, while reads, billing and rewards portal requests keep working. Learn more

API errors and page sizes​

Every API error is now one body with a stable code, a safe message and a requestId, and the same id comes back in the X-Request-Id header on every response. The success and errors members stay, so existing clients keep working, and MCP tool errors carry the same code as the REST API. Statuses are more precise too: 409 for a state conflict or duplicate key, 404 for a missing record, 403 when a signed-in caller lacks a scope and 502 for an upstream failure. The dashboard, Hub and rewards portal read the code, show each field error under its field and give you a support reference to copy. Learn more

{
  "success": false,
  "code": "DUPLICATE_RESOURCE",
  "message": "A resource with this key already exists.",
  "requestId": "req_123",
  "errors": [{ "message": "A resource with this key already exists." }]
}

List endpoints now accept at most 100 rows per page. A larger size, pageSize or webhook limit returns 400 instead of being accepted or silently capped, so lower the page size and walk the pages. In the dashboard, tables page on the server with a Rows per page picker, and pickers, filters and searches reach every row, not only the first page. Learn more

Also this week​

New​

  • Rewards portal custom domains. The portal details sheet shows the CNAME to add and verifies it with Verify DNS.
  • Devices. Organization > Devices lists your devices, and Release removes one and revokes its credential. Learn more
  • Slack. Install the bot for each environment and link your Slack account from Developers in the dashboard.
  • Metadata types linked to a data model. A metadata type can name a custom data model, its values are validated against it, and the Hub has a Data model picker for it.
  • Customer billing meters. Organizations billed on customers see customers and active customers in billing usage.
  • Scheduled exports. Scheduled Saved View exports to SFTP are available to organizations Loom has enabled.
  • Event list with custom fields. GET /{entityType}/{entityId}/events accepts includeEventData=true.
  • Billing plans endpoint. GET /billing/plans returns each plan's price, features and event limit.
  • Status page. status.loomloyalty.com shows uptime and incidents for the API, MCP server and AI assistant.
  • Audience templates. The rule-based audience builder offers templates and a live count for each condition.
  • Daily AI limit notice. Chat and the AI generators say when your daily AI limit resets.
  • Go-live readiness. The dashboard Home page and the Hub onboarding quest show whether your organization is ready to go live.
  • Onboarding quest for Turnkey. Organizations on the Turnkey plan now get the Hub onboarding quest.
  • Whole-organization export. You can export your organization's data, including its program configuration, in one export.
  • Organization deletion request. The owner of a cancelled organization can schedule its deletion, withdraw the request or transfer ownership.
  • treadle CLI. The command-line tool is now run as treadle instead of loom, and treadle plan and treadle apply support tenant manifests and promoting configuration between environments with --env.
  • Analytics answers in Slack. The Slack bot answers ranking and trend questions, such as "top 10 customers by points", for users who can see analytics.

Improved​

  • Audit log. Rows name the target and the actor, and the actor filter adds AI assistant and Customer.
  • Analytics and navigation. Analytics lives in the Hub, and the Hub sidebar groups pages into Engage, Data, Insights and Changes.
  • Weave AI chat. The chat sheet is rebuilt to match the rest of the app. Learn more
  • Billing usage. Only production environments count toward event usage. Learn more
  • Webhooks in the dashboard. Paused endpoints stay visible as read-only, and the dashboard links to the add-on or an upgrade. Learn more
  • Hub onboarding. Skipped steps count toward Full Loom, and each onboarding step pays once.
  • Reserved event namespace. Event type codes under webhook.push. are reserved and return 400.
  • Wallet pass security. Apple wallet device requests must carry the pass's own authentication token.
  • MCP create_customer. The tool describes your customer data model, including custom fields.
  • Look and feel. Menus, dialogs, status pills, tables and the SSO, security and Slack widgets share a refreshed style with AA-compliant badge colors.
  • Slack across environments. You can install, link or remove Slack for any environment of your organization from your current dashboard session.
  • Trace retention. Flow snapshot payloads are cleared 7 days after an execution ends, traces are deleted after 60 days, and a rule's trace turns off 24 hours after it's enabled.

Fixed​

  • Partner webhooks. Webhooks from partners such as Shopify, Mews and Printful are accepted again.
  • Webhook delivery. event.added is delivered when a rule issues a badge or external offer, and only failed events are reported as failed.
  • Sign-in. The Hub no longer signs you out every few minutes, loops through sign-in or lands on the sign-in page after a refresh, and valid tokens are no longer rejected when the identity provider is slow.
  • Lists past 10 items. API keys, roles and scopes all load, not only the first 10.
  • Billing page. Trial, period and renewal dates show, usage no longer reads 0 events, and trials without a card are set up correctly.
  • Event rules. Editing a rule keeps its code, publish and pause act on the current version, and enablement is checked in the event's environment.
  • Data models. Published models show in the Hub, API keys see new versions straight away, and models built on a parent such as metadata save.
  • Events and segments. POST /events accepts plain line items, and segments built on customer fields such as birthDate run.
  • Organization and users. Admins can save their organization, invite with real roles and reach the SSO, Domains and Slack pages.
  • Metadata across organizations. Metadata groups and items are no longer served from one organization to another.
  • Sign-up. Sign-up no longer refuses organizations when the security check can't load.
  • Tenant manifests. treadle plan and treadle apply manage metadata correctly.
  • Onboarding quest on phones. Tapping the quest card in the sidebar drawer opens the quest panel fully on screen.