> For the complete documentation index, see [llms.txt](https://brand.coingecko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brand.coingecko.com/verbal-identity/style/emoji.md).

# Emoji

## Considerations 

Keep in mind that emojis can have implications across different cultural and diversity communities, and that different age groups use emojis differently.

😎 🚀 🌕 ❤️ 🦎 ⭐️ 🔥 📈 📉 🤑 🤓 🖼️ 💪

## Usage

* **Utilize emojis in push notifications, text messages, inbox messages, and chatbot content**. **Avoid using them in core product content.**
  * Not all push notifications require an emoji. Exclude emojis about half the time to maintain their effectiveness.
  * Limit usage to one emoji unless using two or more makes the message clearer.
  * Place emojis in either the header or the body text, but not both within the same message. Keep it straightforward and avoid overdoing it.
  * Use emojis to convey support only. Do not include them in corrective communications, such as error messages.
  * Ensure the messages make sense without the inclusion of emojis. If the sentiment is unclear from the text alone, revise the wording. 
  * Never replace a word with an emoji.
  * Do not start or insert emojis in the middle of a message, as it can make the sentence appear disjointed.
  * Avoid using emoticons. Unlike emojis, emoticons such as =) or :-0 are created using keyboard characters to represent facial expressions. We do not use emoticons because screen readers vocalize each symbol.
  * Minimize the use of gender-specific emojis or those with particular skin tones.
  * Refrain from using emojis that might be sensitive or cause negative emotions.

{% hint style="info" %}
We can be more flexible with the rules on Twitter, Instagram, YouTube, TikTok, and Facebook. Use emojis that best fit the message, regardless of type or quantity.
{% endhint %}


---

# 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://brand.coingecko.com/verbal-identity/style/emoji.md?ask=<question>&goal=<endgoal>
```

`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.