{
  "slug": "bw-lead-ai",
  "name": "BW Lead Attribution Intelligence",
  "version": "1.10.1",
  "download_url": "https://plugins.bowden.works/wp-content/uploads/plugin-updates/bw-lead-ai-1.10.1.zip",
  "download_hash": "sha256:f2f7330a384b5f130e4bbc16ee583d38298eb291264080673eb11d9bd79d402f",
  "download_size": 534421,
  "requires": "6.0",
  "tested": "",
  "requires_php": "7.4",
  "last_updated": "2026-08-13",
  "homepage": "https://plugins.bowden.works/bw-lead-ai/",
  "author": "Bowden Works",
  "description": "Capture traffic source, attribute it to every lead, and understand where your leads are coming from.",
  "changelog": "## [1.10.1] - 2026-08-13\n\n### Changed\n- **A journey now reads newest-first.** The question in front of somebody opening\n  one is almost always \"what did they just do\", and on a long journey the answer\n  was at the bottom of the page. Visits are listed most recent first, and so are\n  the events inside each visit.\n\n### Fixed\n- **The times column could run backwards.** An enquiry was positioned by the last\n  thing the browser had told us about before it, while being *labelled* with the\n  time it actually happened — and those are not the same instant. Anything the\n  browser reported after the fact, such as a form-start that fired before the\n  submission but arrived after it, then appeared below a row showing an earlier\n  time. A journey read 10:38, 10:40, 10:38, 10:40 and the order of events was\n  impossible to follow.\n\n  It is now positioned by the same clock it is labelled with. Which visit an\n  enquiry belongs to is unchanged — still decided without comparing the visitor's\n  clock to the server's — and the position is bounded so an enquiry cannot be\n  pushed out of its own visit by a device whose clock is wrong."
}