> For the complete documentation index, see [llms.txt](https://hitsubscribe.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hitsubscribe.gitbook.io/home/osiris/conversions/cta-events.md).

# CTA Events

We don't have a screenshot of this report, since it isn't meaningful for a community site like [MMAP](https://makemeaprogrammer.com/), which has no marketing funnel to speak of.  (MMAP being the site we use for the demo version of Osiris.)

But by way of description, this is a report of custom events from your GA4 that you have mapped to CTAs on your site.  Generally when we've implemented this for clients, it takes the form of mapping a click event for an interstitial, graphical CTA like "sign up for the newsletter" to a GA4 event.  In this fashion, we can report on how many clicks have happened for the newsletter CTA, on which pages, and from sessions with what sources and media.

The report is grid-like in structure and shows you a breakdown of the event, the URL it occurred at, the originating session source and medium, and the number of times it occurred for this combination of things.  You can filter by:

1. Date range
2. Event(s)
3. Media


---

# 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://hitsubscribe.gitbook.io/home/osiris/conversions/cta-events.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.