> 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/july-2024/v0.20.1-checkout-view-bubble-destination-optimization-user-survey-form.md).

# v0.20.1: Checkout view, Bubble destination optimization, User survey Form

With this small release of Impler v0.20.1 we're excited to introduce Checkout view, Optimization to bubble destination and survey form to know users.

### ✨ New Features

* **Checkout View:** Showing you exact calculation of amount while doing checkout of any plan. So users can understand the calculation of how much is deducted.

### ➕ Improvements

* **Bubble Destination:** Showed custom domain name only when environment is production. So users don't get stuck.
* **User survey form:** To serve users better, introduced survey form to know more about user background.

***

**Stay Connected and Share Your Thoughts**

We’re constantly working on improving the way we handle CSV & Excel import in your product, and we value your input on features, bugs, and more.

Your feedback is crucial in guiding our development efforts and making Impler better. Feel free to send a message to <bhavik@impler.io> and join our [Discord](https://discord.impler.io).


---

# 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 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/july-2024/v0.20.1-checkout-view-bubble-destination-optimization-user-survey-form.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.