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

# Contentsquare

**Contentsquare** is a SaaS solution that anonymously tracks all mouse movements, clicks, and mobile interactions within a website or app to provide insights into customers’ behavior.&#x20;

The tracking data is then aggregated and analyzed via scores, visualizations, and recommendations.&#x20;

## Contentsquare and AB Tasty <a href="#h_01j73pvnnmtnwp9tsxp69s0szz" id="h_01j73pvnnmtnwp9tsxp69s0szz"></a>

AB Tasty is joining forces with Contentsquare to offer you even more precise and advanced campaign analyzes.&#x20;

Results regarding a campaign’s variant performance, a variant to fine-tune, a campaign, and/or variation to prioritize are integrated into Contentsquare analysis.

Contentsquare collects the following information related to AB Tasty:&#x20;

* Campaign Name
* Campaign ID&#x20;
* Variation Name&#x20;
* Variation ID

## Configuration <a href="#h_01j73pvnnmpg55yqeh2mergb0f" id="h_01j73pvnnmpg55yqeh2mergb0f"></a>

To enable the integration of Contentsquare and AB Tasty, follow the guidelines outlined in the [Contentsquare documentation](https://docs.contentsquare.com/thirdparties/#ab-tasty).


---

# 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.abtasty.com/integrations/push-integrations/contentsquare.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.
