> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-activation/connectors/matelso.md).

# Matelso

{% hint style="info" %}
**Matelso** is a call tracking and lead communication platform that connects phone calls with web and marketing data. It assigns tracking phone numbers to website visitors (for example via Search & Replace), so inbound calls can be attributed to campaigns, pages, and traffic sources. Call and related web data are stored in matelso and can be forwarded to analytics, ads, CRM, or custom systems through Integrations 2.0. This allows marketing and sales teams to measure phone leads alongside digital channels and automate follow-up workflows after a call.
{% endhint %}

### Goal of JENTIS integration

When a visitor sees a Phone number on page (by Search & Replace), calls it, when the call ends, Matelso fires a **POST-Call** push to your JENTIS DCP with Call data  + Web data + Custom data.

1. Website script + Search\&Replace number
2. Visitor calls Phone number
3. Call ends (POST-Call)
4. Integrations 2.0 Custom Push to JENTIS
5. Custom analytics tool (e.g.: GA4) tag fired from JENTIS


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/data-activation/connectors/matelso.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.