Platform updates

​

Webhook replay

• Replay replaces Redeliver on workspace and customer webhook deliveries, and it’s queued instead of sent while you wait. For v1 deliveries sent from this release on, a replay sends the original event again with the same id, created_at, and data, and it’s retried if it fails. Legacy webhooks, and older v1 deliveries, get the lead’s current data, sent once as a new event. Replays are refused while a webhook is paused. See Replaying deliveries.
• Bulk replay re-sends up to 1,000 deliveries at once, filtered by status and the date each event was first sent. It replays only the latest delivery of each event, at 5 per second, and shows its progress above the delivery history.
• The delivery history now says how far back deliveries can be replayed, which is 90 days, or 180 days for deliveries that failed or needed a retry.

​

Webhook payload v1

• New workspace and customer webhooks start on the v1 payload version. Each request wraps data in a fixed envelope with version, id, type, created_at, and tenant_id, and data carries public IDs in place of internal ones.
• Existing webhooks stay on Legacy and keep receiving exactly what they get today. Switch one from its payload version settings, where a preview shows the current payload next to the one after save, and an amber note flags {{ event }} or {{ tenant.* }} fields that would render empty on v1.
• Every v1 event has its own evt_… ID, the same on every delivery attempt, so your receiver can skip duplicates.

​

Lead fields

• New field titles can’t reuse the names Juiced reserves for its own lead data, such as source_id or customer_id. Fields that already use one keep their title and show a warning to rename them. See Adding fields to a lead category.

​

v1 lead API

• Send pings and leads to the new v1 API at /api/v1/ping and /api/v1/leads. Responses use public IDs only, a consistent {data, version} body, and one error format with a stable code for every failure.
• Every v1 response carries an X-Request-Id header. Quote it when contacting support.
• The unversioned /api/ping and /api/leads endpoints are now the deprecated legacy API. They keep working, and their responses now carry Deprecation and Link headers that point to the v1 endpoints. No shutdown date has been set.
• A transaction_id covers both versions, so a retry on the other version never creates a second lead. See Safe retries.
• Legacy lead posts can now reference a ping by its ping_… public ID as well as its UUID.

​

Faster setup, clearer operations

• Start a new lead category from a market-specific template or from scratch. Templates give you a field-set starting point; categories you already created keep their existing fields.
• Filter the Leads page by state or county, including Marketplace and Club tabs, and carry those filters into exports.
• Customer-facing email now uses a shared, tenant-branded layout, including your logo and colors for messages you send to customers, partners, and invitees.

​

Fixes

• Prevent full domains from being entered where a platform subdomain is required during signup or an admin subdomain rename. Existing custom-domain setup is unchanged.

​

AI-assisted diagnostics and Stripe-optional onboarding

• Eligible tenant staff can connect a supported AI assistant to read-only, tenant-scoped diagnostic tools after Juiced enables the Tenant MCP connector for their tenant. The connector can explain lead distribution, buyer misses, bid position, login problems, and custom-domain setup without changing data. See Connect an AI assistant.
• Complete onboarding without connecting Stripe when your operation does not collect customer payments. You can create customers and manage their balances manually; connect Stripe later to enable cards, deposits, auto recharge, and card subscriptions.

​

More control over Club subscriptions

• Let customers apply eligible Stripe promotion codes when they start a new Club subscription. They see the discounted first charge and renewal terms before subscribing.
• Hide a Club tier from new signups while existing subscribers keep their price and allowance, then offer it again or archive it when you are done with it.
• Preview and schedule individual or bulk subscriber moves to an offered tier at the next renewal, without proration. Ineligible subscriptions are identified before confirmation.
• See tier availability and subscriber counts in subscription settings, plus Club access, billing, allowance, and pending-move details on each customer overview.

​

Better buyer controls and source visibility

• Set lead eligibility conditions for each customer, using source, lead type, lead category, and lead-field rules. Juiced applies them during bid selection and round-robin delivery; Marketplace purchases and Club claims are not affected.
• See return rate by source in the source list and source overview, so you can identify traffic that is producing returns.
• Include a customer’s registration URL and selected tracking parameters in webhook payload mappings for customer and subscription events.

​

Cleaner duplicate-check settings

• Find global, customer, and partner-default duplicate-check settings together under Ingest → Duplicate Checks. Existing Lead Delivery links redirect to the customer duplicate-check tab.

​

Fixes

• Process an individual duplicate lead from the React panel, matching the classic panel behavior. Bulk processing remains unchanged.
• Retry top-bid refreshes safely after database lock contention, reducing the chance of stale top-bid data during busy periods.

​

Return settings and lead quotas

• Configure the lead-volume lookback used for return tiers, choose whether customers see their return-tier details, and customize the message shown when tiers are disabled.
• Add daily, weekly, or monthly lead-count and value quotas to sources and partners.
• Show tenant-branded 404 pages with an account-switching action when someone lands in the wrong account or does not have permission.

​

Club subscriptions and claimable leads

• Add Club, a subscription-gated pool where eligible customers can claim available leads without a wallet charge.
• Create Club subscription products and monthly tiers through your connected Stripe account, then give tiers access to Club.
• Route leads into Club through a Distribution Stage or place them there through bulk upload, with a configurable claim cap.

​

Customer management improvements

• Sort customers by wallet balance and filter the customer list by a minimum or maximum balance.

​

Fixes

• Improved handling of duplicate custom-domain updates.
• Prevented duplicate workflow webhooks for the same lead event.

​

Bidding, notifications, and billing

• Add tenant-only below-minimum bid options.
• Add buyer contacts to the Lead Assigned workflow webhook, including mapping support in the webhook UI.
• Include assignment scope and partner public ID in Lead Assigned webhook payloads.
• Add another safeguard against duplicate auto-recharges during rapid lead assignment.
• Expand tenant registration to a configuration-driven billing-country allow-list.

​

API and portal changes

• Breaking: remove the deprecated POST /api/marketplace endpoint. See the API reference for current endpoints.
• Fix partner-dashboard queries that could cause portal timeouts.
• Fix tenant branding uploads on custom domains and subdomains.
• Gracefully redirect Livewire requests that reach a missing page.
• Complete prefixed-public-ID cleanup.

​

Customer and partner experience

• Correct funding status for newly created customers.
• Fix customer login when a user’s first customer account is archived.
• Use postcodes rather than LGAs for Australian county-tier handling.
• Limit partner-portal leads to accepted leads.
• Add a per-tenant setting for the unauthenticated customer-panel landing experience.
• Update Domains & Links labels and customer-panel entry behavior.

​

Data, exports, and observability

• Restore custom lead-detail columns in exports.
• Speed up Incoming Logs.
• Fix webhook configuration test results and authentication headers.
• Prevent stale distribution offers from routing leads to paused customers.
• Guard against duplicate auto-recharges during rapid activity.

​

Delivery and partner reliability

• Track duplicate partner-post responses and preserve explicit price and message paths.
• Continue distribution to other eligible offers when a partner post fails.
• Apply source-based lead-type conditions to ping requests.
• Correct partner eligibility when state and postal-code filters are used.
• Recover stuck reverse auctions and unprocessed buy orders.

​

Operations and onboarding

• Add form-urlencoded partner ping/post support for Leadspedia integrations.
• Add custom date ranges.
• Replace the admin Filament panel with the React admin experience.
• Improve subscription auto-upgrade behavior. See Billing.
• Unlock default lead-category fields for configuration.

• Treat county and country as first-class location field types.
• General cleanup and maintenance.