Skip to content

Changelog

Track every update, feature, and improvement we ship. We release frequently to keep your lead operations ahead of the curve.

v6.25.0 — October 20, 2026

Redistribute past a buyer's schedule or caps, build a tracker before you have a traffic source, and accuracy fixes across ingest, exports and lead validation.

New Features

  • Redistribute past a schedule or a cap. Two switches in the Redistribute drawer send a lead to a buyer its schedule or its caps would normally block. Skip caps covers volume, budget and conditional caps, and the sale is still charged, so the buyer's counters overflow on purpose. Both overrides are recorded in the Activity Log.

Improvements

  • A clearer Redistribute drawer. Select all becomes a menu of tickable groups: ready, never tried, out of schedule, over a cap, and earlier hard rejects. A blocked buyer gets a row action that turns on just the switches it needs.

  • Build a tracker before you have a traffic source. The SDK snippet arrives as soon as you pick a campaign, since the SDK reads it from the visitor's landing page anyway. A Direct Tracking URL previews with the gap highlighted, and the copy button stays off while the link is incomplete.

  • An error screen instead of a blank page. A crash now offers reload, a way back to the dashboard, and copyable details.

Fixes

  • Leads from click tracking links and the SDK are no longer rejected when the campaign types traffic source as a number

  • A traffic source is credited only within the lead's own campaign

  • A Zip Code or Phone field named anything other than zip or phone is now checked against the lead's country, in ingest and when you edit a lead

  • An export combining a search term with rejection columns completes instead of failing

  • The affiliate and sub source dropdowns load on large accounts rather than timing out

  • A traffic source with no channel no longer breaks the Tracker Builder or the campaign cloner

v6.24.0 — October 14, 2026

Return a lead or confirm a CPA sale from the Leads list, date your money by sale time or ingest time, and see pending and declined revenue beside confirmed.

New Features

  • Return or confirm a lead from the Leads list. Record a return or a CPA confirmation yourself, on one lead or many, without waiting on a buyer's postback or preparing a Returns upload. A drawer reviews the change lead by lead first, the money moves with the status, and nothing is sent to a partner's tracker.

  • Sale time or ingest time. A switch dates lead money either by when the lead arrived or by when it sold, so you can ask what Tuesday's traffic earned or what you invoiced in October. It applies across roles and buyer scoped lists.

  • Pending and declined money. Revenue that has not settled is reported beside confirmed, with total pending revenue in the admin summary and the overview cards.

  • Clone a postback. Copy a config with its triggers, scopes and rules instead of rebuilding it.

  • Not Selected. A buyer that lost the lead to another buyer reads as Not Selected rather than borrowing someone else's outcome.

Improvements

  • Resend mapping. Mapping rows take postback tokens and transformers, and a buyer is announced by its company name with nothing to configure.

  • Integration mapping rows. Pick the lead field and the transformer from inside the row, and leaving a settings screen with unsaved changes asks first.

  • Postback v1 removed. One postback screen rather than two.

  • Invoices. An invoice that will not open tells you why, and its link is fetched fresh when you click it.

Fixes

  • A buyer that holds nothing on a lead is no longer told another buyer holds it

  • Buyers are named consistently as company, alias and id

v6.23.0 — October 5, 2026

Pricing rules that can judge a buyer's own response, lead events dispatched to Resend, a response timing waterfall on every lead, and an app that stops going white between pages.

New Features

  • Pricing rules. Decide what a buyer pays using conditions and tiers, and condition on the values the buyer itself returned in its ping or post response. A tier's revenue can be a field's value, a percentage of it, or a rate per unit, and its source payout travels with the price. A buyer is priced provisionally at filter time, then priced again once it answers, and the lead timeline names the rule and tier that set the price.

  • Resend event dispatcher. A new integration that keeps the consumer in sync as a Resend contact and dispatches a named event once the lead settles, so your own Resend Automation sends the email. Four outcomes are covered, each contact property maps from a lead field or fixed text, and a lead still pending is re-checked every hour for up to 48 hours.

  • Response timing on every lead. A waterfall drawn to scale, with distribution, integrations and each buyer's ping and post calls on one timeline, so a slow buyer is obvious at a glance.

  • Select every matching lead. Select everything matching your filters at once, with a confirmation that names the real count on every delete, and exports that honour your selection.

Improvements

  • A steadier app. The page you are on stays visible while the next one loads, and a page whose code fails to arrive reloads itself rather than going white.

  • Faster analytics. The supplier summary cards, the admin summary and the lead scan return noticeably faster on large accounts.

  • You stay signed in. A brief network failure during a background token refresh no longer signs you out, and ending an impersonation returns you to your own account.

  • Integration field mapping checks itself. A row can send fixed text, a row that would send nothing is refused, and any table that maps a field warns when that field does not exist.

  • Identifiers in filters and search. Filter and search on an external id or a UUID and get the lead you meant, and lead search is faster on large accounts.

Fixes

  • An offer tracking link with a malformed id returns not found instead of crashing

  • Generated tracker and SDK links keep the https prefix

  • A bulk delete that failed no longer reports success

  • A remembered date range is no longer overwritten by the default on arrival

  • A branding change takes effect without the old branding staying cached

  • An unreachable Resend service is reported as unreachable, not as a bad API key

v6.22.0 — September 28, 2026

The Ruleset Engine is on for every account, number and boolean transformers send real JSON types, and rejection insights name the condition that decided.

New Features

  • Ruleset Engine for every account. The rebuilt filter system now runs on every account. One ruleset combines AND and OR conditions in a first match wins chain, with a guided editor, a lead tester, a template and shared rule library, version history, saved value lists, and Rule Health that flags rules that can never match. Existing filters were converted, and rejection reasons and analytics read the same as before.

Improvements

  • Number and boolean transformers. Output number and output bool now send real JSON numbers and booleans in ping and post bodies, so a buyer that validates types strictly no longer rejects the payload.

  • Rejection insights name the deciding condition. When a group of conditions rejects a lead, the rejection names the condition that decided it, not one it outweighed. Earlier ruleset rejections were backfilled to match.

Fixes

  • A single day picked on the calendar covers the whole day

  • A click conversion is no longer written to the ledger twice

  • A second buyer can no longer take a lead another buyer already holds

  • The payout quoted to a source is capped at two decimal places