> For the complete documentation index, see [llms.txt](https://docs.saas.haut.ai/haut.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saas.haut.ai/haut.ai/releases/changelog/version-2026-36.md). # Version 2026-36 ## Release date September 3, 2026 ## Consumer Apps ### Mailchimp integration Start collecting names, email addresses, and phone numbers from your Consumer App straight into a Mailchimp audience. Every completed analysis lands in Mailchimp as an event, so you can build a customer journey on it. To connect, click **Connect** on the Mailchimp card in the app's **Integrations** section, approve access in Mailchimp, choose the audience that should receive contacts, and turn on **Data sync**. No API key is needed. Learn more: [Integrate Consumer App with Mailchimp](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-mailchimp.md). * Collect consent for marketing emails with the **Email me with news and offers** checkbox on the Email question. Ticked contacts arrive as **Subscribed**, so you can send them marketing emails. Everyone else arrives as **Transactional** and gets transactional emails only. * Each contact carries email, name, phone number if your survey asks for it, and the Haut.AI subject ID as external ID. The **Skin Analysis Complete** event carries the analysis results, survey answers, and product recommendations. Learn more: [Data Sent to Mailchimp](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-mailchimp/data-sent-to-mailchimp.md). * If both Klaviyo and Mailchimp are connected, contacts and events go to both. {% hint style="info" %} The Mailchimp integration is switched on per company. Contact your account manager to enable it. {% endhint %} ### Skin analysis results as Klaviyo profile properties Skin analysis results are now saved as properties on the Klaviyo profile, not only as an event. Build dynamic segments on them, for example everyone whose redness tag is Poor, and use those segments in your flows and campaigns. Properties update every time a person completes a new analysis, so the segments stay current on their own. Every Face Skin Analysis 3.0 parameter arrives as `hautai__score` and `hautai__tag`, for example `hautai_redness_score` and `hautai_redness_tag`, alongside age, skin type, skin tone, and ITA. Existing profiles were updated once with their latest analysis, so segments fill immediately. Learn more: [Build Klaviyo Segments from Skin Analysis Results](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-klaviyo-crm/build-klaviyo-segments-from-skin-analysis-results.md) and [Data Sent to Klaviyo](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-klaviyo-crm/data-sent-to-klaviyo.md). ### Support for PDF report and app links in your emails The **Skin Analysis Complete** event now carries `pdf_report_url` and `app_url`. Use them in your Klaviyo email templates and WhatsApp follow-ups to add a **Download report** button, or to send people back into the app for a new analysis. Learn more: [Sending Automated Emails with Skin Analysis Results](/haut.ai/quick-start-guides/no-code-app-for-e-commerce-businesses/integrate-consumer-app-with-klaviyo-crm/sending-automated-emails-with-skin-analysis-results.md). ### End-of-experience feedback Ask users what they thought of their results. Turn on end-of-experience feedback in **Advanced settings** and users can rate the experience with **Like** or **Dislike** at the bottom of the results screen. A dislike opens a short list of reasons and an optional comment, and you edit that list to fit your app. The prompt appears once per session, is optional, and never blocks the results. Works in Skin and Hair apps. Learn more: [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md#end-of-experience-feedback). ### Custom text above the download button When **Download report** is enabled, you can add a line of text above the download button on the results screen, for example *Download your result and share it with your consultant*. Leave it empty to keep the standard button. Learn more: [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md#download-report). ### Hair app: hints on result parameters Hair result cards can now show an **(i)** icon with a short note about the parameter. The first note explains that hair color detection depends on lighting conditions. ## Datasets ### Data retention controls You now fully control what is stored and for how long, per dataset. Keep photos, metrics and results, and survey answers only as long as your policies and your customers expect, and let the platform delete the rest for you. Set it under **Settings → General → Data retention**. It covers all three data types: **Photos**, **Metrics & results**, and **Survey answers**. Set one period for everything (**Unified**) or a separate period per type (**Per parameter**), from **Delete immediately** to **Indefinitely**, with custom values in days or months. Expired data is permanently deleted by an hourly job. Deleting a subject or a photo now also removes its results and survey answers. Learn more: [Data Retention](/haut.ai/haut.ai-features/datasets/data-retention.md). {% hint style="warning" %} The **Photo retention** option has been removed from the Consumer App's Advanced settings. Your existing retention values were carried over to the dataset unchanged. {% endhint %} ## Product Inventory ### Recommend only the products you have in stock Each product now has an **In stock** switch on its product card, and the inventory table shows an **In stock** or **Out of stock** chip. Out-of-stock products stay in your inventory and drop out of recommendations. Via the API the field is `out_of_stock`. Learn more: [Product Inventory](/haut.ai/haut.ai-features/product-recommendation-system-2.0/product-inventory.md). ### Currencies * The Chilean peso (**CLP**) is now available as a product currency. * Swiss franc prices display as **CHF** instead of the generic franc sign **₣**. ### Fixes * Price and currency changes now appear in the inventory table immediately, without a page reload. * The product dialog stays open after you delete the product image. ## Face Skin Analysis 3.0 * The **Dark circles** result in the SaaS platform now shows the density under the left and right eye separately, matching what the API already returned. Learn more: [Dark Circles](/haut.ai/haut.ai-features/algorithms/face-skin-analysis-3-0/dark-circles.md). * The **Lip lines** mask overlay now renders as colored line highlights instead of a low-quality grey area. Scores were not affected. * The **Lip lines** parameter now has its own documentation, for the results view and for the API. Learn more: [Lip Lines](/haut.ai/haut.ai-features/algorithms/face-skin-analysis-3-0/lines/lip-lines.md) and [Lip Lines Parameter Result Scheme](/haut.ai/developers/saas-api-overview/api-for-face-skin-analysis-3.0/lines/lip-lines.md). *** {% hint style="warning" %} Not a Haut.AI client yet? {% endhint %} Book a demo Platform overview on haut.ai --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.saas.haut.ai/haut.ai/releases/changelog/version-2026-36.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.