# What is Taviqo?

### Why we built Taviqo

GTM is a powerful tool — but as your tags, triggers, and variables grow, it becomes increasingly difficult to manage.

**Common problems with existing GTM workflows:**

* Hard to see which tags are connected to which triggers at a glance
* Requires separate documentation to explain GTM structure to teammates
* One wrong edit can break your entire tracking setup

***

### How Taviqo solves this

Taviqo represents your GTM configuration as a **visual flow canvas**.

\[📸 IMAGE: Canvas screenshot showing PV trigger → CT condition → GA4 tag → DLV variable flow]

Instead of navigating through GTM's complex UI, you can see your entire tracking structure at a glance — and export it directly to GTM.

***

### Key Features

| Feature         | Description                           |
| --------------- | ------------------------------------- |
| Visual Canvas   | Connect nodes with drag-and-drop      |
| GTM JSON Export | Generate GTM-ready JSON files         |
| GTM JSON Import | Load existing GTM configs into canvas |
| Code Snippets   | Auto-generate dataLayer.push() code   |
| Workspaces      | Manage GTM configs per project        |

***

### Who is Taviqo for?

* **Digital Marketers** — Manage GTM without relying on developers
* **Growth Hackers** — Quickly iterate on event tracking setups
* **Frontend Developers** — Manage GTM configs alongside your codebase
* **Marketing Agencies** — Handle multiple clients' GTM configurations


---

# Agent Instructions: 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:

```
GET https://taviqo.gitbook.io/taviqo-docs/getting-started/what-is-taviqo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.