> For the complete documentation index, see [llms.txt](https://docs.indinite.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.indinite.co.uk/marketing-tools.md).
# Marketing Tools
Creating an event is half the battle.\
Getting people to **actually show up**? Thatβs where marketing comes in.
Lucky for you, Indinite gives you built-in tools to make sharing easy and professional.
### π Sharing Your Event
Every event gets its own shiny link. Share it anywhere: WhatsApp, Instagram, email, even on a poster with a QR code.
* **Copy Link** β Instant share link
* **Social Buttons** β Facebook, Twitter, WhatsApp, Telegram
* **Preview Image** β Your event cover automatically becomes the OG image (the thing people see on social media previews).
> π‘ Pro tip: Share it multiple times. People rarely buy tickets the first time they see something. Repetition = sales.
### πΈ Event Page = Free Poster
Your event page is already designed like a digital poster:
* Big bold cover image
* Title & description
* Tickets right there
You can skip Canva this time π
---
# 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.indinite.co.uk/marketing-tools.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.