Stay up-to-date with the latest DataOT release notes and discover new features, performance improvements, and critical bug fixes that enhance your experience with our AI-powered content automation platform. From ecommerce optimization to seamless CMS integrations, each update is designed to make DataOT faster, smarter, and more intuitive for users. Our detailed release history ensures transparency and allows you to leverage the full potential of DataOT's cloud-based solutions, driving better business outcomes and maximizing SEO performance. Explore how DataOT is continuously evolving to meet your needs.
Webapp slugs now support an advanced optional forward slash, giving you more flexibility to include related content via partials—without triggering the full master slug system.
Mailchimp integration just got more powerful with support for PATCH API calls, giving you greater flexibility when updating subscriber data. We've also resolved a JSON output issue in Site Manager for older sites, ensuring smoother and more reliable site management.
MetaBuilder now supports both localbusiness and product reviews, enhancing your structured data for even better SEO. We've also made rendering improvements behind the scenes to support upcoming upgrades, and standardised the #no-name# format for greater consistency across the platform.
The billing name is now explicitly set during form-based payments to ensure it's properly captured and stored.
When using Stripe, the "Name on Card" field is now required—even though Stripe doesn’t mandate it—so we can better identify and associate customers.
Importing users now correctly includes custom CRM fields during the process. The "Get user by email" function now supports an optional flag to return only the related CRM ID.
User CRM settings can now be resaved and reconfigured after resolving a variable conflict with the websocket service. The asset path is now cached for a week to improve performance. Minor updates made to clean up white space formatting.
Single-element arrays are now stored as arrays rather than integers to ensure consistency between GUI saves and data imports. To maintain backward compatibility, webapps are now labelled as either v1 or v2. New webapps default to v2, and v1 webapps...