> For the complete documentation index, see [llms.txt](https://docs.twoowls.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twoowls.io/getting-started/custom-events.md).
# Custom events
### Benefits of custom events
{% hint style="info" %}
**Track beyond:** Every business is different, and so are their definition of valuable events. An online class or a digital product brand might want to track the "download" action, while a clothing brand might see "Search" is an effective indicator of buying power.
{% endhint %}
Custom events help you track beyond what's predefined, and build high-value audiences out of those events.
Examples include:
* View Ebook
* Search
* Form submit
* Subscribe
* Click "Contact"
* Click "Review"
* & many more.
### Setting up
Say you want to create a campaign to target people who have clicked the subscribe button on your website, you need a “subscribe” event.
Here’s how to set it up with Two Owls so your pixel get a Subscribe event whenever someone clicks on the button you choose
### Name the custom event
### Define the button to track
### Test your custom event
{% hint style="info" %}
📝Note that you can only track **click-based** events with this setup. If you need to track events that fire on other types of triggers, don’t hesitate to contact us for support!
{% 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://docs.twoowls.io/getting-started/custom-events.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.