> For the complete documentation index, see [llms.txt](https://themesic-docs.gitbook.io/url-shortener-for-concord/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themesic-docs.gitbook.io/url-shortener-for-concord/url-shortener-module-for-concord.md).

# URL Shortener module for Concord

### 🧩 Module Overview

The **URL Shortener Module** enhances your CRM marketing and outreach capabilities by allowing you to:

* Generate short links for any external or internal URL
* Attach custom splash pages with countdowns and promotional content
* Track visits and engagement analytics for each link
* Manage all links and splash pages directly within the CRM interface
* Control access and visibility through CRM user permissions

> This module integrates seamlessly into the existing CRM layout and uses Concord’s UI framework for a consistent user experience.


---

# 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://themesic-docs.gitbook.io/url-shortener-for-concord/url-shortener-module-for-concord.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.
