> 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-32.md). # Version 2026-32 ## Release date August 17, 2026 ## Hair Analysis ### PDF reports for Hair Hair analysis results can now be delivered as a PDF report, the same way face results already were. The report covers the hair and scalp metrics, the detected main concerns, and the recommended routine. Learn more: [PDF reports](/haut.ai/haut.ai-features/datasets/get-a-report/pdf-reports.md). * Hair concern labels, concern descriptions, and hair-type labels in the report now use the same wording as the app — for example **Color-treated hair** rather than **Colored hair** — and the strings that were previously missing a translation are now populated. * The routine section no longer shows a **Main concern** badge next to each recommended product. ### Customize metrics The **Gathered Hair** and **Detector** parameters no longer appear in the **Customize metrics** list for Hair Consumer Apps. They are technical checks rather than reportable metrics, so they are no longer offered as metrics you can show or hide. Learn more: [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md). ## Surveys ### ID question type for the Brazilian CPF Surveys can now collect a Brazilian CPF through a dedicated **ID** question type. The field is presented with a CPF input mask, is validated before the answer is submitted, and is stored as a special field alongside the other participant profile fields such as date of birth and gender. Learn more: [Add and Customize Survey into Consumer App](/haut.ai/haut.ai-features/consumer-apps/add-and-customize-survey-into-consumer-app.md). * The **ID** question type is off by default. Contact your account manager to enable it for your company. * CPF answers are included in Hair App webhook payloads and CSV exports along with the rest of the survey answers. ## Datasets and Analytics ### Export an audience segment to Klaviyo You can now push an audience segment from the Analytics view straight into Klaviyo. **Export to Klaviyo** freezes the segment's current membership, resolves each subject's email and phone number from their survey answers, and adds them to a Klaviyo static list. Re-running the export does not create duplicates. Learn more: [Export an Audience Segment to Klaviyo](/haut.ai/haut.ai-features/datasets/export-audience-segment-to-klaviyo.md). * The button shows the number of profiles that will actually be exported, which can be lower than the number of subjects in the segment — a subject without a resolvable email or phone number cannot become a Klaviyo profile. * **Profiles are now added to the Klaviyo list regardless of marketing consent.** Previously, a subject who had not given email or phone consent was skipped. Consent is still recorded on the profile, so you can continue to filter on it inside Klaviyo, but it no longer determines list membership. Review your Klaviyo flows if they relied on the old behavior. Learn more: [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). ## Consumer Apps ### Custom text under the heading Every type of Consumer App now supports an optional line of custom text under the heading, for explanatory copy of your own. Learn more: [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md). ### Fixes * The results shelf now opens on the first tab that has content instead of always opening the **Face** tab — so a hair-only app opens on **Hair**. * When the **Buy online** button has been renamed, adding a product to the cart now correctly changes the button to **Added. Go to cart**. Previously the renamed button kept its custom text and gave no feedback that the product had been added. Learn more: [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md). ## Body Skin Analysis ### Macroscaling, Monk Skin Tone, and Sagging The Macroscaling, Monk Skin Tone, and Sagging parameters are now live for Body Skin Analysis, and body metrics now return a per-region breakdown in `area_results` in addition to the aggregated score. Learn more: [Body Skin Analysis Reference](/haut.ai/haut.ai-features/algorithms/body-skin-analysis.md) and [Regions & Metrics](/haut.ai/haut.ai-features/algorithms/body-skin-analysis/regions-and-metrics.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-32.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.