Xpnsr ships weekly. This changelog covers all releases across Expense (real-time spend tracking, virtual cards, QuickBooks/Xero sync), CBN (AI content generation, keyword clustering, satellite domain management, SERP alerts), and Tracker (S2S postback, bot shield, A/B testing, geo-targeting, cohort analysis). Each release is tagged with version number and category — New, Improvement, or Fix.
Xpnsr Changelog — Product Updates, Improvements & Bug Fixes
The Xpnsr Changelog documents every update, improvement, and bug fix across all three products — Expense, CBN (Content-Based Network), and Tracker. We maintain a transparent development process and publish detailed release notes for every change that affects the user experience. Each entry includes the date of release, the product affected, a description of the change, and the type of change — whether it is a new feature, an improvement, a bug fix, or a performance optimization. The changelog is updated in real time as changes are deployed to production, and each entry is tagged with the relevant product so you can filter updates by the products you use.
Expense Product Updates
Expense is Xpnsr's real-time corporate card management platform that connects to Visa and Mastercard networks via the Astrada API. Recent updates to Expense have included support for virtual card issuance with spending limits per merchant category, real-time transaction enrichment with merchant logos and category tags, QuickBooks Online and Xero integration with automatic transaction matching, multi-currency support for USD, EUR, and GBP card accounts, role-based access control with Admin, Viewer, and Cardholder roles, and a redesigned transaction feed with inline receipt capture via mobile camera. The Expense team releases updates on a bi-weekly cadence, with hotfixes deployed as needed for critical issues. Each release is tested against a comprehensive suite of integration tests that simulate card transactions through the Astrada API pipeline, ensuring that new features do not break existing functionality. Performance benchmarks are tracked for each release, with the current p99 latency for transaction capture at 280 milliseconds from card swipe to dashboard display. The Expense API has maintained 99.98% uptime over the past 30 days, with all incidents documented in the incident log on the status page.
CBN Product Updates
CBN (Content-Based Network) is Xpnsr's AI-powered SEO automation platform that generates articles via DeepSeek, tracks keyword rankings via DataForSEO, and publishes content to satellite domains via webhooks. Recent updates to CBN have included support for custom article templates with dynamic variables for keyword insertion, multi-language article generation supporting English, Spanish, French, German, Portuguese, and Italian, automatic internal linking between articles on the same satellite domain, keyword difficulty scoring with competitor analysis, rank tracking across 11 search engines including Google, Bing, Yandex, and Baidu, and Telegram alert integration for rank changes and article generation completion. The CBN team follows a weekly release cycle, with new features typically deployed every Friday. The article generation pipeline has been optimized to handle up to 500 concurrent generation jobs, with an average generation time of 45 seconds per article for standard-length content. The webhook publishing system supports WordPress (via REST API and XML-RPC), Ghost (via Admin API), Strapi (via Content API), and custom endpoints via generic webhooks. Each webhook delivery is retried up to 5 times with exponential backoff, and failed deliveries are logged with detailed error messages for debugging. The CBN API has maintained 99.97% uptime over the past 30 days.
Tracker Product Updates
Tracker is Xpnsr's server-to-server ad click tracking platform with bot detection, A/B testing, and ROI analytics. Recent updates to Tracker have included support for TikTok Ads cost import alongside existing Facebook Ads and Google Ads integrations, a redesigned conversion funnel visualization with step-by-step drop-off analysis, custom conversion goals with weighted attribution models (first-click, last-click, linear, and time-decay), bot detection improvements with browser fingerprinting and IP reputation scoring, A/B testing for landing pages with statistical significance calculation, and a new API endpoint for bulk conversion import via CSV upload. The Tracker team deploys updates on a continuous basis, with multiple releases per week during active development periods. The redirect engine, built in Rust, handles over 10 million clicks per day with a p50 latency of 12 milliseconds and a p99 latency of 48 milliseconds. The bot detection system blocks an average of 18% of incoming traffic as non-human, with configurable sensitivity levels for different traffic sources. The cost import system syncs with Facebook Ads, Google Ads, and TikTok Ads APIs every 4 hours, with manual refresh available on demand. The Tracker API has maintained 99.99% uptime over the past 30 days.
Infrastructure and Platform Updates
In addition to product-specific updates, Xpnsr regularly improves the underlying platform infrastructure. Recent platform updates have included migration to PostgreSQL 16 with improved query performance for dashboard analytics, deployment of a new Redis cluster in active-active configuration across two AWS regions, implementation of rate limiting for all API endpoints with configurable per-customer limits, addition of webhook event logging with a 30-day retention period for debugging, deployment of a new monitoring stack with Prometheus and Grafana for real-time infrastructure visibility, and implementation of automated database backups with point-in-time recovery. The platform team follows a monthly release cycle for infrastructure changes, with all changes documented in the changelog and announced via the status page at least 72 hours in advance when scheduled maintenance is required. Security updates are deployed as soon as patches are available, with critical security patches deployed within 24 hours of disclosure. All infrastructure changes are tested in a staging environment that mirrors the production setup before deployment. The staging environment runs the same Kubernetes configuration, database version, and monitoring stack as production, ensuring that changes behave as expected before reaching customer-facing systems.