What changed and when. Fixes are listed next to features, including the ones that were our fault — a changelog that only announces wins is not much use for judging whether a product is looked after.
Setup now starts by asking where your store runs, with real instructions for Shopify, WooCommerce, Wix, Squarespace, BigCommerce, Webflow, any site you can paste a script into, and a server-side API for reporting from your own backend. Each has its own guide, including an honest account of what that method cannot see.
Reporting a sale now requires the order's own id as well as its value. That is what makes a repeated call — a refreshed confirmation page, a retried webhook — land as the same sale rather than a second one. Signup and lead campaigns are unchanged, since they often have no id to give.
On a site using our script, a conversion call could throw for any visitor who had not arrived from a creator's link — which was most of them. It was invisible in testing, because you test by clicking the link. The script now always defines itself and quietly does nothing for visitors nobody referred.
Our own documentation promised a first-party cookie lasting 30 days. The code was using browser storage with no expiry at all. It now writes the cookie it described, and clears the old unbounded value from any browser still holding one.
Reports have a Download button. The PDF is rendered from the same page you see, so the figures cannot drift, and it comes out as one A4 sheet. A white-labelled report downloads with your branding and none of ours.
The accent you set in Settings now appears on the report itself — a hairline rule under your logo and a tint on the section labels. Deliberately restrained, and the result chip stays red, amber or green whatever you pick, because that colour means something.
Terms, Privacy, the DPA, the Cookie Notice and the Refund Policy gained contents lists and anchored clauses, and the gaps were filled — intellectual property, confidentiality, indemnity, an itemised cookie table, chargebacks, and what happens to your data after you cancel. Still in draft pending review by a solicitor, which the banner on each says.
Agencies get an /account screen separate from client settings, so your own name, plan and billing live in one place rather than once per client.
A logo that was too large or the wrong shape used to be rejected, often twice in a row. It is now resized and re-encoded for you, and we tell you what we did to it.
Conversions took the campaign's currency rather than the order's, so a €90 order on a GBP campaign was stored as £90 — a 15% overstatement invented at the point of entry. The order's own currency is now authoritative, and an unrecognised code is rejected rather than quietly swapped.
On the Growth plan with your logo uploaded, Yonto branding now comes off the report entirely — on screen and in print. Previously the mark stayed in the masthead even when the footer link had gone.
Serverless functions now run in London beside the database, the dashboard streams its slowest section instead of blocking on it, and the framework was updated to close nine dependency advisories.
A refunded Shopify order used to stay in your ROAS forever. Refunds now arrive as their own entries with a negative value, so the sale and the refund both remain visible and the net figure is defensible. Four sales with one refunded reads as exactly that, rather than as three sales.
Reports lead with a sentence rather than a 104px number. A merchant opening a forwarded link wants one question answered, and a ratio is not an answer.
Yonto is built by two people in London and ships most weeks. If something here broke for you, or you want to know whether a change affects your setup, email us.