> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/integrations/metrics-tools.md).

# Metrics tools

Connect external metrics data sources to Smaply

Connect a metrics tool once at the account level, and every journey map in your account can show live values from it. Use these integrations to surface KPIs, survey results, and dashboard data on the journey moments where they actually matter.

#### Why connect a metrics tool

* Tie experience moments to real numbers (conversion, CSAT, NPS, churn) without leaving Smaply
* Metrics refresh on a roughly hourly cycle, so journey maps reflect current data
* One connection serves every workspace and every journey map in your account

{% hint style="info" icon="tag" %}
Service account authentication is available on the **Governance** plan for tools that support it. OAuth is available on all plans with metrics integrations.
{% endhint %}

#### In this section

* [**Google Analytics**](/integrations/metrics-tools/google-analytics.md) - Web traffic, conversion, and user behaviour metrics.
* [**Power BI**](/integrations/metrics-tools/power-bi.md) - Dashboards, datasets, and tables from your Power BI workspaces.
* [**Excel 365**](/integrations/metrics-tools/excel-365.md) - Any Office 365 spreadsheet as a metric source.
* [**Google Sheets**](/integrations/metrics-tools/google-sheets.md) - Flexible connector for any structured spreadsheet data.
* [**Qualtrics**](/integrations/metrics-tools/qualtrics.md) - Survey responses, experience scores, and feedback metrics.


---

# 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://helpdesk.smaply.app/integrations/metrics-tools.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.