> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/getting-started/about-growlytics.md).

# About Growlytics

Growlytics is an end-to-end Marketing Automation and Customer Engagement platform. At Growlytics, we are committed to boosting your business's online conversions and substantially increasing revenue with personalized user engagement and retention with the help of data-driven marketing.

With Growlytics, you can design automated omnichannel user journeys, analyze and track customer behavior and send personalized and contextual messages to targeted customers based on their journey.

You can also use automation to send personalized Emails, SMS, WhatsApp messages, push notifications, web social proofs, In-App messages, web popups, and much more to your users all from a single integrated platform.

By assisting you in leveraging real-time insights into your users and their interactions with your app, website, and campaigns, our journey designer enables you to seamlessly engage users at each stage.


---

# 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://support.growlytics.in/getting-started/about-growlytics.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.