{
  "slug": "bw-lead-ai",
  "name": "BW Lead Attribution Intelligence",
  "version": "1.9.0",
  "download_url": "https://plugins.bowden.works/wp-content/uploads/plugin-updates/bw-lead-ai-1.9.0.zip",
  "download_hash": "sha256:83cb4007f5cae4fab6ddd6dc5b045ceaef09468d2340774db020039f0520eca2",
  "download_size": 528432,
  "requires": "6.0",
  "tested": "",
  "requires_php": "7.4",
  "last_updated": "2026-08-12",
  "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.9.0] - 2026-08-12\n\n### Added\n- **One person is one lead, however many times they enquire.** A second enquiry\n  from the same browser now joins the journey they already have instead of\n  starting a new one. Somebody using a contact form to ask three follow-up\n  questions has not been won four times, and counting them that way was\n  inflating both the lead total and the channels that happened to bring them\n  back.\n\n  **Credit does not move.** It stays with the first enquiry and what led to it —\n  how they originally found the site, and the source of the visit they first\n  enquired on. Everything after that is recorded and shown on their journey and\n  takes no credit, because it did not win the lead. Without that rule a visitor\n  who returned through an ad and sent a second message would hand that ad a lead\n  it played no part in, which is the exact failure this plugin exists to prevent.\n\n  Every enquiry appears on the journey in its place, each with its own form name\n  and time, so the follow-ups are still there to read — they are simply not\n  counted as acquisitions.\n\n  **Links already handed out keep working.** A journey link is written into a\n  CRM record the moment somebody converts, and those outlive everything else\n  here, so the joined submission's link still opens the journey it became part\n  of rather than breaking.\n\n  This applies whatever the update setting says, including \"Never — keep it\n  exactly as it was saved\". Whether a saved journey's *browsing history* keeps\n  being rewritten and whether a second enquiry attaches to the person who made\n  it are two different questions, and that setting only ever answered the first.\n  A snapshot journey still keeps its frozen pageviews; it now also knows they\n  came back.\n\n### Changed\n- **Sites set to \"Never update a saved journey\" now set the same first-party\n  cookie the other two settings do.** It is what lets a second enquiry be\n  recognised as the same person. Nothing else about that setting changed — the\n  browser is still never asked to report a pageview, so it still costs nothing\n  per page.\n\n- Two pieces of copy on the Journey Storage tab were describing the old\n  behaviour and are corrected: the \"Never\" option no longer says a resubmit\n  gives you a second separate journey, and the section now states the credit\n  rule up front rather than leaving it to be inferred from a report."
}