# Product updates > Follow published Lead Source updates. Read dated release notes for the website, buying guides, pricing tools, and resources available to explore today. Canonical page: https://getleadsource.io/updates/ What’s new at Lead Source ## The details behind each improvement. A dated record of published changes. Each entry explains what changed and where to explore it. These first entries cover the marketing website. [Read the latest updates](https://getleadsource.io/updates/#latest-updates)[Explore the platform](https://getleadsource.io/platform/)[Share feedback](https://getleadsource.io/contact/) October 13, 2026 · Website ### Page-specific answers across the site. Marketing and marketplace pages now include 15 accordion questions tailored to the subject of each page. The answers are available in the page content, and the structured data follows those same questions and answers. The update includes keyboard-friendly accordion controls, page-specific titles and descriptions, and checks across the public sitemaps. Getting Started, API reference, and Support content remain in preparation. [Explore the pricing questions](https://getleadsource.io/pricing/#faq-1)[Explore the feature library](https://getleadsource.io/features/) October 13, 2026 · Website ### A faster, more stable browsing experience. Website fonts are hosted locally, page styles are delivered with the page, and versioned assets can be cached efficiently. The mobile navigation now starts in its intended layout before the menu script runs, reducing movement as the page loads. Accessibility roles and comparison-link contrast were refined. Duplicate index.html addresses redirect to clean page URLs. The existing Pay Per Call animations remain in place. [Visit the homepage](https://getleadsource.io/)[Explore Pay Per Call](https://getleadsource.io/features/pay-per-call/) October 13, 2026 · Buying guides ### More detail for platform comparisons. The comparison library now gives more space to the questions behind a platform decision: workflow fit, account structure, usage assumptions, routing needs, and the tradeoffs that deserve a closer look. Guides cover CallRail, CallScaler, Ringba, CallTrackingMetrics, WhatConverts, Retreaver, and TrackDrive. Use them alongside current provider information and your own requirements when evaluating a change. [Browse all comparisons](https://getleadsource.io/compare/)[Read the CallRail guide](https://getleadsource.io/compare/callrail/) How to read these notes ### Published changes, with their scope attached. - 01 #### Check the category A website improvement describes this public site. It does not imply a new application feature or a change to your account. - 02 #### Follow the detail Each note links to a relevant destination so you can inspect the change in context. - 03 #### Confirm account availability If a future note describes an application capability, review its stated availability and your account requirements. - 04 #### Keep plans separate These notes record completed changes. A request or discussion is not a promise of a release date. Frequently asked questions ### A few more things, explained. Explore the details. Open a question for the answer. What does the Lead Source updates page record? + It records dated, published changes and explains their scope. The initial entries cover the public website, including FAQs, browsing improvements, and comparison guides. Do website updates mean my application account changed? + No. A note labeled Website refers to the marketing site. Application changes should be identified separately, with their own availability and scope. Are these release notes a promise of future features? + No. The page records completed changes. A future request, discussion, or product idea is not a release commitment or a guaranteed date. Where can I inspect the changes mentioned in an update? + Each entry includes links to relevant pages. Follow those links to see the published feature explanation, guide, or website improvement in its current context. What changed in the October 13 FAQ update? + Public marketing and marketplace pages gained page-specific accordion questions and matching structured data. Titles and descriptions were checked alongside the content. Were the withheld documentation pages filled by the FAQ release? + No. Getting Started, API reference, and Support content remained in preparation. The FAQ update did not turn those styled shells into completed documentation. What was the purpose of the mobile navigation update? + The mobile menu now begins in its intended collapsed layout before the script runs. This reduces movement of page content while the site is loading. Did the website performance work remove Pay Per Call animations? + No. The published performance work preserved the Pay Per Call animation code while improving delivery of fonts, styles, and cached assets. Which competitors are covered by the expanded comparison guides? + The library includes CallRail, CallScaler, Ringba, CallTrackingMetrics, WhatConverts, Retreaver, and TrackDrive. Each guide focuses on the relevant workflow and buying considerations. Should I verify competitor pricing after reading an older update? + Yes. An update describes what was published at that time. Provider pricing and terms can change, so use current official information when making a purchase decision. Does a performance improvement guarantee the same score on every visit? + No. Performance varies with device, network, page content, and measurement conditions. The release notes describe the improvements rather than a permanent score guarantee. Can I use these notes to infer an uptime commitment? + No. Release notes are not a service-level agreement. Discuss any required availability or contractual commitment directly with the team. Where should I send feedback about a published update? + Use the Contact page and identify the page or workflow involved. Describe what you expected and what you observed without including private account data or credentials. Will every small wording change receive a separate release note? + Not necessarily. The page highlights meaningful published improvements. Individual corrections and minor wording changes may be grouped with a broader update. How do I distinguish a current guide from an update describing it? + The guide contains the current explanation, while the release note describes the change made on a particular date. Follow the linked guide for the latest page content. Keep exploring [Learning center↗](https://getleadsource.io/learn/)[Customer stories↗](https://getleadsource.io/customers/)[Contact↗](https://getleadsource.io/contact/) Meet your next growth tool ### Help shape the next useful improvement. Tell us where your team needs more clarity, context, or control. [Explore the walkthrough](https://getleadsource.io/demo/)[Explore the platform](https://getleadsource.io/platform/)