> For the complete documentation index, see [llms.txt](https://docs.allthingsghl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allthingsghl.com/funnels/cards/promo-tag.md).
# Promo Tag
Spruce up your design with a promo tag
```css
.promo-tag {
position: relative;
font-family: 'Inter', sans-serif;
}
.promo-tag::before {
content: "Edit Me - Special Deal";
position: absolute;
top: 0;
left: 4px;
transform: translateY(-50%);
background: #007027;
color: #FFFFFF;
padding: 6px 10px;
border-radius: 0px;
font-size: 12px;
font-weight: 600;
line-height: 1;
white-space: nowrap;
pointer-events: none;
font-family: 'Inter', sans-serif;
}
```
### Instructions
1. Paste code into `Custom CSS`.
2. Make sure to edit "content" text
3. Apply the `promo-tag` class to any row element.
---
# 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://docs.allthingsghl.com/funnels/cards/promo-tag.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 `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.
