> For the complete documentation index, see [llms.txt](https://support.happydemics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.happydemics.com/launch/survey-customisation/how-to-customise-the-consideration-and-purchase-intent-kpis.md).
# How to customise the Consideration and Purchase intent KPIs?
You have the flexibility to choose the action verb that best fits your brand, product, or service for the Consideration and Purchase Intent indicators.
**Here’s a quick reminder of what these indicators measure:**
* **Consideration** looks at how recalling your ad influences whether people would consider your brand as an option for their needs.
* **Purchase intent** measures the effect of your ad on how willing someone is to make an immediate purchase (or take a similar meaningful action) related to your brand.
When setting up your brand lift, you can select from a variety of action verbs that suit your campaign—such as buy, subscribe, visit, offer, join, download, book, use, or consider. Your chosen words for consideration and/or purchase intent will be used directly in the survey questions to create the most relevant and authentic experience for your respondents.
**For example:**
* If the campaign is about the city of “Paris”, you could choose:\
*In the future, would you consider **visiting** Paris?*\
\&#xNAN;*Today, do you intend **to visit** Paris?*
* If the campaign is about a music streaming platform / app such as “Deezer”, you could choose:\
*In the future, would you consider **subscribing** to Deezer?*\
\&#xNAN;*Do you intend **to subscribe** to Deezer today?*\
or\
*In the future, would you consider **downloading** Deezer?*\
\&#xNAN;*Today, do you intend **to download** Deezer?*
Remember, the most suitable action verb will depend on your campaign’s objective, your brand, product, service, specific offer, and context.
We offer a variety of options that fit most industries. If you prefer, you can also choose a more general wording for these indicators that works across most brands or products.\
Here’s the full list of available phrases:
**Here’s the full list of available phrases:**
| **Verb** | **Buy** |
| ------------- | --------------------------------------------------------------------------------- |
| Consideration | In the future, would you consider buying \[brand/product]? |
| Intent | Today, do you intend to buy \[brand/product]? |
| **Verb** | **Suscribe** |
| Consideration | In the future, would you consider subscribing to \[brand/product]? |
| Intent | Today, do you intend to subscribe to \[brand/product]? |
| **Verb** | **Visit** |
| Consideration | In the future, would you consider visiting \[brand/product]? |
| Intent | Today, do you intend to visit \[brand/product]? |
| **Verb** | **Give as a gift** |
| Consideration | In the future, would you consider giving \[brand/product] as a gift? |
| Intent | Today, do you intend to give \[brand/product] as a gift? |
| **Verb** | **Sign up** |
| Consideration | In the future, would you consider signing up to \[brand/product]? |
| Intent | Today, do you intend to sign up to \[brand/product]? |
| **Verb** | **Download** |
| Consideration | In the future, would you consider downloading \[brand/product]? |
| Intent | Today, do you intend to download \[brand/product]? |
| **Verb** | **Book** |
| Consideration | In the future, would you consider booking via \[brand/product]? |
| Intent | Today, do you intend to book via \[brand/product]? |
| **Verb** | **Use** |
| Consideration | In the future, would you consider using \[brand/product]? |
| Intent | Today, do you intend to use \[brand/product]? |
| **Verb** | **Consider / Buy (generic version)** |
| Consideration | In the future, would you consider \[brand/product]? |
| Intent | Today, do you intend to buy a product or service from the brand \[brand/product]? |
---
# 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://support.happydemics.com/launch/survey-customisation/how-to-customise-the-consideration-and-purchase-intent-kpis.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.