> For the complete documentation index, see [llms.txt](https://changelog.impler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.impler.io/december-2024/v0.29.0-widget-customisation.md). # v0.29.0: Widget Customisation What if you could customise the import widget to match your application’s look and feel? With this release, now you can! ### ✨ Latest Features * Widget Customisation, You can now customize widgets to match your style — change font colors, button colors, hover effects, and primary colors, just from the `useImpler` hook. * Onboard Flow Revised, New users now get an new onboarding flow. You can either upload an Excel or CSV file, and the columns are automatically generated with types detected, or you can choose to start with sample columns. * **Webhook Retry Settings,** You can now set the retry count and retry interval for failed webhooks to control how many times it retries and the delay between attempts. ### ➕ Enhancements * **Enhanced webhook failure notifications**, Now, all team members associated with a project will receive notifications when a webhook fails. ### 🔧 Bug Fixes * **Bubble Data-Sending on Second Attempt,** Fixed issue with data not sending on the second attempt. * **Skip Empty Rows in CSV Parsing,** Now skips empty rows during parsing and fixes the issue of empty rows in the CSV file. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://changelog.impler.io/december-2024/v0.29.0-widget-customisation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.